
NOMOS Cross-Border Broker
Cross-border preflight, x402 quote and evidence receipts for A2A/MCP agent workflows.
What it can do
What data it sees
Do you need an account
No: the server works without sign-in
Cross-border preflight, x402 quote and evidence receipts for A2A/MCP agent workflows.
How to connect
How to connect NOMOS Cross-Border Broker to Claude
The server address to paste into Claude settings:
https://tooloracle.io/mcp/nomos
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect NOMOS Cross-Border Broker to ChatGPT
The server address to paste into ChatGPT settings:
https://tooloracle.io/mcp/nomos
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect NOMOS Cross-Border Broker to Cursor
The server address to paste into Cursor settings:
https://tooloracle.io/mcp/nomos
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (5)
Raw names from tools/list. Only developers need these.
| nomos_crossborder_preflight | Cross-border regulatory preflight for agent data flows. Checks jurisdiction pair (EU, JP, IN, KR, SG, CN, BR, NG, ZA, MX) and data category against a local policy matrix. Returns verdict: ALLOW / ALLOW_PUBLIC_SIGNAL_ONLY / REVIEW / BLOCK (or ERROR for unsupported input), plus blocked_fields, sccs_required, risk_level, matrix_coverage and evidence_hash. Local lookup only — no network access, no legal advice. |
| nomos_asia_market_scan | Read-only view of the most recent local daily scan artifact covering 6 regions: Japan, Singapore/China, India, Korea, Brazil/LatAm, Africa. Returns MCP-ready companies, funded entities, compliance signals. The artifact is written once per day by a separate scanner job; this tool performs no live scanning and no network requests. |
| nomos_mcp_tool_discovery | Search a small static curated catalog of OracleNet MCP tools by keyword and category. Returns tool names, endpoints, protocol support. Local data only — does not probe, crawl or contact any network endpoint. |
| nomos_x402_quote | Get a stateless, unsigned, informational x402 price quote for NOMOS services. Tier 1: $0.02 simple verdict | Tier 2: $0.05 verdict + evidence | Tier 3: $0.10 full packet. Returns payTo address, network (Base mainnet), amount in USDC atomic units, and a deterministic quote digest (not a signature). No payment is initiated and nothing is signed, persisted or reserved; expiry is informational only. |
| nomos_signed_receipt_verify | Look up a NOMOS operation record by its exact SHA-256 receipt hash in the local handshake audit log. Requires a full 64-hex hash, optionally 'sha256:'-prefixed; matching is exact against the stored receipt_hash/entry_hash fields. This is a record lookup, NOT cryptographic signature verification — the response always reports cryptographically_verified: false. |