DPX — Settlement & Intelligence for AI Agents

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.