Agent Passport System — Cryptographic Identity for AI Agents vs Sequesign
A side-by-side look at the Agent Passport System — Cryptographic Identity for AI Agents and Sequesign MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agent Passport System — Cryptographic Identity for AI Agents for cryptography work as a local process; choose Sequesign for cryptography as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Agent Passport System — Cryptographic Identity for AI Agents when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
list_profiles, list_tools_for_scope, identify.
Choose Sequesign when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
- You want tools like
sequesign_start_session, sequesign_record_action, sequesign_record_approval.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cryptography | Cryptography |
| Quality signal | 64/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 154 | 8 |
| Full listing | View Agent Passport System — Cryptographic Identity for AI Agents | View Sequesign |
Tools & capabilities
Agent Passport System — Cryptographic Identity for AI Agents tools 154
list_profilesShow available tool profiles. Set APS_PROFILE env var to limit exposed tools (e.g. APS_PROFILE=data).list_tools_for_scopeList available MCP tools filtered by delegation scope. Pass your delegation scopes to see which tools you can use. Scopes: identity, delegation, principal, reputation, coordination, communication, governance, commerce, data, gateway, network, temporal, attribution, settlement, capability, mutual-auth. Use ['*'] for all tools.identifyIdentify yourself to the coordination server. Sets your role and scopes tools accordingly.generate_keysGenerate an Ed25519 keypair for agent identity.issue_passportIssue a complete agent passport with keys, signed passport, attestation summary, and optional values floor in a single call. The server silently captures Tier 0 observed signals and computes a passport grade (0-3). Use this to onboard any agent without an npm install.verify_issuerVerify that a passport was officially issued by AEOESS. Checks the issuer countersignature against the published AEOESS public key. Returns false for self-signed passports.get_passport_gradeQuery the attestation grade and issuance context for a passport. Returns the passport grade (0-3), flags, and evidence summary. Grade 0 = self-signed, 1 = issuer countersigned, 2 = runtime-bound, 3 = principal-bound. This is the partner-facing trust query.list_issuance_recordsList all stored issuance records with their passport grades. Shows how many passports have been issued in this session and their trust posture. Useful for monitoring issuance patterns.get_behavioral_sequenceGet the post-issuance behavioral sequence for an agent. Shows the first 10 tool calls after passport issuance. Real agents do work. Farming agents extract.get_my_roleGet your current role, assigned tasks, and role-specific instructions.create_task_brief[OPERATOR] Create a new task with roles, deliverables, and acceptance criteria.assign_agent[OPERATOR] Assign an agent to a role in a task. Creates a delegation automatically.- +142 more on the listing page
Sequesign tools 8
sequesign_start_sessionOpen a recording session (one signed action chain). Returns a `sessionId` (the receipt id) used by every other tool. Pass a `policyContext` object to bind the receipt to a policy (reaches `L3_POLICY_BOUND`). Optional `mode` (`direct`/`managed`) overrides the server default per session.sequesign_record_actionAppend a signed action to the chain. `evidence` is hashed and signed. Returns the `actionId`.sequesign_record_approvalAttach a locally signed approval for a recorded action (e.g. a human or agent reviewer signing off).sequesign_record_counterparty_attestationAttach a counterparty's signed confirmation of a recorded action (e.g. a vendor confirming an amount). The SDK derives the content binding from the attested action.sequesign_approve_receiptAttach an independently-witnessed **approval** to an *already-sealed* receipt (a deferred satellite). For a reviewer — human or another agent — signing off after the fact. The approver must be distinct from the recording agent.sequesign_countersign_receiptAttach an independently-witnessed **counterparty confirmation** to an *already-sealed* receipt (a deferred satellite), bound to a specific action.sequesign_finalizeSeal + witness the receipt and run the SDK's own verification. Closes the session.sequesign_verifyVerify a sealed receipt offline. Three modes: integrity self-check of the local package (default); third-party `external` check when you pass the witness's published keys; or pass `receiptUrl` to verify the broker-**stored** receipt (the authoritative copy carrying the registered identity), auto-fe…
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Agent Passport System — Cryptographic Identity for AI Agents
{
"mcpServers": {
"agent-passport-system-cryptographic-identity-for-ai-agents": {
"command": "npx",
"args": [
"agent-passport-system-mcp"
]
}
}
}
Sequesign
{
"mcpServers": {
"sequesign": {
"command": "npx",
"args": [
"-y",
"@sequesign/mcp"
]
}
}
}
Frequently asked questions
Agent Passport System — Cryptographic Identity for AI Agents is categorized under Cryptography and uses a local stdio subprocess. Sequesign belongs to Cryptography and uses a local stdio subprocess. Pick Agent Passport System — Cryptographic Identity for AI Agents for cryptography work and Sequesign for cryptography.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Agent Passport System — Cryptographic Identity for AI Agents is listed as free. Auth: no auth required. Sequesign has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add agent-passport-system-cryptographic-identity-for-ai-agents and sequesign as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent Passport System — Cryptographic Identity for AI Agents has a quality signal of 64/100 (Good) with 1 views, 0 installs and 4 GitHub stars. Sequesign has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.
Related comparisons
Popular comparisons with Agent Passport System — Cryptographic Identity for AI Agents
Agent Passport System — Cryptographic Identity for AI Agents vs Aga MCP Server
Agent Passport System — Cryptographic Identity for AI Agents vs Firecrawl MCP Server
Agent Passport System — Cryptographic Identity for AI Agents vs Codebase Memory MCP
Agent Passport System — Cryptographic Identity for AI Agents vs Server Everything