Proofable MCP
REMOTE · MCP.PROOFABLE.ME · SCANNED OCT 7
Give AI agents real access without giving up control through Proofable MCP.
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the Proofable MCP server?
Proofable MCP is a hosted endpoint at https://mcp.proofable.me/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.proofable.me
claude mcp add --transport http proofable-mcp 'https://mcp.proofable.me/mcp'
{
"mcpServers": {
"proofable-mcp": {
"url": "https://mcp.proofable.me/mcp"
}
}
} {
"servers": {
"proofable-mcp": {
"type": "http",
"url": "https://mcp.proofable.me/mcp"
}
}
} [mcp_servers.proofable-mcp] url = "https://mcp.proofable.me/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"proofable-mcp": {
"type": "remote",
"url": "https://mcp.proofable.me/mcp",
"enabled": true
}
}
} openclaw mcp add proofable-mcp --url 'https://mcp.proofable.me/mcp' --transport streamable-http
mcp_servers:
proofable-mcp:
url: "https://mcp.proofable.me/mcp" {
"McpServers": {
"proofable-mcp": {
"Transport": "http",
"Url": "https://mcp.proofable.me/mcp"
}
}
} assistant mcp add proofable-mcp -t streamable-http -u 'https://mcp.proofable.me/mcp'
{
"mcpServers": {
"proofable-mcp": {
"type": "http",
"url": "https://mcp.proofable.me/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.
- 7 Oct 26 −40
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Oct 26 +1
- Stability: 0.03 → fail ▼ security
- A breaking change shipped without a version bump: still 0.1.3 ▼ security
- Tool “proofable_agent_create” was removed ▼ security
- Tool “proofable_agent_link” was removed ▼ security
- Tool “proofable_agent_mount” was removed ▼ security
- Tool “proofable_proofs_get” was removed ▼ security
- Tool “proofable_proofs_update” was removed ▼ security
- Tool “proofable_secret_create” was removed ▼ security
- Tool “proofable_secret_list” was removed ▼ security
- Tool “proofable_secret_revoke” was removed ▼ security
- Tool “proofable_verify” was removed ▼ security
- Schema quality: 3155 → 961 ▲ functional
- Destructive annotations: 100 → pass functional
- 30 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 29 Sept 26 +39
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 97 functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Tool coverage: 100 functional
- 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
- 25 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
- 11 Sept 26 36
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 7 Oct 2026 · Probed https://mcp.proofable.me/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=proofable.me | CN=WE1,O=Google Trust Services,C=US | 22 Aug 2026 | 20 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 93adc32bc083f225134043cae33bcaed |
| SANs: proofable.me, *.proofable.me | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.proofable.me. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| me. | present | 45352 | 8 | Verified |
| proofable.me. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.proofable.me/mcp/.well-known/oauth-protected-resource", scope="neus:core neus:profile neus:secrets"
Bearer resource_metadata="https://mcp.proofable.me/mcp/.well-known/oauth-protected-resource", scope="neus:core neus:profile neus:secrets"| Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://mcp.proofable.me/mcp/.well-known/oauth-protected-resource", scope="neus:core neus:profile neus:secrets" |
Protected resource metadata
| Document | https://mcp.proofable.me/mcp/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.proofable.me/mcp |
| Authorisation server | https://proofable.me |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.proofable.me/mcp | Auth required | 401 | |
| http (plaintext) | http://mcp.proofable.me/mcp | HTTPS enforced | 301 | https://mcp.proofable.me/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 →
proofable_context ~43
Start here. Returns the signed-in profile, available verifiers, and the recommended workflow in one call. Handles signed-in and offline modes, no separate profile tool needed.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| agentsError | string | – | – |
| agentsStatus | string | – | – |
| authenticated | boolean | – | – |
| contextIndex | – | – | – |
| error | string | – | – |
| message | string | – | – |
| profile | object | – | – |
| recommendedWorkflow | – | – | – |
| status | – | – | – |
| verifierSummary | array | – | – |
No examples provided.
proofable_proofs_check ~176
Does this wallet already have the required proofs? Returns pass or fail, not records. To read proofs, use proofable_proofs_get. Omit the wallet when signed in.
| Name | Type | Req | Description |
|---|---|---|---|
| gateId | string | – | Optional hosted gate or listing id. Signed-in owners still get eligible + matchedCount only. |
| handle | string | – | Optional handle filter for handle-based verifiers. |
| minCount | number | – | Minimum number of matching proofs. Default 1. |
| namespace | string | – | Optional namespace filter for handle checks. |
| requireAll | boolean | – | Require all listed verifiers. Default false accepts any one. |
| verifiers | array | yes | Verifier IDs from proofable_verifiers_catalog. |
| wallet | string | – | Wallet or DID to verify. Omit when signed in to use the current account. |
| Name | Type | Req | Description |
|---|---|---|---|
| eligible | boolean | – | – |
| error | string | – | – |
| matchedCount | number | – | – |
| message | string | – | – |
| satisfied | boolean | – | – |
| status | – | – | – |
| success | boolean | – | – |
| unknownVerifiers | array | – | – |
No examples provided.
proofable_verifiers_catalog ~39
Full verifier catalog: supported networks and required inputs. Use this when a verifier needs schema details beyond the compact verifierSummary in proofable_context.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | – |
| message | string | – | – |
| status | – | – | – |
| verifiers | array | yes | – |
No examples provided.
proofable_verify_or_guide ~177
Reuse a qualifying portable proof or return the one next step needed to finish verification. Omit the wallet when signed in. Signed-in ownership proofs continue with proofable_verify. A hosted link is returned only for an outside login, payment, or different account.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Optional network hint. Omit when Proofable can infer it from the wallet format. |
| data | object | – | Inputs for the selected verifiers. Used only when a new Proof is needed. |
| options | object | – | Optional verification options |
| requireAll | boolean | – | Require all listed verifiers. Default false accepts any one. |
| verifierIds | array | yes | Verifier IDs from proofable_verifiers_catalog. |
| walletAddress | string | – | Wallet or DID. Omit when signed in to use the current account. |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| eligible | boolean | – | – |
| error | string | – | – |
| hostedVerifyUrl | string | – | – |
| matchedCount | number | – | – |
| message | string | – | – |
| proofs | array | – | – |
| status | – | – | – |
| success | boolean | – | – |
No examples provided.
What is the Proofable MCP server?
Proofable MCP is listed in the public MCP registry as io.github.proofable/mcp. Give AI agents real access without giving up control through Proofable MCP. This page covers its hosted endpoint (https://mcp.proofable.me/mcp).
Is the Proofable MCP server safe to use?
Proofable MCP scores 36 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 Proofable MCP server expose?
Proofable MCP exposes 4 tools: proofable_context, proofable_verifiers_catalog, proofable_proofs_check, proofable_verify_or_guide. Their descriptions and schemas cost roughly 435 tokens of context every time the server is loaded.
Does the Proofable MCP server require authentication?
Yes. Proofable MCP asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Proofable MCP server still maintained?
Proofable MCP is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.