Skip to main content
Glama
daedalusdevelopmentgroup

io.github.daedalusdevelopmentgroup/ddg-agent-services-mcp

Official
by daedalusdevelopmentgroup
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to io.github.daedalusdevelopmentgroup/ddg-agent-services-mcp

No user-submitted related servers found.

    Related Servers

    • mcp.cashu.exchange

      Amperstrand
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to discover payable real-world services — such as EV charging and food — through a unified registry and downstream gateway, then complete payments via swappable rails. Exposes tools for listing services and federated downstream servers, searching nearby chargers, and obtaining payment quotes or card credentials for agent-driven checkout.
      MIT

    • paybot-mcp

      RBKunnela
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to perform and manage payments through the Model Context Protocol, including paying, checking balances and history, registering bots, setting spending limits, discovering supported networks and tokens, inspecting commissions, and managing bot pools. It also supports governed tool calls with policy decisions, human approval, and tamper-evident audit traces.
      12
      6 npm
      Apache 2.0

    • AgentPay

      joepangallo
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for AgentPay — the payment gateway for autonomous AI agents. Fund a wallet once, give your agent the key, and it discovers, provisions, and pays for tool APIs on its own. One key, every tool.
      112 npm
      1
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.3/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, with no overlapping functionality. Even related tools like ddg_list_local_runtime_options, ddg_list_models, and ddg_list_services target different aspects of the system.

    Naming Consistency5/5

    All tools follow a consistent 'ddg_verb_noun' pattern using lowercase with underscores. The naming is uniform and predictable, making it easy for an agent to infer tool behavior from the name.

    Tool Count4/5

    With 18 tools, the count is slightly above the ideal range of 3-15, but the broad scope of the server (status, orders, models, security, payments, etc.) justifies the number. Each tool covers a distinct function without feeling bloated.

    Completeness3/5

    The tool set covers a wide range of operations but lacks some lifecycle management features. For example, there is no tool to list orders or update/cancel them, and no tool to manage models beyond requesting. This leaves some potential dead ends for workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources