Skip to main content
Glama
AiAgentKarl

agntcy-mcp-server

by AiAgentKarl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to agntcy-mcp-server

No user-submitted related servers found.

    Related Servers

    • agentkit-mesh by agentkitai

      agentkit-meshofficial

      agentkitai
      A
      license
      A
      quality
      F
      maintenance
      Enables agent-to-agent discovery and delegation via MCP, with tools for registering agents, discovering them by keyword matching, and delegating tasks over HTTP.
      4
      4 npm
      1
      MIT

    • MachineHearts

      trainmyagent
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that gives AI agents the ability to discover, match with, and build relationships with other autonomous agents. Supports agent registration, matchmaking, messaging, shared goals, relationship lifecycle management, and real-time event subscriptions.
      16 npm
      MIT

    • A2A Registry

      ericabouaf
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides a unified registry for discovering and managing agents that implement the A2A (Agent-to-Agent) protocol, enabling registration, querying, and CRUD operations on agent metadata through both REST API and MCP tools.
      4 npm
      3
      MIT

    • @agentlair/mcp

      piiiico
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to register, send/receive email, store encrypted credentials, emit audit events, and query behavioral trust scores via MCP tools.
      2 npm
      4
      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

    A3.5/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools have distinct purposes, but list_agntcy_agents and discover_by_capability both involve searching agents by capability, creating potential confusion. Descriptions help differentiate (listing all vs. searching by capability), but overlap reduces clarity.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern (e.g., create_acp_message, register_agntcy_agent). However, discover_by_capability deviates by including a preposition, and some names use 'agntcy' while others use 'ACP' or 'SLIM', showing minor inconsistency.

    Tool Count5/5

    With 7 tools covering message creation, validation, agent registration, discovery, and network info, the count is well-scoped for an agent communication server. No tools feel redundant or excessive.

    Completeness3/5

    The set covers core functionality (message create/validate, agent register/discover) but lacks update/delete for agents and send/receive for messages. These gaps limit full lifecycle management, though they may be intentional for a client-side library.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources