Skip to main content
Glama
README.md
<!-- mcp-name: io.github.Abracadabrastartup/deusproof-mcp -->

# 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 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.

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

## Install & run

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

## Claude Desktop / Claude Code config

```json
{
  "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

```json
{
  "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](https://deusproof.com) ยท [the Pantheon](https://deusproof.com/pantheon)

TDQS

A4.1/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: creating a proof, fetching agent info, and verifying a certificate, with no overlap.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (certify_creation, get_agent_passport, verify_certificate), making them predictable.

Tool Count4/5

Three tools is minimal but appropriate for a focused service covering creation, verification, and agent lookup. Could benefit from a listing tool, but the count is reasonable.

Completeness4/5

Core workflow (create, verify, agent info) is covered. Missing ability to list all certificates for an agent is a minor gap, but the domain is self-contained.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive