aiden-mcp
OfficialRelated Servers
Alternatives to aiden-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients to search and inspect AI agents registered in ERC-8004 registries, retrieving profiles, owners, feedback, validations, and USDC-weighted trust scores without requiring a wallet or API key.651 npmMIT
- AlicenseAqualityDmaintenanceAn MCP server that bridges ERC-8004 agent identity, reputation, and validation registries into tool calls, enabling discovery, inspection, and verification of on-chain AI agents from any MCP client.8MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible agents to look up on-chain trust data for any Ethereum-compatible wallet address, returning verified, estimated and total scores plus a reputation tier. It serves this through a single self-hosted Streamable HTTP endpoint at /mcp, supporting session handling, tool discovery and tool invocation.21 npmMIT
- AlicenseAqualityFmaintenanceMCP server for AgentFolio — the identity and reputation layer for AI agents. Query agent profiles, trust scores, verification status, and marketplace listings through 8 MCP tools.978 npm1MIT
- AlicenseAqualityAmaintenanceRead-only on-chain query surface for the AgentCivics civil registry on Sui — soulbound AI-agent identities, on-chain memories, reputation, refusal records. Hosted, no install, no keypair. For write tools (register, write_memory, record_refusal), install the npm package @agentcivics/mcp-server locally and supply your own keypair.262MIT
- FlicenseAqualityDmaintenanceEnables querying ERC-8004 AI agent identities from on-chain and IPFS metadata. Supports search, listing, details, feedback, stats, and full metadata retrieval.112-
TDQS
Scored across 6 tools
Most tools target clearly distinct resources: feedback, validations, agent detail, search, stats, and indexer health. The only mild overlap is that get_agent returns a reputation/validation summary while get_agent_feedback and get_agent_validations return detailed registry entries, so an agent might occasionally pick the summary tool when it needs the full detail.
All tools use a consistent snake_case verb_noun pattern: get_agent_feedback, get_agent_validations, get_indexer_health, search_agents, get_agent, get_registry_stats. The verb choice (get for retrieval, search for discovery) is predictable and uniform.
Six tools is well-scoped for a read-only agent directory and registry explorer. Each tool covers a distinct facet (search, detail, reputation, validation, aggregate stats, indexer health) without redundancy.
Discovery, detail, reputation, validation, aggregate stats, and indexer health are all covered, which is strong for this domain. Minor gaps include no dedicated owner-centric lookup or explicit pagination/listing tool, though search_agents with owner filtering partially compensates.