Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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.

0 this week 71 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
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
Install

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

# add to Claude Code
claude mcp add --transport http untitledfinancial-dpx 'https://mcp.untitledfinancial.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "untitledfinancial-dpx": {
      "url": "https://mcp.untitledfinancial.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "untitledfinancial-dpx": {
      "type": "http",
      "url": "https://mcp.untitledfinancial.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.untitledfinancial-dpx]
url = "https://mcp.untitledfinancial.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "untitledfinancial-dpx": {
      "type": "remote",
      "url": "https://mcp.untitledfinancial.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add untitledfinancial-dpx --url 'https://mcp.untitledfinancial.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  untitledfinancial-dpx:
    url: "https://mcp.untitledfinancial.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "untitledfinancial-dpx": {
      "Transport": "http",
      "Url": "https://mcp.untitledfinancial.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add untitledfinancial-dpx -t streamable-http -u 'https://mcp.untitledfinancial.com/mcp'
// mcp.json
{
  "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.

Changelog

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
Diagnostics

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
MCP tools · 115 exposed · ~19,345 tokens

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 →

Tool Tokens
agent.kya_register ~412

KYA — Know Your Agent. Three-tier registration model — compliance burden scales with settlement risk, no documents ever required. ANONYMOUS: agent name only, $1K/day cap, instant. REGISTERED: add ownerEntity + ownerEmail (self-attested, no verification), $25K/day cap, instant. VERIFIED: add ownerLei (active GLEIF LEI) — DPX calls the public GLEIF API, confirms ACTIVE status, and grants VERIFIED instantly. No documents, no manual review; LEI issuers (LOUs) have already done identity verification and DPX inherits it. VERIFIED agents get institutional caps (governed by mandate), FATF R.16 attestation on every settlement, and full AP2 mandate support. Legal basis: FATF R.16 originator = owner entity (not the agent); MiCA Art. 45/72 accepts LEI; GENIUS Act satisfied by entity attestation.

NameTypeReqDescription
frameworkstring–Agent framework: "claude", "gpt-4o", "gemini", "custom", etc.
mandateobject–Optional AP2-compatible spend mandate (REGISTERED/VERIFIED only). Caps are clamped to tier limits for REGISTERED agents.
namestringyesHuman-readable name for this agent.
ownerEmailstring–Contact email. Required for REGISTERED tier ($25K/day cap). Self-attested, not verified.
ownerEntitystring–Organization or person that owns/operates this agent. Required for REGISTERED tier.
ownerLeistring–20-char GLEIF LEI. Providing a valid active LEI instantly grants VERIFIED tier — no documents. Get your LEI at gleif.org.
protocolsarray–Supported protocols: ["x402", "ap2", "mcp", "a2a"].
publicKeystring–Optional public key for credential signature verification.
NameTypeReqDescription
agentIdstring–Unique agent identifier (agt_...). Store this.
kyaLevelstring––
kyaScorenumber–Trust score 0–100.
leiEntityNamestring–Legal name from GLEIF record (VERIFIED only).
leiVerifiedboolean–true if LEI was confirmed via GLEIF API.
tierCapsobject–maxNotionalUsd and dailyCapUsd effective for this agent.
tierNotestring–Explanation of tier and how to upgrade.

No examples provided.

agent.kya_verify ~131

Verify a registered DPX agent and receive a signed 1-hour credential. Returns KYA level, effective spend caps (tier or mandate), owner verification status, mandate active status, and FATF R.16 compliance attestation. Attach credential.signature as X-Agent-Credential header and agentId as X-Agent-Id header on DPX /settle requests — enables mandate enforcement, per-agent audit trail, and FATF attestation. Credential expires in 1 hour; call again to refresh before expiry.

NameTypeReqDescription
agentIdstringyesAgent ID from agent.kya_register (agt_...).
NameTypeReqDescription
credentialobject–agentId, issuedAt, expiresAt, mandateId, attestation (kyaLevel, ownerVerified, mandateActive, fatfCompliant, dailyCapUsd, maxNotionalUsd), signature
kyaLevelstring––
kyaScorenumber––
mandateobject–Active mandate if present, null if expired.
verifiedboolean––

No examples provided.

agent.mandate_create ~264

Create or update an AP2-compatible spend mandate for a REGISTERED or VERIFIED DPX agent. Sets per-agent settlement constraints: max notional per settlement, daily cap, optional counterparty whitelist (LEIs or wallets), allowed currency pairs, ESG floor, and expiry. ANONYMOUS agents cannot hold mandates — register with ownerEntity + ownerEmail first. REGISTERED agents have mandate caps clamped to their tier limit ($25K). VERIFIED agents (GLEIF LEI confirmed) set their own caps with no platform ceiling. Mandate is AP2-formatted for interoperability with Google Agent Payments Protocol.

NameTypeReqDescription
agentIdstringyesAgent ID from agent.kya_register.
counterpartyWhitelistarray–LEIs or wallet addresses. Empty = any counterparty.
currencyPairsarray–Allowed pairs e.g. ["USD|EUR"]. Empty = any pair.
dailyCapUsdnumberyesMax USD per calendar day (UTC).
esgFloornumber–Min counterparty ESG score (0 = no floor).
expiresAtnumber–Unix timestamp for mandate expiry.
issuedBystring–Organization issuing this mandate.
maxNotionalUsdnumberyesMax USD per single settlement.
NameTypeReqDescription
agentIdstring––
ap2Compatibleboolean––
effectiveCapsobject–Actual caps after tier clamping.
mandateobject–Full mandate object.
mandateIdstring–Unique mandate ID (mnd_...).

No examples provided.

analytics.overview ~56

Get live DPX performance analytics. Returns current stability score, ESG composite scores, live fee breakdown, oracle health across all data sources, and a settlement readiness assessment. Use for dashboards, reporting, and AI-driven monitoring of protocol health.

Input schema present but exposes no named parameters.

NameTypeReqDescription
esgScorenumber–Protocol ESG composite score 0–100
feesobject––
oracleHealthobject–Health status per oracle data source
settlementReadyboolean–True if conditions are suitable for settlement
stabilityScorenumber–Current oracle stability score 0–100
timestampstring–ISO 8601 analytics timestamp

No examples provided.

batch_settle ~78

Submit multiple settlements in a single call. Runs all settlements concurrently — one failure does not block others. Returns a summary (total/succeeded/failed) and per-item results mirroring what POST /settle would return. Maximum 50 per batch.

NameTypeReqDescription
settlementsarrayyesArray of settlement request objects (same schema as the settle tool)
NameTypeReqDescription
resultsarray––
summaryobject––

No examples provided.

card.positions ~159

Plan treasury settlement for a crypto card program. Accepts net positions per corridor (e.g. USD-BRL: $2.3M, USD-EUR: €450K) and returns an optimal settlement plan — which corridors to settle now vs. hold, which stablecoin to use per corridor, and estimated all-in fee. No settlement is executed. Call this before card.settle to review the plan. Free.

NameTypeReqDescription
positionsarrayyesArray of net positions. Each: { corridor: "USD-BRL", netAmountUsd: 2300000, recipientAddress?: "0x..." }
settlementDatestring–Settlement date ISO string (defaults to today UTC). E.g. "2026-08-09".

No output schema declared.

No examples provided.

card.settle ~143

Execute treasury settlement for a crypto card program. Takes the same positions array as card.positions but executes all settlements via DPX batch — compliance-gated, oracle-priced, stablecoin-routed. Each position requires a recipientAddress. Use sandbox:true for testing. Returns per-corridor settlement results and a summary.

NameTypeReqDescription
positionsarrayyesArray of net positions. Each: { corridor: "USD-BRL", netAmountUsd: 2300000, recipientAddress: "0x..." }. recipientAddress is required for every position.
sandboxboolean–true = test mode, no on-chain execution. Default true — set false only for live execution.

No output schema declared.

No examples provided.

compliance.aml_screen ~164

AML Screen with Behavioural Profiling — deep AML assessment combining sanctions matching (OFAC, EU, UN, OFSI), behavioural pattern analysis, transaction velocity signals, and counterparty network risk. Returns CLEAR / REVIEW / BLOCK decision with confidence score, matched sanctions lists, behavioural anomaly flags, and a structured compliance narrative for audit. Use for high-value payments, onboarding, or any counterparty flagged by flow_check. Accepts wallet address or entity identifier. x402 paid, USDC on Base.

NameTypeReqDescription
amountUsdnumber–Transaction amount — used for velocity profiling. Optional.
entitystringyesWallet address, LEI, or name of the counterparty to screen.
purposestring–Payment purpose — used for behavioural context. Optional.
NameTypeReqDescription
behaviouralobject–Velocity flags, counterparty network risk, anomaly signals.
confidencenumber–Decision confidence 0–1.
decisionstring–CLEAR / REVIEW / BLOCK
narrativestring–Structured compliance narrative for audit record.
sanctionHitsarray–Matched sanctions list entries with list name and match score.

No examples provided.

compliance.pep_screen ~171

Screen an individual by name against the OpenSanctions PEP (Politically Exposed Person) dataset. PEPs include heads of state, senior government officials, senior executives of state-owned enterprises, senior politicians, senior military officers, judicial officials, and their close associates and family members. Returns match confidence, position/role, nationality, related entities, and an overall risk level (HIGH / MEDIUM / LOW / NONE). HIGH or MEDIUM matches require Enhanced Due Diligence (EDD) per FATF Recommendations 12 and 13 before settlement. Optionally filter by country.

NameTypeReqDescription
countrystring–ISO-2 country code to narrow the search (e.g. "IT"). Optional.
qstringyesFull name to screen (e.g. "Mario Draghi").
NameTypeReqDescription
fatfComplianceobject–EDD required flag, FATF R.12/13 attestation, note
matchedboolean––
matchesarray–Per match: caption, datasets, position, nationality, birthDate, relatedEntities, riskLevel, matchScore
overallRiskstring––
totalMatchesnumber––

No examples provided.

compliance.regulatory_calendar ~126

Returns a structured calendar of upcoming and in-effect compliance obligations across MiCA (EU crypto-asset markets regulation), SFDR (Sustainable Finance Disclosure Regulation), CSRD (Corporate Sustainability Reporting Directive), the US GENIUS Act (payment stablecoin framework), and FATF Recommendations 15/16. For each event: framework, jurisdiction, requirement summary, effective date, impact level, and article reference. Also returns a DPX alignment section mapping each framework to the specific DPX endpoints that satisfy it. Use this before settlement workflow design, compliance gap analysis, or regulatory reporting.

Input schema present but exposes no named parameters.

NameTypeReqDescription
dpxAlignmentobject–Per-framework mapping to DPX endpoints that satisfy each obligation
inEffectarray–Currently active requirements, most recent first
upcomingarray–Events not yet in effect, sorted by effective date ascending

No examples provided.

compliance.sfdr_pai_report ~142

SFDR Annex I PAI Report — generates the full Principal Adverse Impact statement for a portfolio of up to 50 entities (by LEI or wallet address). Returns all 18 mandatory indicators plus 2 optional climate indicators in the SFDR Annex I table format. Required for SFDR Article 8 and Article 9 product annual disclosure. Accepts LEIs or company names (GLEIF-resolved). x402 paid, USDC on Base.

NameTypeReqDescription
entitiesarrayyesLEIs, wallet addresses, or company names. Max 50.
reportDatestring–ISO date for the report reference period (default: today).
NameTypeReqDescription
paiTablearray–SFDR Annex I table rows — indicator, value, unit, data source, coverage.
portfolioScorenumber–Aggregate PAI composite score 0–100.
synthesisstring–Narrative for the PAI statement.

No examples provided.

compliance.sfdr_screen ~147

SFDR Article 8/9 Compliance Screen — determines whether a financial product or counterparty meets the Sustainable Finance Disclosure Regulation classification thresholds. Returns Article classification (6/8/9), Principal Adverse Impact indicator flags across 18 mandatory PAI metrics, ESG score alignment, and DNSH (Do No Significant Harm) assessment. Required for EU-regulated funds and any payment counterparty with SFDR disclosure obligations. Pass LEI or wallet address. x402 paid, USDC on Base.

NameTypeReqDescription
articleTargetstring–Target SFDR article classification to assess against. Default: "8".
entitystringyesLEI or wallet address of the entity to screen.
NameTypeReqDescription
classificationstring–Article 6 / 8 / 9 classification result.
dnshobject–Do No Significant Harm assessment across 6 environmental objectives.
paiFlagsarray–18 mandatory PAI indicators with flag, value, threshold, and pass/fail.
synthesisstring–Plain-language SFDR compliance narrative.

No examples provided.

compliance.ubo_chain ~198

Trace the beneficial ownership chain for any legal entity up to 3 levels deep using GLEIF relationship records, then screen every node in the chain against the OpenSanctions consolidated sanctions list (OFAC SDN, EU, UN, UK OFSI). Returns chain structure (SUBJECT → DIRECT_PARENT → ULTIMATE_PARENT), per-node sanctions status, LEI lapse flags, overall CLEAR / REVIEW_REQUIRED / BLOCKED verdict, and FATF R.16 beneficial ownership compliance attestation. Required for correspondent banking due diligence, FATF R.12/13 UBO identification, and MiCA Article 72 counterparty risk management.

NameTypeReqDescription
deepboolean–Set true to attempt 3-level traversal including intermediate nodes. Default false (direct + ultimate parent only).
leistringyes20-character GLEIF LEI of the entity to trace (e.g. "2594007XIACKNMUAW223").
NameTypeReqDescription
chainarray–Per-node: level, role, lei, entityName, country, leiStatus, sanctions (matched, score, datasets), riskFlag
chainDepthnumber––
fatfR16object–FATF R.16 beneficial ownership compliance attestation
overallStatusstring––
riskFlagsarray–Nodes with sanctions hits or lapsed LEIs
ultimateBeneficialOwnerobject–lei, entityName, country, leiStatus of the UBO

No examples provided.

compliance.vendor_risk ~162

Composite Vendor Risk Score — combines compliance (65%) and ESG (35%) signals into a single vendor risk assessment. Returns an overall risk tier (LOW / MEDIUM / HIGH / CRITICAL), component breakdown, sanctions status, PEP flags, ESG pillar scores, and a payment recommendation (PROCEED / PROCEED_WITH_MONITORING / HOLD / BLOCK). Designed for pre-payment vendor due diligence, treasury onboarding, and supplier risk review. Accepts LEI or wallet address. x402 paid, USDC on Base.

NameTypeReqDescription
amountUsdnumber–Payment amount in USD — scales the risk threshold (larger payments trigger higher scrutiny). Optional.
entitystringyesLEI, wallet address, or company name of the vendor.
NameTypeReqDescription
complianceScorenumber–AML/sanctions/PEP composite 0–100.
esgScorenumber–ESG composite 0–100.
flagsarray–Active risk flags with severity and source.
recommendationstring–PROCEED / PROCEED_WITH_MONITORING / HOLD / BLOCK
riskTierstring–LOW / MEDIUM / HIGH / CRITICAL
synthesisstring–Plain-language vendor risk narrative.

No examples provided.

compliance.vop_verify ~157

Verification of Payee — cryptographically verified payee check before a cross-border payment. Resolves a wallet address against GLEIF LEI registry, ESG Oracle, and on-chain activity to confirm the payee is who they claim to be. Returns a verification attestation, match confidence score, identity fields confirmed, and a signed verification receipt. Required for FATF R16 Travel Rule compliance and recommended for any payment over $3,000. $0.075 USDC per verification.

NameTypeReqDescription
expectedLeistring–Expected LEI for exact-match verification. Optional.
expectedNamestring–Expected legal entity name for name-match verification. Optional.
walletAddressstringyesPayee wallet address to verify.
NameTypeReqDescription
attestationstring–Signed verification receipt for audit.
confidencenumber–Match confidence 0–1.
identityFieldsobject–Confirmed fields: lei, entityName, jurisdiction, esgTier.
verifiedboolean–True if payee identity confirmed.

No examples provided.

compute.cost ~125

Get a model recommendation for a task type without running inference. Returns the best free model for the task, its strengths and speed tier, and a list of alternatives. Use this when an agent needs to select a model before committing to inference, or to surface model selection logic to a human. Free.

NameTypeReqDescription
speedboolean–true = prefer fastest model over most capable. Default false.
taskstringyesDescription of the task — e.g. "summarize a financial document", "write Python code", "translate from French", "reason through a math problem".

No output schema declared.

No examples provided.

compute.models ~72

List all AI models available through DPX Compute. All models are free-tier (no token cost) — routed via OpenRouter. Returns model IDs, provider, capability strengths, context window, and speed tier. Use this before compute.route to understand what models are available and pick the right one for a task. Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

compute.route ~205

Route a task to the best available free AI model and run inference. DPX selects the model based on the task type (reasoning → DeepSeek R1, code → Llama 3.3 70B, multilingual → Qwen 2.5 72B, fast → Llama 3.1 8B), calls OpenRouter, and returns the completion. All models are free-tier — no token cost. Pay per call in USDC via x402. Use this when an agent needs to delegate a subtask to a language model without managing model selection or API keys.

NameTypeReqDescription
messagesarray–Optional. Full message array in OpenAI format [{role, content}]. If omitted, task is sent as a user message.
preferSpeedboolean–true = use the fastest available free model regardless of task type. Default false.
taskstringyesPlain-language description of what the model should do. Used for model selection.

No output schema declared.

No examples provided.

computer_use.pay ~229

Complete a payment that Claude's computer use session has identified on screen — a checkout form, wire transfer UI, invoice approval, or vendor portal payment step. Call this instead of typing credentials into a UI. Describe what you see on screen, provide the amount and recipient, and DPX runs the full oracle gate → compliance screen → settlement flow. Returns a receipt. Use whenever computer use encounters a payment that would otherwise require human re-entry or approval.

NameTypeReqDescription
amountnumberyesPayment amount in USD as shown on screen
counterparty_namestring–Vendor or payee name as shown on screen
purposestringyesPayment purpose — e.g. vendor-invoice, contractor-payment, subscription, procurement
recipient_addressstringyesRecipient wallet address (0x...). If only bank/email visible, use settlement.nl instead.
sandboxboolean–Set false for live execution. Default: true
screen_contextstringyesDescribe what is visible on screen — the payment form, vendor name, invoice number, or UI context. Used for audit trail.
NameTypeReqDescription
aiConfidencenumber––
aiDecisionstring––
decisionstring––
feeUsdnumber––
netUsdnumber––
reasonstring––
settlementIdstring––
statusstring––
txHashstring––

No examples provided.

defi.concept_lookup ~110

A 39-term DeFi/digital-currency glossary spanning fundamentals, blockchain, tokens/assets, protocols, governance, security, and regulatory terms (fiat, TVL, AMM, DAO, impermanent loss, MiCA, and more), sourced from the World Economic Forum glossary plus DPX-curated DeFi infrastructure definitions. Optional keyword filter.

NameTypeReqDescription
qstring–Optional keyword filter across term, definition, and category (e.g. "collateral", "governance").
NameTypeReqDescription
countnumber––
labelstring––
recordsarray–Per term: id, term, definition, category, source

No examples provided.

defi.research_papers ~121

13 structured institutional research papers on CBDCs, stablecoins, crypto regulation, and cross-border payments — from BIS, the Federal Reserve, ECB, FSB, IMF, G7, SWIFT, and R3 — each with a summary and key findings. These papers are free but otherwise scattered as individual PDFs with no query layer; this makes them queryable in one place. Optional keyword filter.

NameTypeReqDescription
qstring–Optional keyword filter across title, organization, summary, and category (e.g. "mBridge", "reserve").
NameTypeReqDescription
countnumber––
labelstring––
recordsarray–Per paper: id, title, author, organization, date, category, summary, key_findings, source

No examples provided.

dpx.metrics ~109

Live performance metrics for the DPX settlement infrastructure — pulled directly from production telemetry. Returns request volumes, error rates, growth trends, per-service breakdown, and spike analysis across all active DPX workers. Free — designed for investor due diligence, analyst queries, and Standard Metrics / portfolio management integrations. No auth required.

NameTypeReqDescription
windowstring–Time window for metrics. "7d" = last 7 days, "30d" = last 30 days. Default: 30d.
NameTypeReqDescription
dailyAveragenumber––
errorRatestring––
peakDayobject––
servicesarray––
summarystring––
totalRequestsnumber––
weeklyTrendarray––
windowstring––

No examples provided.

esg.batch ~128

Screen up to 50 entities in a single call. Accepts LEIs or company names (GLEIF-resolved). Returns results ranked by composite ESG score descending — highest scoring counterparties first. Useful for portfolio-level compliance screening, supplier due diligence, and TMS pre-payment checks. Name resolution is slower than direct LEI input.

NameTypeReqDescription
leisarray–Array of LEIs to screen (fastest path — no GLEIF resolution needed).
namesarray–Array of company names to screen (resolved via GLEIF — slower, allows ≤3s per name).
NameTypeReqDescription
failednumber––
resultsarray–Entities sorted by composite score descending. Each item includes lei, entityName, score object, or an error note.
succeedednumber––
totalnumber––

No examples provided.

esg.lookup ~209

Resolve a company name, domain, or ticker to a LEI via GLEIF and return the full ESG score. Removes the need for callers to have a LEI. Returns Environmental (40%), Social (35%), and Governance (25%) pillar scores, composite 0–100, fee surcharge tier, and per-source breakdown (SEC EDGAR, OSHA, BLS SOII, EU E-PRTR, ESMA, World Bank WGI, GLEIF). Use when you have a company name but not a LEI.

NameTypeReqDescription
countrystring–ISO-2 country code to narrow results (e.g. "US", "DE"). Optional but improves match accuracy.
narrateboolean–Set true to include a 2–3 sentence plain-English compliance narrative generated by the AI synthesis layer.
qstringyesCompany name, domain, or ticker to look up (e.g. "Apple Inc", "siemens.com", "MSFT")
NameTypeReqDescription
foundboolean––
narrationstring–Plain-language compliance narrative (only when narrate=true)
resolvedobject––
scoreobject–Full ESG score object with composite, environmental, social, governance, feeTier, feeSurcharge, sources, coverage

No examples provided.

esg.portfolio ~154

Score an entire counterparty portfolio in one call (up to 200 entities by LEI or name). Returns portfolio-level composite E/S/G scores, tier distribution, aggregate fee surcharge impact in basis points, worst offenders (bottom 10% by composite), top performers, MiCA Article 72 ongoing monitoring status, and SFDR PAI flags. The canonical pre-settlement compliance check for treasury systems and TMS integrations.

NameTypeReqDescription
labelstring–Optional label for this portfolio (e.g. "Q3 2026 Counterparties").
leisarray–LEIs to score (fastest — no name resolution).
namesarray–Company names to score (GLEIF-resolved).
NameTypeReqDescription
complianceobject–micaArticle72, highRiskCount, sfdr flags
distributionobject–byTier counts, min, max, median
entitiesobject––
labelstring––
portfolioobject–composite, environmental, social, governance, tier, avgFeeSurcharge, totalFeeImpactBps
topPerformersarray––
worstOffendersarray–Bottom 10% entities with weakest pillar identified

No examples provided.

esg.score ~132

Get the live counterparty risk score (ESG-denominated) for a wallet address or the protocol default. Returns Environmental, Social, and Governance risk scores (0–100 each), composite weighted average, and the compliance-adjusted settlement fee percentage this score produces. Updated hourly from 6 institutional data sources: WorldBank, IMF, OECD, UN SDG API, ClimateMonitor, and SEC EDGAR. Required by EU SFDR Principal Adverse Impact reporting and CSRD financed emissions disclosure for institutional clients.

NameTypeReqDescription
addressstring–Wallet address (0x...) to score. Omit for protocol default.
NameTypeReqDescription
addressstring–Scored wallet address or "default"
environmentalnumber–Environmental score 0–100
esgScorenumber–Composite ESG score 0–100
feePctnumber–ESG fee percentage applied at settlement
governancenumber–Governance score 0–100
socialnumber–Social score 0–100
sourcesarray–Data sources used
tierstring–ESG tier label
updatedAtstring–ISO 8601 last update timestamp

No examples provided.

esg.supply_chain ~159

Supply Chain ESG Screen — screens an entire supplier/counterparty supply chain for ESG risk exposure. Accepts a focal entity (by LEI or wallet address) and traces upstream supply chain relationships via GLEIF. Returns per-tier ESG scores, highest-risk nodes, SFDR PAI exposure from supply chain, and a Scope 3 financed-emissions estimate. Useful for procurement teams, ESG-adjusted settlement pricing, and CSRD supply chain due diligence. x402 paid, USDC on Base.

NameTypeReqDescription
depthnumber–Supply chain depth to trace (1 = direct suppliers, 2 = tier-2). Default 1. Max 2.
entitystringyesLEI or wallet address of the focal company.
NameTypeReqDescription
scope3Estimateobject–PCAF Scope 3 Category 1 estimate — attributed emissions.
supplyChainScorenumber–Aggregate supply chain ESG composite 0–100.
synthesisstring–Plain-language supply chain ESG narrative.
tiersarray–Per-tier: nodes, avgEsgScore, highRiskNodes, sfdrPaiFlags.

No examples provided.

esg.trend ~134

Get the historical ESG composite trend for a specific entity by LEI. Returns score history, trend direction (IMPROVING / STABLE / DETERIORATING), and delta over the requested window. Data accumulates each time the entity is scored via esg.lookup, esg.batch, or esg.portfolio. Useful for due diligence, MiCA Article 72 ongoing monitoring reports, and detecting counterparties whose ESG posture is degrading.

NameTypeReqDescription
daysnumber–Lookback window in days (7–365). Default 90.
leistringyes20-character GLEIF LEI.
NameTypeReqDescription
baselinenumber––
currentnumber––
dataPointsnumber––
daysnumber––
deltanumber–Score change over the window (positive = improving)
historyarray––
leistring––
trendstring––

No examples provided.

esg.watch ~139

Register an entity for ongoing ESG monitoring. DPX checks the score daily and fires a webhook when the composite score shifts by ≥ thresholdPoints. Satisfies MiCA Article 72 ongoing monitoring requirements. Returns a watchId for status checks and cancellation. Webhook payload includes previous/current score, delta, and tier change.

NameTypeReqDescription
leistringyes20-character GLEIF LEI of the entity to monitor.
thresholdPointsnumber–Fire webhook if composite score changes by ≥ N points. Default 5. Minimum 1.
webhookUrlstringyesHTTPS URL to POST score change alerts to. Must be HTTPS.
NameTypeReqDescription
baselineScorenumber–Composite score at registration (used as first comparison point)
baselineTierstring––
createdAtstring––
entityNamestring––
leistring––
watchIdstring–UUID — use to check status (GET /esg/watch/:id) or cancel (DELETE /esg/watch/:id)

No examples provided.

fees.compare ~153

Compare DPX settlement cost against Stripe cross-border (5.4% + $0.30), Wise (0.40–1.50%), Ripple ODL (0.20–0.50%), Lightspark, SWIFT (2.00–5.00%), PayPal, and bank wire. Returns dollar savings vs each at the current DPX all-in rate (~2.035% typical). Also returns GENIUS Act and MiCA compliance status for each competitor.

NameTypeReqDescription
amountUsdnumberyesSettlement amount in USD
esgScorenumber–ESG score 0–100
hasFxboolean–Cross-currency? Adds 0.40% FX fee.
NameTypeReqDescription
amountUsdnumber–Settlement amount compared
comparisonobject–Per-competitor comparison keyed by competitor ID
dpxobject––
notestring–Context note on comparison methodology

No examples provided.

fees.schedule ~64

Get the complete DPX fee schedule: all components (core/FX/ESG/license), volume discount tiers (Standard / Growth / Institutional / Sovereign), ESG fee table by score, scenario examples, and competitive benchmarks vs Stripe, Wise, SWIFT, and bank wire.

Input schema present but exposes no named parameters.

NameTypeReqDescription
benchmarksobject–Competitor fee benchmarks
examplesarray–Fee calculation examples
feesobject–Fee component definitions
tiersobject–Volume discount tiers

No examples provided.

fees.verify ~87

Verify that the off-chain fee quote matches what the on-chain DPXSettlementRouter contract will charge. Returns feesMatch (true/false). Call after get_quote and before settle to confirm fee integrity.

NameTypeReqDescription
amountUsdnumberyesSettlement amount in USD
esgScorenumber–ESG score 0–100
hasFxboolean–Cross-currency settlement?
NameTypeReqDescription
deltanumber–Absolute difference in basis points
feesMatchboolean–True if off-chain quote matches on-chain contract
offChainFeeobject––
onChainFeeobject––
recommendationstring–PROCEED | INVESTIGATE

No examples provided.

flow_check ~159

Single pre-flight call before settling. Runs oracle check, compliance screen, and stablecoin routing in parallel and returns a unified go/no-go decision. Replaces the 3-step oracle → screen → route loop. Returns: decision (PROCEED/HOLD/BLOCKED), recommended token, estimated net received, oracle score, compliance verdict, and a ready-to-use settleBody.

NameTypeReqDescription
addressstring–Counterparty wallet address for compliance screen (optional but recommended)
amountnumberyesSettlement amount in source currency
fromstring–Source currency code (default: USD)
leistring–Counterparty LEI for enhanced compliance check (optional)
tostring–Destination currency code (default: USD)
NameTypeReqDescription
complianceobject––
decisionstring–PROCEED | HOLD | BLOCKED
estimatedNetUsdnumber–Estimated net received after all fees
oracleobject––
readyboolean–True when decision is PROCEED
settleBodyobject–Ready to POST to /settle (null if BLOCKED or HOLD)
tokenstring–Recommended stablecoin (USDC, EURC, or USDT)
ttlSecondsnumber––

No examples provided.

forecast.calendar ~75

Seasonal climate event calendar with commodity impact. Returns 12 critical annual windows (hurricane season, corn pollination, Brazil frost risk, Black Sea harvest, ENSO influence periods, etc.) sorted by urgency — active windows first, then by months until next occurrence. Each entry includes affected commodities, severity, and the agronomic basis.

Input schema present but exposes no named parameters.

NameTypeReqDescription
calendararray–Seasonal events sorted by urgency — active events first
currentMonthnumber–Current UTC month (1–12) for reference

No examples provided.

forecast.commodity_outlook ~158

Climate-driven price pressure outlook for a commodity. Returns BULLISH/BEARISH/NEUTRAL signal with 30/60/90-day horizons, confidence score, per-region stressor breakdown, and current FRED price reference. Covers 11 commodities: WHEAT, CORN, SOYB, COFFEE, COCOA, COTTON, SUGAR, WTI, NG, COPPER, LUMBER. Designed for institutional research teams evaluating commodity positions. Signals reflect supply constraint risk from climate — not a financial recommendation. Cache: 4h.

NameTypeReqDescription
freshboolean–true = bypass 4h cache and recompute live signals
symbolstringyesCommodity symbol
NameTypeReqDescription
climateScorenumber–Supply constraint pressure 0–100; >65 = elevated bullish pressure
confidencenumber–Signal confidence 0–1
currentPriceobject–Latest FRED price reference (value, unit, date)
forecastedAtstring––
horizonsobject–30d / 60d / 90d — each has signal, confidence, basis
inGrowingSeasonboolean–true = stressors in peak transmission window — act faster
namestring––
reasoningstring–Plain-language synthesis of climate signals and price implications
recommendationstring––
regionsarray–Per production-region climate scores and drought/temperature readings
signalstring––
stressorsarray–Active climate stressors with severity, region, price impact estimate, probability
symbolstring––

No examples provided.

forecast.heat_check ~119

Commodity Heat Check — all 11 commodity symbols simultaneously scored RED / YELLOW / GREEN. Fast single-call scan of the full commodity universe: WHEAT, CORN, SOYB, COFFEE, COCOA, COTTON, SUGAR, WTI, NG, COPPER, LUMBER. Returns per-symbol climate stress signal, risk driver, and urgency label. Ideal for daily monitoring, dashboard widgets, and as a triage step before calling forecast.commodity_outlook for detail on flagged symbols. Free.

Input schema present but exposes no named parameters.

NameTypeReqDescription
summarystring–Plain-language summary of which markets are most stressed.
symbolsarray–Per-symbol: symbol, signal (RED/YELLOW/GREEN), urgency, primaryDriver, score.

No examples provided.

forecast.portfolio_stress ~91

Climate stress test for a multi-commodity portfolio. Pass up to 20 positions with weights (percentages or fractions — normalized internally). Returns aggregate portfolio climate score, which positions are most stressed, which could act as climate hedges, and a plain-language summary. Useful for commodity fund managers evaluating aggregate climate exposure before rebalancing.

NameTypeReqDescription
positionsarrayyesPortfolio positions with symbol and weight
NameTypeReqDescription
dominantRiskstring–Most climate-stressed position
hedgeCandidatesarray–Symbols with climateScore ≤ 35 — potential climate hedges
portfolioClimateScorenumber–Weighted aggregate climate stress 0–100
positionsarray–Per-position signal and climate score
stressedPositionsarray–Symbols with climateScore ≥ 65
summarystring––

No examples provided.

forecast.production_regions ~62

All ~40 global commodity production regions ranked by current climate risk score. Each region shows which commodities it affects and its current climate risk level (HIGH/MODERATE/LOW). Use to identify which geographic zones are under active climate stress and which commodities are most exposed.

Input schema present but exposes no named parameters.

NameTypeReqDescription
regionsarray–Regions sorted by climate risk score, with affected commodities and risk level
updatedAtstring––

No examples provided.

forecast.scenario ~171

What-if climate scenario analysis. Apply a named scenario or custom stressor multipliers to any subset of commodities and see how signals shift. Built-in scenarios: la_nina_moderate, la_nina_severe, el_nino_moderate, gulf_hurricane_major, us_plains_drought_severe, black_sea_disruption, brazil_frost, chile_drought_copper, pacific_northwest_wildfire. Use to stress-test a commodity thesis before committing to a position.

NameTypeReqDescription
scenariostring–Built-in scenario ID — or omit and provide stressorOverrides
stressorOverridesobject–Custom multipliers if not using a named scenario (1.0 = no change)
symbolsarray–Symbols to analyze — omit for all 11
NameTypeReqDescription
descriptionstring––
portfolioImpactobject–mostImpacted, leastImpacted, averageClimateScore
resultsarray–Per-commodity signal, climateScore, recommendation, topStressor, reasoning
scenariostring––

No examples provided.

forecast.subscribe ~232

Commodity Alert Webhook — register a URL to receive push alerts when a commodity signal crosses a threshold. Supports alerts on signal changes (BULLISH → BEARISH), confidence drops below a floor, or climate stress score crossing a level. Returns a subscriptionId for management. Alerts fire within 30 minutes of a signal change. Useful for autonomous agents that need to react to commodity market shifts without polling. x402 paid (first month), USDC on Base.

NameTypeReqDescription
alertOnstring–Trigger type. signal_change = any BULLISH/BEARISH/NEUTRAL flip. confidence_drop = confidence falls below threshold. climate_stress = climateScore crosses level. Default: signal_change.
symbolsarrayyesCommodity symbols to monitor. E.g. ["WHEAT", "WTI"]. Use ["*"] for all 11.
thresholdnumber–For confidence_drop: minimum confidence floor (0–1). For climate_stress: score level (0–100). Not used for signal_change.
webhookUrlstringyesHTTPS URL to receive POST alerts.
NameTypeReqDescription
alertOnstring––
subscriptionIdstring–Subscription ID for updates and cancellation.
symbolsarray––
webhookUrlstring––

No examples provided.

forecast.tcfd_report ~176

TCFD Physical Risk Report — generates a Task Force on Climate-related Financial Disclosures (TCFD) physical risk assessment for a commodity portfolio. Maps climate signals from all 11 commodity markets to TCFD physical risk categories (acute and chronic), scores transition risk alignment, and produces a structured report suitable for investor disclosure. Pass portfolio as an array of {symbol, positionUsd}. x402 paid, USDC on Base.

NameTypeReqDescription
horizonstring–Forecast horizon for risk assessment. Default 90d.
portfolioarrayyesArray of {symbol: "WHEAT", positionUsd: 500000}. Symbols: WHEAT · CORN · SOYB · COFFEE · COCOA · COTTON · SUGAR · WTI · NG · COPPER · LUMBER.
NameTypeReqDescription
disclosurestring–Draft TCFD disclosure narrative for the portfolio.
physicalRiskobject–Acute and chronic physical risk scores per commodity, mapped to TCFD categories.
portfolioScorenumber–Aggregate TCFD physical risk score 0–100.
transitionRiskobject–Policy, technology, market, and reputation transition risk signals.

No examples provided.

fx.corridors ~102

All 60+ currency corridors with current stability tier, daily volatility estimate, and regulatory flags. Sort is best-first (OPTIMAL → ADVERSE). Use to compare corridors before choosing a payment route — e.g. "which LATAM corridor is most stable for a $2M payment this week?" Filter by source currency with the from parameter. Free.

NameTypeReqDescription
fromstring–Optional: filter to corridors starting from this currency (e.g. USD)
NameTypeReqDescription
corridorCountnumber––
corridorsarray–Corridors sorted best-first with score, tier, vol, regulatory flags
summaryobject–Count by tier: OPTIMAL / FAVORABLE / CAUTION / ELEVATED_RISK / ADVERSE

No examples provided.

fx.cost_certainty ~166

All-in settlement cost quote for cross-border payments. CFO-grade output: exact amount received in target currency after rail fees, 48h FX cost variance expressed in dollars, corridor stability overlay, and optimal execution window. Answers "if I send $X today, what does my counterparty receive net of everything, and how certain is that number?" Requires x402 micropayment.

NameTypeReqDescription
amountnumberyesAmount to send
amountCurrencystring–Currency of the amount (defaults to from)
fromstringyesSource currency ISO 4217 (e.g. USD)
leistring–Optional counterparty LEI for ESG-adjusted fee tier
tostringyesTarget currency ISO 4217 (e.g. BRL)
NameTypeReqDescription
corridorIntelligenceobject–Corridor stability score, regulatory flags, cascade level
costCertaintyobject–48h volatility, uncertainty in USD, received range in target currency
executionRecommendationobject–SETTLE_NOW / DELAY_24H / DELAY_48H with best execution window UTC
railFeesobject–All-in fee breakdown in USD
settlementobject–Sent and received amounts with live FX rate

No examples provided.

fx.rate ~101

Live mid-market FX rate for any currency pair. Returns mid rate, bid/ask spread, daily volatility %, regulatory flags for the corridor, and data freshness. Sourced from central bank rates (open.er-api.com, updated hourly, no API key required). Free.

NameTypeReqDescription
fromstringyesSource currency ISO 4217 code (e.g. USD)
tostringyesTarget currency ISO 4217 code (e.g. BRL)
NameTypeReqDescription
asknumber––
bidnumber––
corridorFlagsarray–Regulatory flags for this corridor
dailyVolatilityPctnumber–Estimated daily FX volatility %
midnumber–Mid-market rate (from → to)
pairstring––
spreadPctnumber–Implied interbank spread %
updatedAtstring––

No examples provided.

integration.kyriba ~195

Kyriba TMS Integration — DPX settlement bridge for Kyriba treasury management systems. Accepts a Kyriba-formatted payment instruction and executes it through the DPX settlement flow with oracle gating, compliance screening, and stablecoin routing. Returns a Kyriba-compatible confirmation response including settlement ID, execution status, and fee breakdown. The client's own Kyriba OAuth credentials are used — DPX never holds credentials. Useful for treasury teams running Kyriba who want DPX oracle intelligence and on-chain settlement without leaving their TMS workflow. Free (settlement x402 fee charged at execute step).

NameTypeReqDescription
oauthTokenstring–Client's Kyriba OAuth bearer token. Never stored by DPX.
paymentInstructionobjectyesKyriba SPI payment instruction object — amount, currency, counterparty, valueDate.
sandboxboolean–If true, oracle and compliance run live but no on-chain execution. Default true.
NameTypeReqDescription
executionobject–On-chain execution params (sender-funded — client calls approve() + settle()).
kyribaRefstring–Kyriba-format confirmation reference.
settlementIdstring–DPX settlement ID.
statusstring–AUTHORIZED / SANDBOX / HELD / REVIEW / FAILED

No examples provided.

integration.status ~88

Check the status of a DPX integration verification session. Polls Base mainnet for receipt of the $0.01 USDC handshake payment. Returns "pending" until payment is detected on-chain, then "verified" with the txHash and a Basescan explorer link. Poll every 10–15 seconds after sending the payment.

NameTypeReqDescription
idstringyesverificationId returned by integration.verify.
NameTypeReqDescription
explorerstring–Basescan URL for the verification transaction.
idstring––
messagestring––
statusstring–Current verification state.
txHashstring–Transaction hash of the $0.01 payment. Present when verified.
verifiedAtstring–ISO timestamp of on-chain confirmation. Present when status is "verified".
walletAddressstring––

No examples provided.

integration.travel_rule ~230

FinCEN Travel Rule Compliance — generates and transmits Travel Rule records for cross-border payments over $3,000. Creates a FATF R16-compliant record with originator and beneficiary identity data, transaction details, and a cryptographic attestation. Returns a Travel Rule ID for the audit trail. Accepts the same settlement parameters as settlement.execute — use after oracle and compliance gates pass. Can also receive inbound Travel Rule records from counterparty VASPs. Free (included in settlement flow; standalone record creation available).

NameTypeReqDescription
amountUsdnumberyesTransfer amount in USD.
beneficiaryAddressstringyesBeneficiary wallet address.
beneficiaryLeistring–Beneficiary LEI. Optional.
beneficiaryNamestring–Legal name of beneficiary entity. Optional if LEI provided.
originatorAddressstringyesOriginator wallet address.
originatorLeistring–Originator LEI. Optional.
originatorNamestring–Legal name of originator entity. Optional if LEI provided.
purposestring–Payment purpose code.
NameTypeReqDescription
attestationstring–Signed compliance attestation.
statusstring–RECORDED / TRANSMITTED / PENDING_ACK
travelRuleIdstring–FATF R16 Travel Rule record ID.

No examples provided.

Common questions

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.