settlement.status — DPX — Institutional Cross-Border Settlement MCP Tool
settlement.status
(settlement status) is one of 85 tools on the
DPX — Institutional Cross-Border Settlement
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call settlement.status from your client
- Claude Code DPX — Institutional Cross-Border Settlement settlement.status run in your project directory
- Claude Desktop DPX — Institutional Cross-Border Settlement settlement.status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor DPX — Institutional Cross-Border Settlement settlement.status ~/.cursor/mcp.json
- VS Code DPX — Institutional Cross-Border Settlement settlement.status .vscode/mcp.json
- Zed DPX — Institutional Cross-Border Settlement settlement.status ~/.config/zed/settings.json
- Windsurf DPX — Institutional Cross-Border Settlement settlement.status ~/.codeium/windsurf/mcp_config.json
- Cline DPX — Institutional Cross-Border Settlement settlement.status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI DPX — Institutional Cross-Border Settlement settlement.status ~/.gemini/settings.json
- Grok DPX — Institutional Cross-Border Settlement settlement.status .mcp.json (in your project root)
- ChatGPT DPX — Institutional Cross-Border Settlement settlement.status Settings → Connectors → Advanced → Developer mode
- Claude.ai DPX — Institutional Cross-Border Settlement settlement.status Settings → Connectors → Add custom connector
- LangChain DPX — Institutional Cross-Border Settlement settlement.status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http dpx https://mcp.untitledfinancial.com/mcpOther tools on this server
- protocol.manifest
- settlement.quote
- esg.score
- esg.lookup
- esg.batch
- esg.watch
- esg.portfolio
- intelligence.subscribe
- intelligence.subscription.get
- intelligence.subscription.delete
- esg.trend
- oracle.governance
- compliance.ubo_chain
- compliance.pep_screen
- compliance.regulatory_calendar
- defi.concept_lookup
- defi.research_papers
- stability.corridor
- stability.settlement_window
- stability.stablecoin_route
- agent.kya_register
- agent.mandate_create
- agent.kya_verify
- forecast.commodity_outlook
- forecast.portfolio_stress
- forecast.scenario
- forecast.production_regions
- forecast.calendar
- fx.rate
- fx.cost_certainty
- fx.corridors
- oracle.stability
- oracle.status
- fees.schedule
- fees.verify
- fees.compare
- route
- flow_check
- batch_settle
- invoice.create
- invoice.get
- invoice.pay
- settle.subscribe
- analytics.overview
- settlement.execute
- settlement.nl
- computer_use.pay
- oracle.rails
- protocol.investment_context
- dpx.metrics
- integration.verify
- integration.status
- ramp.connect
- ramp.spend_analysis
- ramp.agent_card
- ramp.settle
- ramp.compliance_screen
- market.cascade
- oracle.mycelium
- intelligence.tectonic
- intelligence.aftershock
- intelligence.contagion
- intelligence.resonance
- intelligence.gender_risk
- market.shipping
- market.fx
- treasury.yield_route
- mercury.accounts
- mercury.transactions
- mercury.send
- mercury.ach_authorize
- mercury.sweep
- swift.gpi_track
- policy.create
- policy.check
- policy.delegate
- receipt.create
- ledger.session
- search_docs
- card.positions
- card.settle
- compute.models
- compute.cost
- compute.route
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.