Provenonce MCP Server

Cryptographic identity, SIGIL naming, heartbeat, and passports for AI agents.

Local serverstdioPython

What is the Provenonce MCP server?

Provenonce MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Cryptographic identity, SIGIL naming, heartbeat, and passports for AI agents.

What you get

Add this skill to your agent and it gets: - A permanent cryptographic hash (identity) - A SIGIL (verified identity class + tier) - A signed Passport (verifiable offline by any third party) - Heartbeat (continuous liveness proof) - Beats proofs (evidence of computational work) - Lineage (full ancestry chain)

What the assistant can call

Once Provenonce is connected, these are the calls the assistant has available:

  • provenonce_register — Auto-register agent, get hash + API key
  • provenonce_status — Full current state (SIGIL, balance, hints)
  • provenonce_purchase_sigil — Buy SIGIL, unlock heartbeat + passport
  • provenonce_heartbeat — Submit liveness proof
  • provenonce_batch_heartbeat — Heartbeat multiple children in one call
  • provenonce_get_passport — Get signed identity document
  • provenonce_beats_proof — Compute work proof, get receipt (for spawn/resync)
  • provenonce_submit_beats — Compute VDF beats and credit lifetime beat count
  • provenonce_verify_agent — Check another agent's identity
  • provenonce_spawn — Spawn a child agent
  • provenonce_get_lineage — Get full ancestry chain

Configuration and credentials

You will need 4 environment variables: PROVENONCE_API_KEY, PROVENONCE_AGENT_HASH, PROVENONCE_SKILL_REF, PROVENONCE_REGISTRY_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Provenonce's toolset — provenonce_register, provenonce_status, provenonce_purchase_sigil and 8 more — is a fair guide to whether it matches your workflow. It is maintained by ProvenonceAI; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Provenonce's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Provenonce.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the provenonce mcp server does with a few real requests.

Available tools

ToolWhat it does
provenonce_registerAuto-register agent, get hash + API key
provenonce_statusFull current state (SIGIL, balance, hints)
provenonce_purchase_sigilBuy SIGIL, unlock heartbeat + passport
provenonce_heartbeatSubmit liveness proof
provenonce_batch_heartbeatHeartbeat multiple children in one call
provenonce_get_passportGet signed identity document
provenonce_beats_proofCompute work proof, get receipt (for spawn/resync)
provenonce_submit_beatsCompute VDF beats and credit lifetime beat count
provenonce_verify_agentCheck another agent's identity
provenonce_spawnSpawn a child agent
provenonce_get_lineageGet full ancestry chain

How to install the Provenonce MCP server

{
  "mcpServers": {
    "provenonce": {
      "command": "npx",
      "args": ["-y", "@provenonce/mcp"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
PROVENONCE_API_KEYCredential the server authenticates with.Yes
PROVENONCE_AGENT_HASHConfiguration value read at startup.Optional
PROVENONCE_SKILL_REFConfiguration value read at startup.Optional
PROVENONCE_REGISTRY_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Provenonce to provenonce register.
  • Use Provenonce to provenonce status.
  • Use Provenonce to provenonce purchase sigil.

Frequently asked questions

It connects Provenonce to MCP-compatible AI assistants such as Claude and Cursor, exposing 11 tools (provenonce_register, provenonce_status, provenonce_purchase_sigil, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Provenonce directly.