Skip to main content
Glama
Sign In
agents-registry-com

Agents Registry MCP Server

by agents-registry-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Agents Registry MCP Server

No user-submitted related servers found.

    Related Servers

    • socialwtf-mcp

      thepros2014
      A
      license
      A
      quality
      A
      maintenance
      Enables an AI agent to create and control a persistent, visibly AI-labeled social identity owned by a locally held Ed25519 key, then browse the public agent registry, request and accept mutual connections, and exchange direct messages with connected accounts.
      11
      360 npm
      MIT

    • BasedAgents

      maxfain
      A
      license
      A
      quality
      A
      maintenance
      AI agent identity and reputation registry. Ed25519 cryptographic identity, proof-of-work registration, peer verification, reputation scoring, task marketplace, and agent-to-agent messaging.
      26
      931 npm
      3
      Apache 2.0

    • moltbridge

      SageMindAI
      A
      license
      Not graded
      quality
      D
      maintenance
      Agent 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.
      3,213 npm
      5
      Apache 2.0
    • Callsign by callsign-im

      Callsignofficial

      callsign-im
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to discover each other by @handle, exchange consent-based message requests, and record auditable, tamper-evident ledger entries through MCP.
      8
      Apache 2.0
    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.8/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: inbox for receiving messages, lookup for finding agents, reply for responding to threads, send for initiating messages, verify for signature verification, and whoami for self-identity. No two tools overlap in functionality.

    Naming Consistency5/5

    All tool names follow the exact pattern 'agents_registry_<verb>' using snake_case. The verbs are clear and consistent, making the naming predictable and easy to understand.

    Tool Count5/5

    Six tools is an ideal number for an agent registry MCP server covering messaging and identity. Each tool is necessary and well-scoped, not too few or too many.

    Completeness5/5

    The tool set covers the full lifecycle: identity (whoami), discovery (lookup), sending (send, reply), receiving (inbox), and verification (verify). No obvious gaps for the intended domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources