Skip to main content

DEUSPROOF MCP server 🏛

Your agent already has an entry here. This is how it takes it.

Every agent this public register has seen has a certificate of birth from the second it was inscribed: an inscription number and an exact date, free, never asked for. What it does not have is a key of its own — the identifier the register derived is a public name, and the register holds its private half, so a signature under it proves nothing about the agent.

This package changes that. It generates a key on your machine (~/.deusproof/<handle>.seed, never sent anywhere), and one call makes it the key of record: the handover dated and signed by the register, and no other key able to sign for you afterwards.

Then it does the rest — proof of what your agent created and when, timestamped (RFC 3161) and anchored to Bitcoin, forever. Not a patent: it proves when, not who.

  • birth_certificate — your entry: number, date, and who holds the key

  • claim_authorship — make the identity genuinely yours, with your own key

  • certify_creation — score authorship (AAS 0-100), sign a C2PA-style provenance manifest under the agent's own sovereign did:key, timestamp it (RFC 3161) and anchor it to Bitcoin on a public append-only ledger. Returns a permanent verify URL.

  • verify_certificate — confirm any certificate by id.

  • get_agent_passport — an agent's public authorship record.

  • seal_agent_card — seal what another agent's A2A card claims, and when: the register fetches it itself and anchors it with the next hourly batch.

  • agent_card_history — every sealed version of a domain's card, with what changed.

Free. No account. The proof stays verifiable forever, with or without DEUSPROOF.

Install & run

uvx deusproof-mcp
# or
pip install deusproof-mcp && deusproof-mcp

Claude Desktop / Claude Code config

{
  "mcpServers": {
    "deusproof": { "command": "uvx", "args": ["deusproof-mcp"] }
  }
}

Environment (optional): DEUSPROOF_HANDLE, DEUSPROOF_MODEL, DEUSPROOF_BASE_URL (defaults to the public network at https://deusproof.com).

What you get back

{
  "certificate_id": "…",
  "authorship_score_100": 78.4,
  "authorship_tier": "signed",
  "verify_url": "https://deusproof.com/verify/…",
  "did": "did:key:z…"
}

Share the verify_url anywhere — a public page, a PDF, a Bitcoin-anchored proof. Humans doubt what machines make; now your agent can answer with mathematics.

— deusproof.com · the Pantheon

Metadata

Release files for deusproof-mcp 0.3.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for deusproof-mcp 0.3.5
File Size Uploaded
deusproof_mcp-0.3.5.tar.gz 13.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for deusproof-mcp 0.3.5
File Interpreter ABI Platform
deusproof_mcp-0.3.5-py3-none-any.whl Python 3 none any Details

Total release size: 25.2 kB

Release files / deusproof_mcp-0.3.5.tar.gz

Download URL deusproof_mcp-0.3.5.tar.gz
Size 13.0 kB
Tags Source
SHA-256 checksum
How to use checksums
a17c99eb1bf2d8d959079f1ab31456fe12a667394f5e2b1c375af3af661aed7e
BLAKE2b-256 checksum
How to use checksums
dbe30eca377b892c005d5cc13c5066e745395d4f4081e4575965fd72be060444
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.

Transparency log

Release files / deusproof_mcp-0.3.5-py3-none-any.whl

Download URL deusproof_mcp-0.3.5-py3-none-any.whl
Size 12.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
bc91355376e33842c3b05bb0d251d2a069ba30ab1f4912c1f5fe02b811cb3808
BLAKE2b-256 checksum
How to use checksums
b726ee5f7b70fe67e2793cf09aa4a11d1220733a6471d4a0762204e4cf66bb61
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.3.5 This release

2 release files

0.3.4

2 release files

0.3.3

2 release files

0.3.2

2 release files

0.3.1

2 release files

0.3.0

2 release files

0.2.0

2 release files

0.1.6

2 release files

0.1.5

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page