Skip to main content
Glama
arcusid

arcid-mcp

by arcusid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to arcid-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      -

    • 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

    • Kawal

      PugarHuda
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets you probe ERC-8004 agents on BNB Smart Chain by calling their declared MCP or A2A endpoints, checking payment requirements, reading on-chain reputation authorship, and finding agents by description.
      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
    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

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource or action: search_agents for discovery, get_agent for full records, get_agent_feedback and get_agent_validations for specific sub-resources, and get_registry_stats/get_indexer_health for operational context. There is no overlap or ambiguity in purpose.

    Naming Consistency5/5

    All tools use snake_case with a consistent verb_noun pattern, predominantly get_* with a single search_* verb that appropriately reflects its discovery function. No mixed conventions or vague names.

    Tool Count5/5

    Six tools is well-scoped for a read-only directory and lookup service, with each tool earning its place without redundancy. The count sits comfortably in the ideal 3-15 range.

    Completeness4/5

    The surface covers agent search, retrieval, feedback, validations, aggregate stats, and indexer health, which is strong for a read-only index. Minor gaps exist, such as no global feedback search or batch agent retrieval, but core workflows are fully supported.

    Resources