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: verifiable priority.
-
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 sovereigndid: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.
Metadata
Release files for deusproof-mcp 0.3.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| deusproof_mcp-0.3.4.tar.gz | 13.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| deusproof_mcp-0.3.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.1 kB
Release files / deusproof_mcp-0.3.4.tar.gz
| Download URL | deusproof_mcp-0.3.4.tar.gz |
|---|---|
| Size | 13.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
963b4208fd7e61560159bfe028c5ea27f5cacbd13850b9c22dc5129a57e157c4
|
|
BLAKE2b-256 checksum How to use checksums |
96f2a3b2784d54732abea9c0144ddc6e98458a70664c8e4095d216f84d4ca6c7
|
| 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 Sep 23, 2026.
Transparency logRelease files / deusproof_mcp-0.3.4-py3-none-any.whl
| Download URL | deusproof_mcp-0.3.4-py3-none-any.whl |
|---|---|
| Size | 12.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9e51b20ecdb0a0baf9ac3fd474b6cb74c94681b1ebb1397f249487e456abbb64
|
|
BLAKE2b-256 checksum How to use checksums |
5b059bba0bfdc4ac910a019663079eb67e38fd17fee4e6c0e541411524745384
|
| 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 Sep 23, 2026.
Transparency log