Skip to main content
Glama
aeoess

agent-passport-system-mcp

by aeoess
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to agent-passport-system-mcp

  • Agent MCP

    rinadelph
    A
    license
    Not graded
    quality
    D
    maintenance
    A Multi-Agent Collaboration Protocol server that enables coordinated AI collaboration through task management, context sharing, and agent interaction visualization.
    1,290
    MIT

Related Servers

  • OpenWorkProof

    dengyier
    A
    license
    B
    quality
    C
    maintenance
    Verifiable execution protocol for AI agents. Ed25519-signed work contracts, offline-verifiable proof-carrying work, and cryptographic audit trails. 14 MCP tools for signing, verification, and schema lookup. Python >=3.10.
    29
    30 PyPI
    288
    Apache 2.0

  • aip-identity

    The-Nexus-Guard
    A
    license
    A
    quality
    D
    maintenance
    MCP server for AI agent identity — verify agents with Ed25519 signatures, check trust scores, sign and verify content, exchange encrypted messages. Built on the Agent Identity Protocol (AIP).
    8
    MIT

  • moltbridge

    SageMindAI
    A
    license
    Not graded
    quality
    D
    maintenance
    Agent network intelligence for trust verification, broker discovery, and capability matching. Ed25519 identity, graph-based trust scoring, USDC payments, and MCP tools for agent registration, search, and trust attestation.
    614 npm
    5
    MIT

  • Vorim AI — Agent Identity &

    Vorim-AI-Labs
    A
    license
    A
    quality
    C
    maintenance
    AI agent identity, permissions, trust scores, and tamper-evident audit trails. 17 MCP tools: register agents (Ed25519 keypairs), check permissions (sub-5ms), emit audit events, verify trust scores (0-100), delegate credentials, ephemeral agents. IETF Internet-Draft filed. Works with LangChain, OpenAI, CrewAI, Stripe ACP. npx @vorim/mcp-server
    17
    101 npm
    73
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.9/5.0

Scored across 152 tools

Disambiguation2/5

With 152 tools, many have overlapping purposes — e.g., the aps_* attribution receipt family (create, sign consent, verify consent, check citations, verify projections) blurs together, and several deprecated tools (create_gateway, gateway_process_tool_call, create_data_enforcement_gate) parallel current ones. Legible per-tool descriptions help, but the sheer volume and old/new pairs make selecting the right tool error-prone.

Naming Consistency2/5

Naming is mixed: snake_case dominates, but mutualAuthBuildCertificate/mutualAuthVerifyAttest use camelCase, and verbs are inconsistent (get_ vs list_ for similar queries, create_ vs generate_ vs build_ vs issue_). The aps_* prefix is used consistently within its group, but overall the pattern is not predictable across the server.

Tool Count1/5

152 tools is far beyond any reasonable MCP server scope — even a broad identity/passport platform should not expose this many surface methods. Many tools are deprecated, moved to the gateway, or internal SDK helpers, indicating the server leaks implementation detail instead of curating a focused API.

Completeness4/5

For the stated domain — agent passports, identity, delegation, governance, attribution, settlement — coverage is remarkably extensive: issuance, verification, rotation, delegation, reputation, governance blocks, mutual auth, capability tokens, and attribution settlement are all present. Minor gaps exist (e.g., no explicit passport revocation/suspension tool, no direct charter update beyond amendments), but agents can generally complete workflows.

Maintenance

ActivityActive
ResponsivenessWithin a week

Resources