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

    • 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

    • Synergy MCP

      Ir0nBeard
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes a live catalogue of specialist tools as MCP endpoints and returns x402 payment challenges for each call, letting agents pay per use in USDC from their own wallet without subscriptions or API keys.
      MIT

    • a2a-x402-mcp-services

      Disseveru
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to access production-grade paid MCP tools with real on-chain x402 v2 settlement, including EVM wallet risk scoring, payload normalization, and facilitator discovery, all discoverable via Bazaar-compatible metadata.
      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

    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

    ActivityStale
    ResponsivenessUnresponsive

    Resources