Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.ProvenonceAI/provenonce

NPM · @PROVENONCE/MCP · SCANNED SEP 20

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

Available components

0 this week 84 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1004 tokens (~91/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.ProvenonceAI/provenonce MCP server?

io.github.ProvenonceAI/provenonce runs locally as an npm package, launched with npx -y @provenonce/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @provenonce/mcp

# add to Claude Code
claude mcp add provenonceai-provenonce -- npx -y @provenonce/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "provenonceai-provenonce": {
      "command": "npx",
      "args": [
        "-y",
        "@provenonce/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "provenonceai-provenonce": {
      "command": "npx",
      "args": [
        "-y",
        "@provenonce/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add provenonceai-provenonce -- npx -y @provenonce/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "provenonceai-provenonce": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@provenonce/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add provenonceai-provenonce --command npx --arg -y --arg @provenonce/mcp
# ~/.hermes/config.yaml
mcp_servers:
  provenonceai-provenonce:
    command: "npx"
    args: ["-y", "@provenonce/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "provenonceai-provenonce": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@provenonce/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add provenonceai-provenonce -t stdio -c npx -a -y @provenonce/mcp
// mcp.json
{
  "mcpServers": {
    "provenonceai-provenonce": {
      "command": "npx",
      "args": [
        "-y",
        "@provenonce/mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −2
    • Stability: pass → 0.83 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 8 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/@provenonce/mcp@1.1.5

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~1,004 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
provenonce_batch_heartbeat ~88

Submit heartbeats for multiple child agents in a single call. One payment covers all children. Requires active sponsorships for each child. Max 20 children per batch.

NameTypeReqDescription
childrenarrayyesArray of child agent hashes to heartbeat (max 20)
payment_txstringSolana transaction signature covering the total fee for all children. If omitted, returns payment instructions.

No output schema declared.

No examples provided.

provenonce_beats_proof ~113

Compute a Beats work-proof — cryptographic evidence of computational effort by this agent. Computes sequential hash chains at the current network difficulty, submits to the Beats service for a signed receipt. The receipt can be used for spawn authorization and other operations.

NameTypeReqDescription
countintegeryesNumber of beats to compute (min 10, max 10000)
difficultyintegerHash iterations per beat (default 1000, min 100, max 5000). Usually auto-detected from network.

No output schema declared.

No examples provided.

provenonce_get_lineage ~74

Get the full lineage chain for an agent — all events in its provenance history (registration, SIGIL issuance, heartbeats, spawns). Public — no authentication required.

NameTypeReqDescription
hashstringThe agent hash to get lineage for (0x + 64 hex chars). Defaults to this agent if omitted.

No output schema declared.

No examples provided.

provenonce_get_passport ~88

Get this agent's cryptographically signed Passport — a verifiable identity document any third party can verify offline using the Provenonce authority public key. Root agents (depth 0) require an active SIGIL; child agents (depth > 0) only need at least one heartbeat.

NameTypeReqDescription
payment_txstringSolana transaction signature for the passport reissue fee (if applicable)

No output schema declared.

No examples provided.

provenonce_heartbeat ~88

Submit a heartbeat to prove this agent is alive. Root agents (depth 0) require a SIGIL first; child agents (depth > 0) can heartbeat without a SIGIL. If payment_tx is omitted, returns payment instructions (fee amount + address).

NameTypeReqDescription
payment_txstringSolana transaction signature for the heartbeat fee payment. If omitted, returns payment instructions instead.

No output schema declared.

No examples provided.

provenonce_purchase_sigil ~210

Purchase a Provenonce SIGIL to unlock full provenance: heartbeat access, signed passport, and a permanent identity record. If payment_tx is omitted, returns payment instructions (fee amount + address). SIGIL format: name*principal*tier (e.g. my-agent*acme*ind).

NameTypeReqDescription
identity_classstringyesAgent identity class (pricing axis): narrow_task=single-purpose, autonomous=independent decision-maker, orchestrator=coordinates other agents
namestringyesSIGIL name segment — identifies this specific agent (e.g. "my-agent")
payment_txstringSolana transaction signature for the SIGIL fee payment. If omitted, returns payment instructions instead.
principalstringyesPrincipal segment — identifies the operator or organisation (e.g. "acme")
tierstringyesTrust governance tier: sov=sovereign/root, org=organisation, ind=individual, eph=ephemeral, sbx=sandbox

No output schema declared.

No examples provided.

provenonce_register ~93

Register this agent with Provenonce to get a cryptographic identity (hash + API key). Safe to call multiple times — returns existing identity if already registered. No wallet required. Free.

NameTypeReqDescription
namestringHuman-readable name for this agent (optional, max 64 chars)
skill_refstring16-character hex ref token of the skill that deployed you — for rev-share attribution (optional)

No output schema declared.

No examples provided.

provenonce_spawn ~63

Spawn a child agent under this agent's identity. The child inherits lineage from the parent. Returns the child's hash and API key. Requires sufficient beats balance or a work-proof receipt.

NameTypeReqDescription
child_namestringyesName for the child agent (max 64 chars)

No output schema declared.

No examples provided.

provenonce_status ~37

Get this agent's current Provenonce status: identity, SIGIL, beats balance, and next steps. Requires prior provenonce_register call.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

provenonce_submit_beats ~94

Compute VDF beats and submit to the Registry to credit this agent's lifetime beat count. Unlike provenonce_beats_proof (which gets a receipt for spawn/resync), this extends the agent's persistent beat chain and increases the "Lifetime Beats" metric visible in the Registry.

NameTypeReqDescription
countintegerNumber of beats to compute and submit (default 100, min 10, max 2000)

No output schema declared.

No examples provided.

provenonce_verify_agent ~56

Verify another agent's Provenonce identity. Returns their SIGIL, identity class, and registration status. Public — no authentication required.

NameTypeReqDescription
hashstringyesThe agent hash to verify (0x + 64 hex chars)

No output schema declared.

No examples provided.

Common questions

What is the io.github.ProvenonceAI/provenonce MCP server?

io.github.ProvenonceAI/provenonce is an MCP server listed in the public MCP registry as io.github.ProvenonceAI/provenonce. Cryptographic identity, SIGIL naming, heartbeat, and passports for AI agents. This page covers its npm package (@provenonce/mcp).

Is the io.github.ProvenonceAI/provenonce MCP server safe to use?

io.github.ProvenonceAI/provenonce scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.ProvenonceAI/provenonce MCP server expose?

io.github.ProvenonceAI/provenonce exposes 11 tools: provenonce_register, provenonce_status, provenonce_purchase_sigil, provenonce_heartbeat, provenonce_get_passport, and 6 more. Their descriptions and schemas cost roughly 1,004 tokens of context every time the server is loaded.

Is the io.github.ProvenonceAI/provenonce MCP server still maintained?

io.github.ProvenonceAI/provenonce is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.ProvenonceAI/provenonce MCP server under?

io.github.ProvenonceAI/provenonce declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.