Provenonce
Give shipped AI agents cryptographic identity, SIGIL names, heartbeats, and passports so clients and other services can verify who is calling.
Overview
Provenonce is an MCP server for the Ship phase that gives AI agents cryptographic identity, SIGIL naming, heartbeat checks, and passports over stdio.
What is this MCP server?
- Cryptographic agent identity and SIGIL naming for stable, verifiable agent handles
- Heartbeat signaling so operators can detect stale or impersonated agent sessions
- Agent passports for presenting trust metadata over MCP tool calls
- stdio npm package @provenonce/mcp (v1.1.5) for Claude Code, Cursor, and other MCP hosts
- Server version 1.1.5
- npm package identifier @provenonce/mcp
- Transport: stdio
What problem does it solve?
You cannot prove which agent spoke or whether an autonomous worker is still legitimate once multiple MCP clients and deployments share the same surface area.
Who is it for?
Indie builders shipping multi-tenant or customer-facing agents who need attributable, monitorable agent identity beyond a bare API key.
Skip if: One-off local coding sessions with no external users and no requirement to prove agent provenance.
What do I get? / Deliverables
After registering Provenonce in your MCP config, agents can expose verifiable identity and liveness signals that other tools and services consume through standard MCP calls.
- Registered SIGIL names and agent passports reachable via MCP tools
- Heartbeat endpoints agents can update for liveness monitoring
- Documented stdio MCP server block for your agent host
Recommended MCP Servers
Journey fit
How it compares
MCP identity and attestation server, not a general-purpose OAuth provider or a coding skill.
Common Questions / FAQ
Who is Provenonce MCP for?
Solo and small teams shipping AI agents who want cryptographic identity, naming, and heartbeat signals exposed to MCP-capable hosts like Claude Code or Cursor.
When should I use Provenonce MCP?
Use it during ship and security prep when agents talk to users, other agents, or external APIs and you need passports and liveness instead of anonymous tool access.
How do I add Provenonce to my agent?
Install @provenonce/mcp from npm, add a stdio MCP server entry pointing at that package in your host config, then follow provenonce.dev/mcp-skill for SIGIL and passport setup.