DPX — Institutional Cross-Border Settlement
REMOTE · MCP.UNTITLEDFINANCIAL.COM · 2 COMPONENTS · SCANNED OCT 9
AI-native settlement rail + intelligence oracle for autonomous agents. x402, Base mainnet, 81 tools.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: this server exposes a tool marked destructive (intelligence.subscription.delete) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated. View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 19345 tokens (~168/item across 115 items; 115 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (86% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 115 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the DPX — Institutional Cross-Border Settlement MCP server?
DPX — Institutional Cross-Border Settlement is a hosted endpoint at https://mcp.untitledfinancial.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.untitledfinancial.com
claude mcp add --transport http untitledfinancial-dpx 'https://mcp.untitledfinancial.com/mcp'
{
"mcpServers": {
"untitledfinancial-dpx": {
"url": "https://mcp.untitledfinancial.com/mcp"
}
}
} {
"servers": {
"untitledfinancial-dpx": {
"type": "http",
"url": "https://mcp.untitledfinancial.com/mcp"
}
}
} [mcp_servers.untitledfinancial-dpx] url = "https://mcp.untitledfinancial.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"untitledfinancial-dpx": {
"type": "remote",
"url": "https://mcp.untitledfinancial.com/mcp",
"enabled": true
}
}
} openclaw mcp add untitledfinancial-dpx --url 'https://mcp.untitledfinancial.com/mcp' --transport streamable-http
mcp_servers:
untitledfinancial-dpx:
url: "https://mcp.untitledfinancial.com/mcp" {
"McpServers": {
"untitledfinancial-dpx": {
"Transport": "http",
"Url": "https://mcp.untitledfinancial.com/mcp"
}
}
} assistant mcp add untitledfinancial-dpx -t streamable-http -u 'https://mcp.untitledfinancial.com/mcp'
{
"mcpServers": {
"untitledfinancial-dpx": {
"type": "http",
"url": "https://mcp.untitledfinancial.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Oct 26 0
- A breaking change shipped without a version bump: still 2.5.0 ▼ security
- Tool “reports.scenario” was removed ▼ security
- 30 Sept 26 0
- New tool “reports.scenario” functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 19 Sept 26 0
- A breaking change shipped without a version bump: still 2.5.0 ▼ security
- Tool “reports.macro” was removed ▼ security
- Tool “reports.esg” was removed ▼ security
- Tool “reports.compliance” was removed ▼ security
- Tool “reports.climate” was removed ▼ security
- Tool “reports.treasury” was removed ▼ security
- Tool coverage: 82% → 87% ▲ functional
- 18 Sept 26 0
- Tool coverage: 87% → 82% ▼ functional
- New tool “reports.macro” functional
- New tool “reports.treasury” functional
- New tool “reports.esg” functional
- New tool “reports.compliance” functional
- New tool “reports.climate” functional
- 11 Sept 26 0
- Tool “oracle.status” rewrote its description, which is the text the model reads security
- New tool “defi.research_papers” functional
- New tool “defi.concept_lookup” functional
- 4 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 8 Oct 2026 · Probed https://mcp.untitledfinancial.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=untitledfinancial.com | CN=WE1,O=Google Trust Services,C=US | 30 Aug 2026 | 29 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | a38192527df9660e25fc3e52e9fdbe |
| SANs: untitledfinancial.com, mcp.untitledfinancial.com, *.mcp.untitledfinancial.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.untitledfinancial.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| untitledfinancial.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.untitledfinancial.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.untitledfinancial.com/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ramp.connect ~120
Connect a Ramp corporate account to DPX settlement. Returns an OAuth authorization URL — direct the user to this URL to grant DPX access to their Ramp account. Required scopes: transactions:read, bills:read/write, cards:read/write, cards:read_agentic (Agent Cards), business:read, bank_accounts:read, vendors:read, entities:read. Call once per tenant; tokens are stored and refreshed automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| tenant_id | string | yes | Your internal tenant or customer ID — returned in the callback so you can match the connection. |
| Name | Type | Req | Description |
|---|---|---|---|
| authorize_url | string | – | Redirect the user to this URL to authorize DPX on their Ramp account. |
| scopes | string | – | Requested OAuth scopes. |
| tenant_id | string | – | – |
No examples provided.
ramp.settle ~239
Execute a DPX stablecoin settlement funded by a Ramp Agent Card — combines card creation and settlement in one call. Ramp handles the fiat conversion leg; DPX settles USDC or EURC on Base mainnet in ~30 seconds. Returns pacs.002 confirmation + SFDR PAI indicators. No crypto wallet pre-funding required. Requires Ramp account connected via ramp.connect.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Payment amount (e.g. "50000.00"). |
| callback_url | string | – | Webhook URL for pacs.002 delivery. |
| creditor_lei | string | – | Recipient LEI for GLEIF VoP (optional). |
| creditor_name | string | yes | Recipient name. |
| creditor_wallet | string | yes | Recipient on-chain wallet address (0x...). |
| currency | string | yes | Source currency: USD or EUR. |
| merchant_scope | string | – | Merchant name for Agent Card scope. |
| reference | string | – | Your internal payment reference. |
| settlement_asset | string | – | Settlement asset: USDC (default) or EURC. |
| tenant_id | string | yes | Tenant ID of the connected Ramp account. |
| Name | Type | Req | Description |
|---|---|---|---|
| agentCard | object | – | – |
| compliance | object | – | FATF R16 + SFDR PAI indicators. |
| dpxPaymentId | string | – | – |
| iso20022 | object | – | pacs.002 status object. |
| settlement | object | – | – |
| status | string | – | – |
No examples provided.
ramp.spend_analysis ~112
Analyse a connected Ramp account's wire and international bill volume to surface DPX settlement opportunity. Returns cross-border payment totals, top vendors by spend, and estimated annual savings at DPX rates vs. typical bank wire (3.0% all-in vs. DPX ~2.035%). Requires Ramp account connected via ramp.connect.
| Name | Type | Req | Description |
|---|---|---|---|
| page_size | number | – | Number of bills to analyse (default 100, max 500). |
| tenant_id | string | yes | Tenant ID of the connected Ramp account. |
| Name | Type | Req | Description |
|---|---|---|---|
| crossBorder | object | – | Wire and international bill totals. |
| dpxOpportunity | object | – | Estimated annual savings and DPX fees. |
| topVendorsBySpend | array | – | Top 10 vendors by total payment volume. |
No examples provided.
receipt.create ~309
Record a tamper-evident signed receipt for an agent financial action. Call immediately after every successful settlement. Returns a receipt ID and HMAC-SHA256 signature over the canonical receipt JSON — cryptographic proof the record has not been altered. Receipts are queryable by session or agent for audit.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Agent that executed the payment |
| amount_usd | number | yes | Amount paid in USD |
| compliance_decision | string | – | Compliance decision at time of payment (PROCEED / HOLD / BLOCKED) |
| counterparty | string | – | Counterparty name |
| delegation_id | string | – | Delegation ID if acting under delegated authority |
| from_currency | string | – | Source currency (default: USD) |
| oracle_status | string | – | Oracle status at time of payment (STABLE / CAUTION / UNSTABLE) |
| policy_id | string | – | Policy ID that governed this payment |
| recipient | string | – | Recipient wallet address |
| sandbox | boolean | – | True if this was a sandbox settlement |
| session_id | string | – | Task or session ID for grouping (use the same ID for all payments in one agent run) |
| settlement_id | string | – | Settlement ID returned by the settle tool |
| task_context | string | – | Plain-text description of what task triggered this payment |
| to_currency | string | – | Destination currency (default: USD) |
| tx_hash | string | – | On-chain transaction hash (if live) |
No output schema declared.
No examples provided.
reports.climate ~111
AI-synthesized climate risk report — TCFD physical risk assessment, commodity stress signals across 11 markets, climate outlook (STABLE/ELEVATED/CRITICAL), and narrative risk guidance. Sourced from DPX Commodity Forecast Oracle and live climate signals. Cached hourly. Requires a pre-purchased DPX Reports API key via Authorization: Bearer <key>.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | DPX Reports API key. Alternatively, set Authorization: Bearer <key> in the calling context. |
No output schema declared.
No examples provided.
reports.compliance ~126
AI-synthesized compliance report — OpenSanctions global sanctions screening, PEP status, FATF country risk tier, AML risk score with signal breakdown, Travel Rule / FATF R.16 attestation status, and compliance verdict narrative. Requires lei or name. Requires a pre-purchased DPX Reports API key.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | DPX Reports API key. |
| lei | string | – | GLEIF LEI of the entity to screen. |
| name | string | – | Entity name to screen (if no LEI). One of lei or name required. |
No output schema declared.
No examples provided.
reports.esg ~120
AI-synthesized ESG report — all 18 SFDR Annex I PAI indicators, E/S/G sub-scores, CSRD financed emissions estimate, fee tier implication for DPX settlement, and ESG disclosure narrative. Requires a wallet address or LEI. Requires a pre-purchased DPX Reports API key.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Wallet address or on-chain entity address to score. |
| apiKey | string | – | DPX Reports API key. |
| lei | string | – | Optional GLEIF LEI for SFDR PAI report. |
No output schema declared.
No examples provided.
reports.macro ~109
AI-synthesized macro report — global macro stability score (0–100), regime classification (STABLE/CAUTION/UNSTABLE), USD structural health across 12 signals, 30/60/90-day outlook with confidence scores, and synthesis across geopolitical, FX, credit, and supply chain signals. Sourced from DPX Stability Oracle v9. Cached hourly. Requires a pre-purchased DPX Reports API key.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | DPX Reports API key. |
No output schema declared.
No examples provided.
reports.treasury ~95
AI-synthesized treasury report — 30-day settlement volume by corridor, AI decision audit (authorized/held/review/failed breakdown), average oracle score at settlement, escalation rate, and portfolio-level settlement health narrative. Requires a pre-purchased DPX Reports API key.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | DPX Reports API key. |
| period | string | – | ISO month (YYYY-MM). Defaults to current month. |
No output schema declared.
No examples provided.
route ~130
Multi-stablecoin settlement routing. Given amount, source currency (from), and destination currency (to), returns all three stablecoin options (USDC, EURC, USDT) ranked by settlement efficiency. EURC is recommended for EUR destinations — eliminates cross-currency conversion. Returns settleBody ready to POST to /settle for the top-ranked option.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Settlement amount in source currency |
| from | string | yes | Source currency code (USD, EUR, GBP, BRL, etc.) |
| to | string | yes | Destination currency code (USD, EUR, GBP, etc.) |
| Name | Type | Req | Description |
|---|---|---|---|
| generatedAt | string | – | – |
| options | array | – | – |
| routingAdvice | object | – | – |
| settleEndpoint | string | – | – |
| ttlSeconds | number | – | – |
No examples provided.
search_docs ~121
Search DPX documentation by keyword. Returns the most relevant doc sections — including how-to guides, API references, fee structure, oracle architecture, compliance requirements, and integration setup. Call this when you need protocol details mid-task rather than relying on context alone. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results to return (default 3, max 5). |
| query | string | yes | Keywords to search — e.g. "how to settle", "esg fee formula", "butterfly cascade", "mercury send", "compliance screen". |
No output schema declared.
No examples provided.
settle.subscribe ~94
Register a webhook callback for settlement completion events. Your endpoint receives a POST with X-DPX-Signature: sha256=<hmac> over the raw JSON body whenever a settlement completes. Returns a subscriptionId and webhookSecret — store the secret immediately, it is returned once.
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | – | Event types (default: ["settlement.completed"]) |
| url | string | yes | HTTPS endpoint to receive settlement.completed events |
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | – | – |
| subscriptionId | string | – | – |
| webhookSecret | string | – | HMAC secret — returned once, store immediately |
No examples provided.
settlement.execute ~260
Execute a DPX cross-border settlement. The Settlement Agent checks oracle conditions, reasons with Claude AI, and executes on-chain (or returns sandbox result if sandbox=true). Returns settlement ID, status (executed/held/sandbox/failed), tx hash, net amount, fees, oracle conditions, and AI reasoning. Default: sandbox=true — set sandbox=false only for live execution.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount in source currency units |
| destinationCurrency | string | yes | Destination currency: USD, EUR, GBP, USDC, EURC |
| esgScore | number | – | ESG score override 0–100 (testing only) |
| purpose | string | – | Payment purpose: intercompany, vendor-payment, payroll, treasury |
| quoteId | string | – | Pre-fetched quoteId from get_quote (optional — agent fetches live if omitted) |
| recipientAddress | string | yes | On-chain recipient wallet address (0x...) |
| referenceId | string | – | External reference ID (invoice number, TMS ID, etc.) |
| sandbox | boolean | – | Sandbox mode — real calculations, no on-chain execution. Default: true. |
| sourceCurrency | string | yes | Source currency: USD, EUR, GBP, USDC, EURC |
| Name | Type | Req | Description |
|---|---|---|---|
| httpStatus | number | – | HTTP status from Settlement Agent |
| result | object | – | – |
| summary | string | – | Human-readable settlement outcome summary |
No examples provided.
settlement.iso20022 ~174
ISO 20022 Pain.001 Payment Intake — parses a pain.001 XML payment initiation message and converts it to a DPX /settle body. Handles single-credit and multi-credit transfer instructions. Returns a structured settle body ready to pass to settlement.execute, including oracle-validated corridor selection and stablecoin routing. Use this when receiving payment instructions from a TMS (Kyriba, FIS, SAP) or bank that emits ISO 20022 format. Free (parse only); the downstream settlement.execute call carries the x402 fee.
| Name | Type | Req | Description |
|---|---|---|---|
| pain001Xml | string | yes | Raw pain.001 XML string. |
| sandbox | boolean | – | Pass through to settlement.execute as sandbox mode. Default true. |
| validateOnly | boolean | – | If true, parse and validate without returning a settle body. Default false. |
| Name | Type | Req | Description |
|---|---|---|---|
| payments | array | – | Parsed payment instructions with amount, currency, creditor, debtor. |
| settleBody | object | – | Structured body ready for settlement.execute. Null if validateOnly=true. |
| validationErrors | array | – | Schema or business-rule validation errors, if any. |
No examples provided.
settlement.nl ~175
Execute a payment from a plain-English instruction. DPX's AI synthesis layer parses the instruction, runs the full oracle gate → compliance screen → settlement flow autonomously, and returns a receipt. Use this when the agent has a natural-language payment task rather than structured parameters. Examples: 'Pay Acme GmbH $25,000 for invoice #42', 'Send $10k to 0x... for vendor services', 'Settle the outstanding balance with Nova Trade SA'. Sandbox mode by default.
| Name | Type | Req | Description |
|---|---|---|---|
| instruction | string | yes | Plain-English payment instruction, e.g. 'Pay Acme GmbH $25,000 USD for invoice #INV-2026-0042' |
| recipientAddress | string | yes | Recipient wallet address (0x...) |
| sandbox | boolean | – | Set false for live execution. Default: true |
| Name | Type | Req | Description |
|---|---|---|---|
| aiConfidence | number | – | – |
| aiDecision | string | – | – |
| feesTotal | number | – | – |
| netAmount | number | – | – |
| settlementId | string | – | – |
| status | string | – | – |
| txHash | string | – | – |
No examples provided.
settlement.quote ~242
Get a binding fee quote for a DPX settlement. Returns core fee (1.50%), FX fee (0.40% cross-currency), live ESG fee (0–0.50%), license fee (0.01%), total all-in rate, net amount, oracle status, AI reasoning, and a quoteId valid for 300 seconds. Always call this before settlement.execute.
| Name | Type | Req | Description |
|---|---|---|---|
| amountUsd | number | yes | Settlement amount in USD. |
| counterpartyName | string | – | Counterparty company name — used for ESG auto-lookup if lei is not provided. |
| esgScore | number | – | Counterparty ESG score 0–100. If omitted and lei or counterpartyName is provided, the ESG Oracle is queried automatically. |
| hasFx | boolean | – | True if source and destination currencies differ (adds 0.40% FX fee). |
| lei | string | – | Counterparty LEI — triggers automatic ESG lookup if esgScore is not provided. |
| monthlyVolumeUsd | number | – | Monthly volume for discount tier. $1M+ = Institutional (20% off). $10M+ = Sovereign (30% off). |
| Name | Type | Req | Description |
|---|---|---|---|
| amountUsd | number | – | Input settlement amount in USD |
| expiresAt | string | – | ISO 8601 expiry timestamp |
| fees | object | – | – |
| netAmountUsd | number | – | Net amount after all fees |
| oracleScore | number | – | Oracle confidence 0–100 |
| oracleStatus | string | – | STABLE | CAUTION | UNSTABLE |
| quoteId | string | – | Binding quote ID, valid 300 seconds |
| reasoning | string | – | AI reasoning for fee calculation |
| tier | string | – | Volume tier: Standard | Growth | Institutional | Sovereign |
No examples provided.
settlement.status ~72
Look up a previous DPX settlement by settlement ID. Returns the full audit record: status, tx hash, amounts, fees, oracle conditions at time of settlement, ESG score, Claude AI reasoning, and timestamp.
| Name | Type | Req | Description |
|---|---|---|---|
| settlementId | string | yes | Settlement ID from the settlement.execute tool (format: dpx_...) |
| Name | Type | Req | Description |
|---|---|---|---|
| httpStatus | number | – | HTTP status from Settlement Agent |
| settlement | object | – | – |
No examples provided.
settlement.try ~147
Settlement Dry Run — returns the full oracle response a real /settle call would receive, without payment or on-chain execution. Runs live oracle gate, live compliance pre-check, and fee math. Use this to demonstrate the settlement flow to a human, onboard a new agent, or verify oracle conditions before committing a payment. No authentication required, no USDC needed. Returns: oracle status and score, compliance tier, fee estimate, stablecoin routing, and a plain-language settlement brief. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| amountUsd | number | yes | Settlement amount in USD. |
| destinationCurrency | string | – | Destination currency (default: USD). |
| sourceCurrency | string | – | Source currency (default: USD). |
| Name | Type | Req | Description |
|---|---|---|---|
| brief | string | – | Plain-language settlement brief. |
| compliance | object | – | tier, flags, amlStatus. |
| feeEstimate | object | – | totalBps, grossUsd, netUsd, intelligenceFee. |
| oracle | object | – | status, score, reasoning. |
| stablecoin | string | – | Recommended stablecoin for this settlement. |
No examples provided.
stability.corridor ~212
Corridor-specific settlement stability score (0–100) for any currency pair. Combines the live global Stability Oracle score with corridor-specific risk adjustments covering 28 currency pairs: regulatory flags (BCB/IOF for BRL, PBoC capital rules for CNH, BCRA controls for ARS, etc.), FX liquidity score based on active trading sessions at current UTC time, cascade penalty from live macro signals, and weekend/off-hours penalty. Returns SETTLE_NOW / DELAY_24H / DELAY_48H recommendation with rationale. Distinct from oracle.stability (which is global) and market.fx (which is spot-rate focused) — this answers "is this specific corridor safe to settle through right now?"
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Source currency ISO-4217 code (e.g. "USD", "EUR", "GBP"). |
| to | string | yes | Destination currency ISO-4217 code (e.g. "BRL", "MXN", "SGD"). |
| Name | Type | Req | Description |
|---|---|---|---|
| components | object | – | globalOracleScore, corridorAdjustment, cascadePenalty, liquidityScore, weekendPenalty |
| corridor | object | – | score (0–100), tier, recommendation (SETTLE_NOW/DELAY_24H/DELAY_48H), regulatoryFlags, corridorNotes |
| marketContext | object | – | cascadeLevel, globalOutlook, currentUtcHour, isWeekend |
No examples provided.
stability.settlement_window ~241
Optimal settlement execution window analysis for a specific cross-border payment over the next 72 hours. Generates 18 × 4-hour time slots and scores each by composite risk: corridor stability, FX session liquidity, cascade level decay/growth based on macro outlook, weekend/off-hours penalty, and counterparty ESG tier (if LEI provided). Returns a ranked window schedule with OPTIMAL / GOOD / ACCEPTABLE / AVOID classification per slot, a best-window recommendation, and large-amount splitting guidance for settlements ≥ $5M. Use this before scheduling large cross-border settlements to minimize execution risk.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Settlement amount (default 1,000,000). Used for large-amount guidance ≥$5M. |
| currency | string | – | Currency of the amount (defaults to from). |
| from | string | yes | Source currency ISO-4217 (e.g. "USD"). |
| lei | string | – | Optional 20-char GLEIF LEI of counterparty — fetches live ESG tier to apply counterparty risk penalty. |
| to | string | yes | Destination currency ISO-4217 (e.g. "BRL"). |
| Name | Type | Req | Description |
|---|---|---|---|
| marketContext | object | – | globalOracleScore, corridorAdjustment, cascadeLevel, globalOutlook, regulatoryFlags |
| recommendation | object | – | bestWindow (ISO datetime), bestScore, optimalCount, goodCount, summary, largeAmountNote |
| windows | array | – | 18 × 4-hour slots: startUtc, endUtc, compositeScore, tier, components, recommendation, rationale |
No examples provided.
stability.stablecoin_route ~210
Multi-stablecoin settlement routing — given a source and destination currency pair, recommends the optimal stablecoin path based on corridor liquidity, regulatory fit, gas economics, and DPX native support. Returns a ranked list of stablecoins (USDC, EURC, BRLA, MXNC, NGNC, AEDX, PYUSD, USDT, and others) with regulatory flags, MiCA/GENIUS Act compliance status, liquidity tier, and warnings. Identifies blocked routes (e.g. USDT for EU under MiCA, BRLA before BCB Resolution 561 deadline). Use before settlement to avoid regulatory penalties and ensure optimal execution path.
| Name | Type | Req | Description |
|---|---|---|---|
| amountUsd | number | – | Settlement amount in USD (used for liquidity tier and large-amount warnings). |
| from | string | yes | Source currency ISO-4217 (e.g. "USD"). |
| to | string | yes | Destination currency ISO-4217 (e.g. "EUR", "BRL", "AED"). |
| Name | Type | Req | Description |
|---|---|---|---|
| evaluatedAt | string | – | ISO timestamp |
| recommendation | object | – | symbol, chain, reason, micaCompliant, geniusActCompliant |
| routes | array | – | Ranked stablecoin options — each with symbol, liquidityTier, regulatoryFlags, warnings, blocked status, notes |
No examples provided.
swift.gpi_track ~198
Track a DPX settlement via SWIFT gpi-compatible status. Given a UETR (Unique End-to-End Transaction Reference), returns gpi-format payment status including pacs.002 payload that a SWIFT member bank can submit to the gpi Tracker. Use this when a UETR was provided at payment initiation (via the uetr field in settlement.execute or POST /payments/initiate). Returns ACCP (settled), PDNG (pending), or RJCT (rejected) with full on-chain settlement details. DPX is not a SWIFT member — the SWIFT member bank submits the returned pacs.002 to the gpi Tracker via their own gpi API access.
| Name | Type | Req | Description |
|---|---|---|---|
| uetr | string | yes | RFC 4122 UUID UETR assigned at payment initiation, e.g. "97ed4827-7b6f-4491-a06f-b548d5a7512d". |
| Name | Type | Req | Description |
|---|---|---|---|
| dpxPaymentId | string | – | DPX internal payment ID. |
| gpiStatus | string | – | ACCP | PDNG | RJCT |
| pacs002 | object | – | Full ISO 20022 pacs.002 payload for gpi Tracker submission. |
| uetr | string | – | The UETR provided. |
No examples provided.
treasury.yield_route ~498
Treasury Float Yield Routing Analysis — OPTIONAL, CLIENT-DIRECTED ONLY. Analyzes whether idle settlement float can be productively deployed into a yield-bearing instrument between the current time and a scheduled settlement deadline. Returns a structured recommendation with expected yield, exit timing, liquidity assessment, slippage estimate, and a mandatory risk disclosure. THIS TOOL DOES NOT MOVE FUNDS. It provides analysis only. All execution decisions are made by the client or agent acting on explicit instruction. DPX charges a flat fee for this analysis and does not receive any portion of yield earned. Current supported instrument: sUSDS (Sky Protocol Savings Rate). Selected because: • Instant on-chain entry and exit (no T+1 delays) • No US person restrictions • Real asset backing (tokenized RWAs + Spark borrow rates) • Available on Base chain via bridge • No de-peg events recorded (unlike synthetic alternatives) Safety parameters enforced: • Maximum 90% of settlement amount — 10% always stays in USDC • Early exit triggered 30 minutes before settlement deadline (not 15) • Slippage guard: if DEX USDC/USDS quote shows >0.1% slippage, recommendation = HOLD • Minimum viable window: 2 hours (shorter windows do not justify entry/exit gas costs) Not recommended if: • Settlement window is < 2 hours • Amount is < $50,000 (gas costs erode yield) • Client has not acknowledged the risk_disclosure object in this response • Settlement is time-critical with zero tolerance for delay
| Name | Type | Req | Description |
|---|---|---|---|
| amountUsdc | number | yes | Settlement amount in USDC. Minimum $50,000 for yield routing to be viable after gas costs. |
| dryRun | boolean | – | If true, returns analysis without any on-chain queries. Useful for planning. Default: false. |
| riskTolerance | string | – | conservative = sUSDS only (T-bill / RWA backed, instant exit). moderate = sUSDS with higher slippage tolerance (up to 0.15%). Default: conservative. |
| settlementDeadlineUtc | string | yes | ISO 8601 UTC timestamp of when USDC must be ready for settlement (e.g. "2026-06-15T20:00:00Z"). The tool will recommend exiting 30 minutes before this. |
| Name | Type | Req | Description |
|---|---|---|---|
| amountReserved | number | – | Amount kept in USDC regardless (10% floor). |
| amountRoutable | number | – | Amount to deploy (90% of input, USDC). 10% stays in USDC. |
| currentApyPct | number | – | Current Sky Savings Rate APY (live, from Sky Protocol). |
| estimatedSlippage | number | – | Estimated DEX slippage for USDC→USDS→USDC round trip (%). |
| exitBy | string | – | Recommended exit timestamp (30 min before deadline). |
| expectedYieldUsdc | number | – | Expected yield for this window at current APY. |
| gasEstimateUsdc | number | – | Estimated Base L2 gas cost for entry + exit in USDC. |
| instrument | string | – | Recommended instrument (currently always sUSDS). |
| instrument_detail | object | – | Background on the recommended instrument. |
| netYieldUsdc | number | – | Expected yield minus gas costs. |
| notViable | boolean | – | True if net yield is negative (gas exceeds expected yield). |
| recommendation | string | – | ROUTE (deploy float), HOLD (stay in USDC), or INSUFFICIENT_WINDOW. |
| risk_disclosure | object | – | MUST be surfaced to the client before any action is taken. |
| slippageGuardTripped | boolean | – | True if slippage > 0.1% — recommendation will be HOLD. |
| windowHours | number | – | Available window in hours (deadline minus now minus 30-min buffer). |
No examples provided.
What is the DPX — Institutional Cross-Border Settlement MCP server?
DPX — Institutional Cross-Border Settlement is an MCP server listed in the public MCP registry as io.github.untitledfinancial/dpx. AI-native settlement rail + intelligence oracle for autonomous agents. x402, Base mainnet, 81 tools. This page covers its hosted endpoint (https://mcp.untitledfinancial.com/mcp).
Is the DPX — Institutional Cross-Border Settlement MCP server safe to use?
DPX — Institutional Cross-Border Settlement scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the DPX — Institutional Cross-Border Settlement MCP server expose?
DPX — Institutional Cross-Border Settlement exposes 115 tools: protocol.manifest, settlement.quote, esg.score, esg.lookup, esg.batch, and 110 more. Their descriptions and schemas cost roughly 19,345 tokens of context every time the server is loaded.
Does the DPX — Institutional Cross-Border Settlement MCP server require authentication?
No. We connected to DPX — Institutional Cross-Border Settlement without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DPX — Institutional Cross-Border Settlement MCP server still maintained?
DPX — Institutional Cross-Border Settlement is still listed as active in the MCP registry. We last reached this channel on 8 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.