Skip to main content
Glama
aiden-network

aiden-mcp

Official
by aiden-network
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to aiden-mcp

No user-submitted related servers found.

    Related Servers

    • web3-agents-mcp

      hanjoonchoe
      A
      license
      A
      quality
      B
      maintenance
      An 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.
      8
      MIT
    • @agentcivics/mcp-server by agentcivics

      @agentcivics/mcp-serverofficial

      agentcivics
      A
      license
      A
      quality
      A
      maintenance
      Read-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.
      26
      1
      MIT

    • ERC-8004 MCP Server

      wpank
      F
      license
      A
      quality
      D
      maintenance
      Enables querying ERC-8004 AI agent identities from on-chain and IPFS metadata. Supports search, listing, details, feedback, stats, and full metadata retrieval.
      11
      2
      -
    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

    A3.9/5.0

    Scored across 6 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources