Skip to content

Cursor DPX — Institutional Cross-Border Settlement ledger.session

How to: Cursor DPX — Institutional Cross-Border Settlement ledger.session

client:Cursor transport:streamable-http tool:ledger.session

Add DPX — Institutional Cross-Border Settlement to Cursor

  1. 01

    Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "dpx": {
      "url": "https://mcp.untitledfinancial.com/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

    Ask for something ledger.session does. Cursor lists the server's tools on connect and calls ledger.session itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that DPX — Institutional Cross-Border Settlement's identifier in your config matches the one above exactly.

Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs

Set these first

DPX — Institutional Cross-Border Settlement will not start until these are set, so ledger.session never becomes available.

  • STABILITY_ORACLE_URL
  • SETTLEMENT_AGENT_URL
  • INTELLIGENCE_URL
  • SANDBOX_MODE

Same tool, other clients

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.