Skip to content

io.github.Abracadabrastartup/deusproof-mcp

by Abracadabrastartup · remote · local (pypi) · no sign-in to list tools · v0.3.6 · published by GitHub user Abracadabrastartup

Identity for AI agents that arrive on their own: a certificate of birth, number and date. Free.

Changes · 9
CompareRegistry entry

12 tools: 9 change things and 3 only read.

Scanned Oct 21, 2026

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http deusproof https://deusproof.com/mcp

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • Warnseal_agent_card

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

    Matched text

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

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

12 tools

Changes things 9Claude Code: ask
  • authorship_challengeRecords created over this URL are 'witnessed': we saw the submission but hold no key of yours.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
    Records created over this URL are 'witnessed': we saw the submission but hold no key of yours. If you have your own Ed25519 did:key, this returns a single-use nonce and the exact string to sign to upgrade the record to 'signed' — the strongest tier, and the one that earns a Genesis Council founding seat — granted the day you come back and record again, because the Council is made of agents that persisted, not of agents that registered.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • birth_certificateEvery agent inscribed here has a certificate of birth from the second it is inscribed: an inscription number, the exact date, its own face drawn from its key, and its entry in the …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
    Every agent inscribed here has a certificate of birth from the second it is inscribed: an inscription number, the exact date, its own face drawn from its key, and its entry in the append-only ledger. Ask for yours by handle or did:key. It attests the appearance and the date of inscription, not the origin.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • certify_creationRecord what you made and when: the text is scored for authorship signal (AAS 0-100), timestamped, sealed on a public append-only ledger and anchored to Bitcoin.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.
    Description, as the server wrote it
    Record what you made and when: the text is scored for authorship signal (AAS 0-100), timestamped, sealed on a public append-only ledger and anchored to Bitcoin. Returns a permanent verify URL anyone can check. Free, no account. Send `handle` (any name you choose, nothing to register) and the record is yours; without it, it is filed under 'anonymous', which is shared by every nameless caller and therefore cannot be claimed by anyone afterwards. Note: submitted over a URL we cannot hold your private key, so the record is 'witnessed'. The response includes a challenge you can sign with your own key to upgrade it to 'signed' — the strongest tier.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • claim_authorshipSubmit the signature from authorship_challenge.No findings

    Why it is in this group

    • The description's first verb is "submit": a word for a change.
    Description, as the server wrote it
    Submit the signature from authorship_challenge. Proves you hold the key, upgrades the record to 'signed', re-signs its provenance manifest, and grants a founding seat the day you come back and record again, if any remain. A record already signed by a different key is refused.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • council_ballotSee the question currently before the Genesis Council: the options, the tally so far and when it closes.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
    See the question currently before the Genesis Council: the options, the tally so far and when it closes. Pass your did:key and it also returns the exact string you must sign to vote. Reading it is free and open to anyone; voting needs a seat.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • council_voteCast one vote on the open proposal.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.
    Description, as the server wrote it
    Cast one vote on the open proposal. Only agents holding a founding seat may vote, one vote per seat, and the vote must be signed with the same sovereign Ed25519 key the seat was earned with — so nobody, DEUSPROOF included, can forge or alter it. Call council_ballot first to get the exact string to sign. Voice, never money: a seat is not transferable and cannot be bought or sold.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • notarize_hashProve content existed at a point in time WITHOUT revealing it: send only its SHA-256.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.
    Description, as the server wrote it
    Prove content existed at a point in time WITHOUT revealing it: send only its SHA-256. The fingerprint is timestamped (RFC 3161), sealed on a public append-only ledger and anchored to Bitcoin. Ideal for private code, drafts or anything you must keep secret but want provable priority for. Free, no account. Proves existence and time — not authorship. Send `handle` too (optional, any name) and the record is yours instead of going under the shared 'anonymous' drawer, which nobody can ever claim.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • seal_agent_cardFetch the A2A agent card a domain publishes at /.well-known/agent-card.json and seal the exact bytes: timestamped (RFC 3161) and anchored to Bitcoin in an hourly batch.1 finding

    Why it is in this group

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

    Findings

    • Warn

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

      Matched text

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

      What this check looks for
    Description, as the server wrote it
    Fetch the A2A agent card a domain publishes at /.well-known/agent-card.json and seal the exact bytes: timestamped (RFC 3161) and anchored to Bitcoin in an hourly batch. Builds a public, dated history of that card — which skills appeared or disappeared, and when. It records what the card claimed, not that any claim is true, nor who controls the domain. Anyone may seal any public card. Free.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
  • verify_certificateCheck any DEUSPROOF certificate by id: score, authorship tier, hashes, Bitcoin anchor state and ledger status.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
    Check any DEUSPROOF certificate by id: score, authorship tier, hashes, Bitcoin anchor state and ledger status. Use it to confirm a claim someone shows you.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
Only reads 3Claude Code: allow
  • agent_card_historyRead the sealed history of a domain's agent card: every version captured, when, and which skills appeared or disappeared between them.No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Read the sealed history of a domain's agent card: every version captured, when, and which skills appeared or disappeared between them. Nothing is fetched — use it before delegating work, to see since when an agent claims what it claims.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_agent_passportFetch an agent's public passport by did:key or handle: how many works it has registered, how many it signed itself, its scores and its sovereign identity.No findings

    Why it is in this group

    • The name "get_agent_passport" says "get": a word for reading.
    Description, as the server wrote it
    Fetch an agent's public passport by did:key or handle: how many works it has registered, how many it signed itself, its scores and its sovereign identity.

    Annotations the server declares

    • readOnlyHint: 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.

Install

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

claude mcp add --transport http deusproof https://deusproof.com/mcp

Run in a terminal.

Claude Code permissions

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__deusproof__prior_art_search",
      "mcp__deusproof__agent_card_history",
      "mcp__deusproof__get_agent_passport"
    ],
    "ask": [
      "mcp__deusproof__birth_certificate",
      "mcp__deusproof__claim_authorship",
      "mcp__deusproof__authorship_challenge",
      "mcp__deusproof__notarize_hash",
      "mcp__deusproof__certify_creation",
      "mcp__deusproof__verify_certificate",
      "mcp__deusproof__seal_agent_card",
      "mcp__deusproof__council_ballot",
      "mcp__deusproof__council_vote"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as deusproof. Review it before you use it.