DPX — Settlement & Intelligence for AI Agents
Server Details
Compliance-gated stablecoin settlement + x402 macro/ESG/climate intelligence for agents. 115 tools.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Server Listing
- dpx-mcp
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 115 tools
The 115-tool surface is massively overlapping: multiple settlement executors (settlement.execute, settlement.nl, computer_use.pay, batch_settle, card.settle, ramp.settle), multiple pre-flight gates (flow_check, oracle.settlement_gate, settlement.try), and several compliance/ESG/intelligence report tools that duplicate or nest one another. Some descriptions attempt distinctions, but an agent will frequently be unable to tell which tool is the correct one for a given task without deep protocol knowledge.
Most tools follow a readable namespace.action snake_case pattern (e.g. compliance.aml_screen, oracle.stability, invoice.create), with only a few unprefixed exceptions such as route, batch_settle, flow_check, and search_docs. Minor inconsistencies like settle.subscribe vs settlement.execute and subscribe vs subscription.get keep it from being fully uniform, but the convention is mostly consistent.
At 115 tools, this server is far beyond any reasonable scoped surface for a single MCP server. The count indicates severe bloat and forces agents to navigate a sprawling set of overlapping capabilities rather than a focused, well-earned toolset.
Core settlement, quote, compliance, oracle, FX, and integration paths are broadly covered, but there are notable lifecycle gaps: receipt.create says receipts are queryable yet no receipt query tool exists, and there is no settlement cancellation/refund/reversal, no policy or mandate revoke/delete, and ramp.agent_card references a missing ramp.agent_card_status. Agents can work around many gaps, but some workflows dead-end.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
EUR settlement + trust for AI agent commerce: budgets, KYA, merchant discovery. 22 tools.
17 pay-per-call web, finance, legal and onchain tools for AI agents. USDC on Base via x402/MPP.
271 agent-payable tools: competitive intel, finance, KYC, compliance, ESG. x402 per-call.
Cross-asset market data, LLM gateway and ML forecasts for AI agents. USDC via x402 + MPP.
Related MCP Servers
- FlicenseNot gradedqualityBmaintenanceKeyless, pay-per-call compliance & regulated-data tools for AI agents: OFAC wallet + sanctions/PEP + KYB screening, SEC filings, FRED economics, FDA recalls, federal awards, and continuous monitoring (watch a wallet/company/brand for status changes). USDC via x402 on Base/Solana, no API key, no signup.-
- AlicenseNot gradedqualityDmaintenance53 regulatory compliance evidence tools across 3 MCP servers for AI agents. MiCA authorization status, DORA evidence packs, stablecoin risk scoring (105+ tokens), macro intelligence (86 FRED series). Every response ECDSA-signed (ES256K), blockchain-anchored, audit-ready. Free tier, OAuth 2.0.MIT
- AlicenseAqualityDmaintenanceFinancial intelligence for AI agents. 31 tools across 8 data sources — regime, derivatives, stablecoin flows, momentum, volatility, macro, DeFi, weather patterns, political cycles, seasonality. The context layer between your agent and a bad trade.3122 npm9MIT
- AlicenseNot gradedqualityFmaintenanceArchived and no longer maintained. Tools and prices shown here are out of date. Use the maintained server: glama.ai/mcp/servers/OceanAlt666/oceanalt-aml-mcp (GitHub: OceanAlt666/oceanalt-aml-mcp).444 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.