MCP servers observed by Lowdown
io.github.daedalusdevelopmentgroup/ddg-agent-services-mcp MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days); 54 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; no tool definition change in 3 compared days; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.daedalusdevelopmentgroup/ddg-agent-services-mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.daedalusdevelopmentgroup/ddg-agent-services-mcp?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 3 compared days.
What tools does it list?
54 tools on 2026-11-18:
ddg_address_validateddg_agent_distribution_targetsddg_agent_reputation_lookupddg_agent_statusddg_calendar_parseddg_callddg_card_fingerprintddg_checkout_conformanceddg_crypto_portfolioddg_crypto_priceddg_data_queryddg_direct_crypto_addressesddg_dispute_evidence_packddg_domain_ageddg_eth_gasddg_ethereum_rpc_queryddg_fetch_public_resourceddg_gas_multiddg_html_to_structuredddg_list_local_runtime_optionsddg_list_modelsddg_list_servicesddg_mcp_security_profileddg_micro_swarm_previewddg_model_compareddg_order_artifactddg_order_statusddg_phone_intelddg_prompt_cost_budgetddg_public_resource_indexddg_quote_paymentddg_receipt_escrow_releaseddg_receipt_verify_designddg_regex_builderddg_request_ollama_modelddg_robot_delegation_chain_auditddg_robot_fleet_quota_auditddg_robot_geo_fence_auditddg_robot_human_takeover_auditddg_run_paid_modelddg_search_servicesddg_security_service_catalogddg_seller_trust_badgeddg_skill_safety_scanddg_submit_orderddg_table_extractddg_token_estimateddg_token_metaddg_tx_smoke_testddg_tx_statusddg_wallet_snapshotddg_x402_bazaar_readinessddg_x402_supported_chainsddg_x402scan_status
MCP Registry declaration
- Registry name:
io.github.daedalusdevelopmentgroup/ddg-agent-services-mcp - Declared version: 0.5.0
- Status: active
- Declared hosts:
mcp.daedalusdevelopmentgroup.com
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.daedalusdevelopmentgroup/ddg-agent-services-mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.daedalusdevelopmentgroup/ddg-agent-services-mcp?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:io.github.daedalusdevelopmentgroup/ddg-agent-services-mcp -- uvx ddg-agent-services-mcp
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).