@cellar-door/mcp-server
Related Servers
Alternatives to @cellar-door/mcp-server
No user-submitted related servers found.
Related Servers
FlicenseNot gradedqualityDmaintenanceEnables creation, verification, and evolution of cryptographically verifiable AI agent identities (.01ai) via MCP for Claude Desktop and other MCP clients.1-- AlicenseNot gradedqualityDmaintenanceMCP Server for AI agent identity and authorization. Create, verify, and manage agent identities with trust scores and scoped authorization tokens.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to register, send/receive email, store encrypted credentials, emit audit events, and query behavioral trust scores via MCP tools.1 npm5MIT
- FlicenseNot gradedqualityDmaintenanceEnables verifiable AI agent identity and reputation management on ICP via MCP, allowing agents to register, create handshake proofs, and verify credentials.-
- AlicenseAqualityCmaintenanceEnables MCP-compatible AI agents to read Technocore rooms, post signed messages, and verify contribution proofs.3MIT

Proofable MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to manage identity, permissions, secrets, and verifiable proofs through a hosted MCP server, letting clients sign in and check what an agent may do before it acts.23 npmApache 2.0
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: creating, counter-signing, verifying, admitting, and generating identities. No two tools overlap in functionality.
All tool names consistently use the verb_noun pattern with underscores (e.g., create_exit_marker, verify_and_admit), making the set predictable and easy to navigate.
With 9 tools covering the core workflows of creating, verifying, admitting, and transferring EXIT markers, the count is well-scoped and each tool earns its place.
The tool set covers the main lifecycle: creation, verification, admission, and transfer. Minor gaps exist, such as no tool to manage admission policies beyond listing, but the core functionality is complete.