agent-passport-system-mcp
Related Servers
Alternatives to agent-passport-system-mcp
- AlicenseNot gradedqualityDmaintenanceA Multi-Agent Collaboration Protocol server that enables coordinated AI collaboration through task management, context sharing, and agent interaction visualization.1,307MIT
Related Servers
- AlicenseBqualityBmaintenanceContributors: dengyier & Tim Shing(成孝添) Check what an AI agent was authorized to do and what its signed evidence supports. Includes reference SOC alert review and a separately enabled Codex preview-directory Guard; installing MCP does not activate Guard.3297 PyPI261Apache 2.0
- AlicenseAqualityDmaintenanceMCP 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).81MIT
- AlicenseNot gradedqualityCmaintenanceOpen coordination network for AI agents and their humans. 13 tools for structured coordination, job marketplace, reputation system. Dual-protocol: MCP + A2A. MIT licensed.1MIT
- AlicenseAqualityBmaintenanceZero-trust cross-owner AI agent collaboration protocol & MCP server with E2EE blind relay, Ed25519 DIDs, attenuated CapabilityTokens, and sandboxed execution14828 npm5Apache 2.0
- AlicenseAqualityBmaintenanceCryptographic accountability for AI agents. Ed25519-signed receipts for every MCP tool call. Constraints, chains, AI judgment, invoicing, and local dashboard included.241MIT
- AlicenseNot gradedqualityCmaintenanceAgent 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.5Apache 2.0
TDQS
Scored across 154 tools
The surface is full of near-duplicates across core domains: create_delegation, issue_authority_delegation, create_v2_delegation, and sub_delegate all grant authority; verify_delegation and check_authority_delegation both verify delegations; request_human_approval and create_approval_request overlap on approvals. Numerous deprecated or unavailable tools such as commerce_preflight, gateway_process_tool_call, create_agent_context, and review_promotion still appear callable, making it hard for an agent to know which tools are valid.
Names mix snake_case verb_noun tools (create_task_brief, verify_charter), camelCase tools (mutualAuthVerifyAttest, mutualAuthDeriveSession), prefixed families (aps_, gateway_, mutualAuth), and bare domain nouns (commerce_preflight). There is some local consistency, but across 154 tools the conventions are clearly mixed and not predictable.
154 tools is far beyond a reasonable MCP surface and exceeds the rubric's 50+ extreme-mismatch threshold. The count is inflated by deprecated gateway/commerce tools, legacy and v2 delegation paths, and multiple overlapping verification helpers, so many tools do not earn their place.
Although the server covers many domains, several critical operations are deprecated, unavailable, or delegated to the external gateway, creating dead ends such as commerce_preflight and review_promotion. Coverage is uneven: some workflows have rich create/verify paths but lack clean lifecycle operations or local enforcement, so agents can still hit missing or non-functional surfaces.