DPX — Institutional Cross-Border Settlement
Server Details
AI-native stablecoin settlement rail replacing SWIFT for institutional cross-border payments. 14 tools covering settlement quotes, execution, ESG scoring, oracle status, fee verification, competitor comparison, rail health, investment context, and MPP-gated macro intelligence. Settles via Base mainnet USDC at ~1.385% all-in.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.4/5 across 61 of 71 tools scored.
Most tools have clearly distinct purposes, especially within their domains (e.g., analytics, compliance, ESG, forecasting). However, a few tools like route and stability.stablecoin_route or settlement.quote and fx.cost_certainty may cause confusion despite distinct descriptions, and the large number of intelligence tools (cascade, aftershock, contagion, etc.) could lead to misselection without careful reading.
Naming follows a domain prefix pattern (e.g., agent.kya_register, settlement.quote, esg.score), which provides some structure. However, inconsistencies exist: some tools use underscores (batch_settle, flow_check), others are single words (route), and the mix of verb_noun and noun_verb styles (e.g., compliance.pep_screen vs market.fx) reduces predictability.
At 71 tools, the server is very broad in scope, covering compliance, ESG, forecasting, intelligence, treasury management, and more. While each tool seems justified for the complex institutional domain, the sheer number may overwhelm agents and makes the set feel bloated. A more focused scope or tighter tool grouping would improve appropriateness.
The tool surface is remarkably comprehensive for cross-border settlement, covering end-to-end workflow from quoting, FX analysis, compliance screening, ESG scoring, forecasting, and multiple payment rails (Mercury, Ramp, SWIFT). Minor gaps exist (e.g., no tool to update a settlement after execution), but core operations are well-covered, and the addition of integration and audit trails enhances completeness.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!