Promise
REMOTE · MCP.USEPROMISE.AI · SCANNED SEP 29
Evidence-backed follow-through memory for what you owe, await, and need to remember.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 668 tokens (~60/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 15% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the Promise MCP server?
Promise is a hosted endpoint at https://mcp.usepromise.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.usepromise.ai
claude mcp add --transport http ai-usepromise-promise 'https://mcp.usepromise.ai/mcp'
{
"mcpServers": {
"ai-usepromise-promise": {
"url": "https://mcp.usepromise.ai/mcp"
}
}
} {
"servers": {
"ai-usepromise-promise": {
"type": "http",
"url": "https://mcp.usepromise.ai/mcp"
}
}
} [mcp_servers.ai-usepromise-promise] url = "https://mcp.usepromise.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-usepromise-promise": {
"type": "remote",
"url": "https://mcp.usepromise.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-usepromise-promise --url 'https://mcp.usepromise.ai/mcp' --transport streamable-http
mcp_servers:
ai-usepromise-promise:
url: "https://mcp.usepromise.ai/mcp" {
"McpServers": {
"ai-usepromise-promise": {
"Transport": "http",
"Url": "https://mcp.usepromise.ai/mcp"
}
}
} assistant mcp add ai-usepromise-promise -t streamable-http -u 'https://mcp.usepromise.ai/mcp'
{
"mcpServers": {
"ai-usepromise-promise": {
"type": "http",
"url": "https://mcp.usepromise.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 22 Sept 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 29 Sept 2026 · Probed https://mcp.usepromise.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.usepromise.ai | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 22 Sept 2026 | 22 Mar 2027 | RSA 2048 | SHA256-RSA | 787c58a3c39d70d12115014b41ebf61 |
| SANs: mcp.usepromise.ai | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.usepromise.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| usepromise.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.usepromise.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.usepromise.ai/mcp | HTTPS enforced | 301 | https://mcp.usepromise.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
capture_note Capture note ~85
Let a user tell Promise something to remember. Safety: Echo what Promise understood and require review when the platform requests it.
| Name | Type | Req | Description |
|---|---|---|---|
| contactId | string | – | – |
| dueAt | string | – | – |
| kind | string | – | – |
| personName | string | – | – |
| requestId | string | – | – |
| title | string | – | – |
| transcript | string | yes | – |
No output schema declared.
No examples provided.
connect_promise Connect Promise ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| clientName | string | – | Name of the agent or MCP client requesting access. |
| intent | string | – | Signup intent to preserve in Promise attribution. |
| returnUrl | string | – | HTTPS URL the user can return to after Promise authorization. |
| scopes | array | – | – |
| state | string | – | Opaque agent state returned unchanged after authorization. |
No output schema declared.
No examples provided.
create_follow_up Create follow-up ~76
Create a future follow-up from explicit user intent. Safety: Only create follow-ups from explicit user instructions.
| Name | Type | Req | Description |
|---|---|---|---|
| contactId | string | – | – |
| dueAt | string | – | – |
| personName | string | – | – |
| requestId | string | – | – |
| title | string | yes | – |
| transcript | string | – | – |
No output schema declared.
No examples provided.
draft_follow_up Draft follow-up ~66
Draft a follow-up message without sending it. Safety: Do not send email in v1. Return a draft and Promise confirmation link.
| Name | Type | Req | Description |
|---|---|---|---|
| commitmentId | string | – | – |
| context | string | – | – |
| goal | string | – | – |
| personName | string | – | – |
No output schema declared.
No examples provided.
get_commitment Get commitment ~44
Retrieve a structured Promise commitment or waiting-on item. Safety: Prefer structured status, due dates, people, and source links over raw mail.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_commitment_evidence Get commitment evidence ~42
Show why Promise believes a follow-up or memory exists. Safety: Return source summaries and citations permitted by the platform API.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_person_context Get person context ~66
Summarize what matters before the user speaks with someone. Safety: Avoid exposing hidden/private fields unless the platform scopes allow them.
| Name | Type | Req | Description |
|---|---|---|---|
| contactId | string | – | – |
| limit | integer | – | – |
| query | string | – | Name or email search when contactId is unknown. |
No output schema declared.
No examples provided.
get_today Get Today ~38
Return what currently deserves the user's attention. Safety: Return concise items and links back to Promise for sensitive action.
| Name | Type | Req | Description |
|---|---|---|---|
| horizonDays | integer | – | – |
No output schema declared.
No examples provided.
list_commitments List commitments ~54
List what the user owes and what the user is waiting on. Safety: Do not infer more certainty than Promise returns.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| scope | string | – | – |
No output schema declared.
No examples provided.
mark_resolved Mark resolved ~41
Tell Promise that a commitment or waiting-on item is complete. Safety: Confirm destructive or irreversible status changes in the agent UI.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
search_memory Search memory ~44
Search Promise's derived memory with user authorization. Safety: Search derived Promise memory, not raw provider mailboxes.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
What is the Promise MCP server?
Promise is an MCP server listed in the public MCP registry as ai.usepromise/promise. Evidence-backed follow-through memory for what you owe, await, and need to remember. This page covers its hosted endpoint (https://mcp.usepromise.ai/mcp).
Is the Promise MCP server safe to use?
Promise scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Promise MCP server expose?
Promise exposes 11 tools: connect_promise, get_today, list_commitments, get_commitment, get_commitment_evidence, and 6 more. Their descriptions and schemas cost roughly 668 tokens of context every time the server is loaded.
Does the Promise MCP server require authentication?
No. We connected to Promise without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Promise MCP server still maintained?
Promise is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.