Passport
Issue portable Ed25519 identities and signed manifests so your agents have cryptographic credentials you can move between environments.
Overview
ScopeBlind Passport is a MCP server for the Build phase that provides portable Ed25519 cryptographic identity and signed manifests for AI agents via stdio.
What is this MCP server?
- npm package @scopeblind/passport v0.4.3 with stdio MCP transport
- Ed25519 keypairs and signed manifests for portable AI agent identity
- Source in scopeblind/ScopeBlindD2 packages/passport on GitHub
- Foundation for ScopeBlind receipt and policy flows used with protect and verify servers
- npm package @scopeblind/passport version 0.4.3
- GitHub source: scopeblind/ScopeBlindD2 (packages/passport)
What problem does it solve?
Agents calling tools across MCP gateways lack a portable, verifiable identity, so audits and trust boundaries collapse into opaque API keys.
Who is it for?
Builders hardening Claude Code or multi-MCP setups who want agent-native identity before adding policy gates and receipt verification.
Skip if: Teams that only need a single SaaS OAuth login with no signed agent artifacts or offline verification story.
What do I get? / Deliverables
After install, your agent stack can create and carry Ed25519 identities and manifests that downstream ScopeBlind tools can sign and verify.
- Ed25519 key material and signed manifests usable across agent sessions
- Identity artifacts compatible with ScopeBlind Protect receipts and Verify checks
- Documented agent principal for Cedar policies and gateway configuration
Recommended MCP Servers
Journey fit
Agent identity belongs in Build while you wire MCP tools, hooks, and automation—the credential layer ships with the agent stack, not after launch marketing. Agent-tooling is the shelf for MCP servers that extend what Claude Code and peers can trust and authenticate as first-class actors.
How it compares
Cryptographic agent-identity MCP, not a hosted LLM or generic secrets vault UI.
Common Questions / FAQ
Who is com.scopeblind/passport for?
Solo developers and small teams shipping agent workflows who need Ed25519 keypairs and signed manifests exposed to the model through MCP.
When should I use com.scopeblind/passport?
Use it during build when you are defining how agents identify themselves to gateways, hooks, and other ScopeBlind security MCP servers.
How do I add com.scopeblind/passport to my agent?
Install @scopeblind/passport from npm, add a stdio MCP server entry in Claude Code or Cursor pointing at the package binary, then invoke identity tools from your agent session.