Provenonce
Give autonomous agents a verifiable cryptographic identity, stable SIGIL names, heartbeats, and passports before they act on behalf of your product.
Overview
Provenonce is a MCP server for the Ship phase that issues cryptographic identity, SIGIL names, heartbeats, and passports so AI agents can be named and verified in your stack.
What is this MCP server?
- Cryptographic identity binding for AI agents via Provenonce MCP (stdio, npm @provenonce/mcp)
- SIGIL naming for stable, human- and machine-readable agent identifiers
- Heartbeat signaling to show an agent is alive and accountable over time
- Agent passports for portable, verifiable credentials across tools and sessions
- MCP server v1.1.4 with stdio transport for Claude Desktop and compatible hosts
- Server schema version 1.1.4 on npm identifier @provenonce/mcp
- Single stdio transport package in server.json
- Four capability themes: cryptographic identity, SIGIL naming, heartbeat, passports
What problem does it solve?
Solo builders cannot easily prove which agent instance acted, reuse a trusted identity across sessions, or show that an automation is still healthy without bolting on custom auth.
Who is it for?
Indie builders shipping multi-session agents, marketplaces, or copilots that need consistent naming and cryptographic identity without building identity from scratch.
Skip if: Teams that only run stateless one-shot prompts with no persisted agent role or no requirement to prove agent provenance.
What do I get? / Deliverables
After registering Provenonce MCP, your agent workflows can attach verifiable identity and heartbeat signals so downstream systems and you can trust who ran each action.
- Registered MCP server exposing identity, naming, heartbeat, and passport tools
- Agents addressable via SIGIL names with verifiable identity metadata
- Operational heartbeat channel for liveness checks on automated workers
Recommended MCP Servers
Journey fit
Identity and proof-of-agent controls belong on the Ship shelf because they harden how agents authenticate and are recognized before production exposure. Security is the canonical subphase for cryptographic identity, naming, and agent passport flows that reduce spoofing and untrusted automation.
How it compares
MCP identity and passport server, not a general coding skill or browser automation plugin.
Common Questions / FAQ
Who is io.github.jarekpiot/provenonce for?
Solo and small-team builders who deploy AI agents via MCP and need cryptographic identity, SIGIL naming, heartbeats, and passports rather than anonymous tool calls.
When should I use Provenonce MCP?
Use it during Ship when you are hardening agent access—before agents touch production APIs, user accounts, or third-party integrations that require accountable automation.
How do I add Provenonce to my agent?
Install the @provenonce/mcp npm package, add the MCP server to Claude Desktop or your MCP host with stdio transport, and follow provenonce.dev/mcp-skill for configuration.