A
licenseNot graded
qualityB
maintenanceEnables AI agents to manage ephemeral payment tokens with cryptographic spend mandates, risk scoring, catalog resolution, and automated bargaining through native MCP tools.
7
MIT
io.github.daedalusdevelopmentgroup/ddg-agent-services-mcp
OfficialRelated Servers
Alternatives to io.github.daedalusdevelopmentgroup/ddg-agent-services-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to manage Agentic Payment Protocol ephemeral tokens with cryptographic spend mandates, risk scoring, merchant catalog resolution, and automated bargaining through MCP tools.MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseAqualityBmaintenanceEnables 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.1220 npmApache 2.0
- AlicenseAqualityCmaintenanceEnables agents to call paid utilities for DNS/SSL checks, site status, summarization, keyphrase extraction, decision advice, data cleanup, claim verification, and grounding via per-call USDC payments over x402, with free discovery tools and no signup or API key.10MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to make per-call paid tool requests over HTTP 402, with request-bound payments and replay protection, while returning auditable provenance and self-checks for every answer.MIT
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
ActivitySlowing
ResponsivenessLimited data