Promise MCP server

• Registry nameai.usepromise/promiseverified in the MCP registry

The registry name sits under usepromise.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-24
• Tools11
• Server calls itselfPromise MCP
• Server version0.1.0
• Protocol version2025-03-26

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 406 ms.

• Its tools do every use case we checked: find commitments hidden in email threads; keep notes on people and their upcoming follow-ups.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score69 of 100answers 100 · does the job 100 · definitions 83 · context 100 · use 0 · connects 100 · lowered by the warning signs below
• What an agent can do with it2 of 2 use cases
• Answered100% of days12 of 12 daily checks
• Median first answer428 ms
• Space in an agent's context≈ 1,243 tokensthe definitions of all its tools (11), which an agent carries on every turn
• Tool definitionsB · 83 of 100
• Typed results0 of 11 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 11 of 11

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• connect_promise

  Return a Promise signup URL for users who want agent access to follow-up memory. Safety: Never collects provider credentials in the agent. Send the user to Promise.

• get_today

  Return what currently deserves the user's attention. Safety: Return concise items and links back to Promise for sensitive action.

• list_commitments

  List what the user owes and what the user is waiting on. Safety: Do not infer more certainty than Promise returns.

• get_commitment

  Retrieve a structured Promise commitment or waiting-on item. Safety: Prefer structured status, due dates, people, and source links over raw mail.

• get_commitment_evidence

  Show why Promise believes a follow-up or memory exists. Safety: Return source summaries and citations permitted by the platform API.

• get_person_context

  Summarize what matters before the user speaks with someone. Safety: Avoid exposing hidden/private fields unless the platform scopes allow them.

• search_memory

  Search Promise's derived memory with user authorization. Safety: Search derived Promise memory, not raw provider mailboxes.

• capture_note

  Let a user tell Promise something to remember. Safety: Echo what Promise understood and require review when the platform requests it.

• create_follow_up

  Create a future follow-up from explicit user intent. Safety: Only create follow-ups from explicit user instructions.

• mark_resolved

  Tell Promise that a commitment or waiting-on item is complete. Safety: Confirm destructive or irreversible status changes in the agent UI.

• draft_follow_up

  Draft a follow-up message without sending it. Safety: Do not send email in v1. Return a draft and Promise confirmation link.