Skip to content

Proofable MCP server

io.github.proofable/mcpproofablestreamable-httpv0.1.12Scanned

Every AI tool you use knows your work and follows your rules, with a receipt for every action.

12 tools: 1 can delete or cancel things, 8 change things and 3 only read.

Tools: 1 delete, 0 irreversible, 8 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 0
  • 3 findings

Sign-in required, OAuth metadata published. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Proofable MCP server can do

The Proofable MCP server is published by the GitHub account proofable. It has 12 tools. It can delete or cancel things (1 tool: proofable_proofs_update) and create or change data (8 tools: proofable_proofs_check, proofable_verify, proofable_verify_prepare, proofable_verify_submit and 4 more). 3 tools only read.

4 tools bring in text other people can write (proofable_verify, proofable_verify_prepare, proofable_verify_submit and 1 more).

The fixed checks matched 3 findings (annotation-conflict and credentials-mention). Each one comes with the text it matched.

Its remote endpoint asks for sign-in and publishes OAuth metadata, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 7, 2026, version 0.1.12.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

12 tools

Deletes or cancels 1Claude Code: deny
  • proofable_proofs_updateUpdate a proof you own: title, tags, and visibility (public|unlisted|private).Reads text others writeNo findings

    Why it is in this group

    • The name "proofable_proofs_update" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Update a proof you own: title, tags, and visibility (public|unlisted|private). Setting visibility to private revokes public access, so confirm before making an already-shared proof private. Or leave feedback on an accessible proof. Send one kind of change per call: metadata, vote, or comment. Owners can vote on their own proofs. Delegated agents need manage_proofs.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Changes things 8Claude Code: ask
  • proofable_agent_createCreate or import an agent on your profile.1 finding

    Why it is in this group

    • The name "proofable_agent_create" says "create": a word for a change.

    Findings

    • Info

      The input schema at properties.skills.description mentions "credential".

      Matched text

      inputSchema.properties.skills.description: "...(not a secret, not an OAuth token, not credential material)."

      What this check looks for
    Description, as the server wrote it
    Create or import an agent on your profile. Default: signed-in account. Optional separate account and controls. Generate and retain any dedicated key outside Proofable, then pass only its public address. Keep the same agentId on retries.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • proofable_agent_mountLoad the agent identity, permissions, skills, and context into this project.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Load the agent identity, permissions, skills, and context into this project.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • proofable_proofs_checkDoes this wallet already have the required proofs?No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Does this wallet already have the required proofs? Returns pass or fail, not records. Reading proof bodies needs a signed-in session, which is what unlocks proofable_proofs_get; signed-out callers get this check and can sign in to go further. Omit the wallet when signed in.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • proofable_verifyCreate a proof directly for the signed-in account.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Create a proof directly for the signed-in account. Omit the wallet for your own account. If another signer is required, use proofable_verify_prepare and proofable_verify_submit.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • proofable_verify_or_guideResolve a verification request for the selected Proofable checks.1 finding

    Why it is in this group

    • The description's first verb is "resolve": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Warn

      The server marks "proofable_verify_or_guide" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "resolve": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Resolve a verification request for the selected Proofable checks. Returns current qualifying proofs when they exist; otherwise returns the single next step. This tool does not create a proof.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • proofable_verify_preparePrepare a signature request for the selected Proofable checks.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Prepare a signature request for the selected Proofable checks. Returns the exact signing string, timestamp, chain, and hosted fallback. This call does not submit the check or create a proof.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • proofable_verify_submitSubmit a signed Proofable check using the same wallet, checks, data, and chain used to prepare it, plus the returned signing timestamp and signature.Reads text others writeNo findings

    Why it is in this group

    • The name "proofable_verify_submit" says "submit": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Submit a signed Proofable check using the same wallet, checks, data, and chain used to prepare it, plus the returned signing timestamp and signature. Creates a proof only when verification succeeds.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 3Show 3 read-only tools
  • proofable_contextReturn the signed-in Proofable profile and its current read-only context: proof index, agents, permissions, and verifier summary.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Return the signed-in Proofable profile and its current read-only context: proof index, agents, permissions, and verifier summary. Use once after sign-in.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • proofable_proofs_getRead a proof by qHash or search proofs by scope, tags, verifier, or text.No findings

    Why it is in this group

    • The name "proofable_proofs_get" says "get": a word for reading.
    Description, as the server wrote it
    Read a proof by qHash or search proofs by scope, tags, verifier, or text. With no filter, returns an index hint; scope=all pages metadata. Use include=content for proof bodies and includeComments with qHash for discussion. Omit identifier when signed in.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • proofable_verifiers_catalogReturn supported check definitions with the inputs and networks each requires.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Return supported check definitions with the inputs and networks each requires.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, OAuth metadata published

Looked at Nov 20, 2026, 19:09 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
401
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
yes
resource_metadata in WWW-Authenticate
https://mcp.proofable.me/mcp/.well-known/oauth-protected-resource
RFC 9728 protected resource metadata
https://mcp.proofable.me/mcp/.well-known/oauth-protected-resource
Authorization servers
https://proofable.me
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no

Posture changes

  1. Nov 13, 2026
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://mcp.proofable.me/mcp/.well-known/oauth-protected-resource
    • RFC 9728 protected resource metadata: https://mcp.proofable.me/.well-known/oauth-protected-resource/mcp to https://mcp.proofable.me/mcp/.well-known/oauth-protected-resource

Findings

Matches of fixed checks, with the text they matched.

2 warn1 info
  • The server marks "proofable_verify_or_guide" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "resolve": a word for reading.

    What this check looks for
  • The server marks "proofable_agent_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "proofable_agent_link" says "link": a word for a change.

    What this check looks for
  • The input schema at properties.skills.description mentions "credential".

    Matched text

    inputSchema.properties.skills.description: "...(not a secret, not an OAuth token, not credential material)."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 2 -> 0 (and 4 more).View diff
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://mcp.proofable.me/mcp/.well-known/oauth-protected-resource
    • RFC 9728 protected resource metadata: https://mcp.proofable.me/.well-known/oauth-protected-resource/mcp to https://mcp.proofable.me/mcp/.well-known/oauth-protected-resource
  2. Tools8 added.+8 addedView diff

Install

Pinned to version 0.1.12. Values in angle brackets are yours to fill in.

claude mcp add --transport http proofable https://mcp.proofable.me/mcp
claude mcp add --transport http proofable https://mcp.proofable.me/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__proofable__proofable_context",
      "mcp__proofable__proofable_verifiers_catalog",
      "mcp__proofable__proofable_proofs_get"
    ],
    "ask": [
      "mcp__proofable__proofable_proofs_check",
      "mcp__proofable__proofable_verify",
      "mcp__proofable__proofable_verify_prepare",
      "mcp__proofable__proofable_verify_submit",
      "mcp__proofable__proofable_verify_or_guide",
      "mcp__proofable__proofable_agent_link",
      "mcp__proofable__proofable_agent_create",
      "mcp__proofable__proofable_agent_mount"
    ],
    "deny": [
      "mcp__proofable__proofable_proofs_update"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as proofable. Review it before you use it.

Capability tags behind 4 rules
  • mcp__proofable__proofable_verify untrusted-input
  • mcp__proofable__proofable_verify_prepare untrusted-input
  • mcp__proofable__proofable_verify_submit untrusted-input
  • mcp__proofable__proofable_proofs_update untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.proofable/mcp/verify?hash=fed52436f827ad1ab2c9b34310ae2c3c79f2cdcfeab6a0f795d434df11f8e17f" | jq -e '.changed == false'

Pinned hash fed52436f827, from Nov 7, 2026, 05:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.proofable/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.proofable/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.proofable/mcp.svg)](https://radar.anlyon.com/servers/io.github.proofable/mcp)

Source: MCP Registry · repository. Synced Nov 17, 2026, 22:18 UTC.

Proofable MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Proofable MCP server safe?

No scan can promise that. What its definitions show: 12 tools, 9 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Proofable MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: proofable_proofs_update.

Can the Proofable MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Proofable MCP server have?

12 tools: 1 destructive, 8 write, 3 read. proofable_proofs_update, proofable_proofs_check, proofable_verify, proofable_verify_prepare, proofable_verify_submit, proofable_verify_or_guide, proofable_agent_link, proofable_agent_create and 4 more.

Does the Proofable MCP server need sign-in or OAuth?

Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.

Does the Proofable MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Proofable MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 7, 2026. Every change is on this page and in its Atom feed.