io.github.daedalusdevelopmentgroup/ddg-agent-services-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ddg_mcp_security_profileA | Return this MCP wrapper's local security controls and publication gates. |
| ddg_public_resource_indexA | List allowlisted DDG public manifests/docs available as MCP resources. |
| ddg_fetch_public_resourceC | Fetch an allowlisted DDG public manifest/doc by id or ddg:// URI with redaction and size caps. |
| ddg_list_servicesB | List DDG live/manual services from the public pricing and catalog surfaces. |
| ddg_list_modelsA | List local/free Ollama models and queryable paid/account-backed route labels. |
| ddg_list_local_runtime_optionsA | List free-seat status plus requestable local runtimes such as Ollama, llama.cpp, LM Studio, OpenAI-compatible servers, and vLLM. |
| ddg_quote_paymentC | Return the payment challenge for a supported DDG protected route without executing backend compute. |
| ddg_run_paid_modelA | Run a paid model/chat or agent-run route after caller supplies valid payment headers. |
| ddg_submit_orderA | Submit a paid operator-reviewed DDG order after caller supplies valid payment headers/proof. |
| ddg_request_ollama_modelC | Queue a local model/runtime request. This never auto-downloads by public request. |
| ddg_checkout_conformanceA | Return DDG's public checkout conformance profile without spending money. |
| ddg_agent_statusA | Return DDG's machine-readable service/rail/MCP status document. |
| ddg_skill_safety_scanA | Run the free static-only DDG AI skill/workflow safety scan. The scan never executes submitted code and redacts secret-like evidence. |
| ddg_order_statusB | Poll an agent-scoped DDG order status URL. |
| ddg_order_artifactB | Fetch an agent-scoped DDG order artifact when ready. |
| ddg_receipt_verify_designA | Describe the planned free receipt-verification tool contract. This is intentionally marked not-live until |
| ddg_security_service_catalogB | Return DDG's AI-agent cybersecurity service catalog. |
| ddg_tx_smoke_testB | Exercise the one-cent DDG transaction smoke-test route with caller-supplied payment headers. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| ddg_manifest_ai | DDG public AI manifest. |
| ddg_manifest_status | DDG public agent status manifest. |
| ddg_manifest_catalog | DDG public service catalog manifest. |
| ddg_manifest_pricing | DDG public agent pricing manifest. |
| ddg_manifest_checkout_conformance | DDG public checkout conformance profile. |
| ddg_manifest_cybersecurity_services | DDG public cybersecurity service catalog. |
| ddg_docs_llms | DDG llms.txt for AI-agent discovery. |
| ddg_docs_mcp_design | DDG MCP design notes for AI-agent clients. |
| ddg_openapi | DDG OpenAPI contract. |
TDQS
Scored across 18 tools
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.
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.
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.
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.