Use IFSO
from your AI assistant.

What it is

MCP (Model Context Protocol) is a common way for AI assistants like Claude, ChatGPT, Cursor, VS Code and others to use outside tools. IFSO runs an MCP server at https://api.ifso.tech/mcp. Once your assistant knows that address, you can ask it things like "what is the fee for a match result payment?" and it asks IFSO for you.

What it can do

• READ
  ifso_list_conditions

  What a payment can wait for (a date, a price, a match result, a Polymarket question, both of you tapping OK, or a referee), with example commands and the amount limits.

• READ
  ifso_quote_fees

  The fee for a condition type, and with an amount the total to approve. Fees are flat and never a share of the amount.

• PREP
  ifso_prepare_payment

  Turns a command like "/ifso 0x... 20 on 2026-12-01" into a preview and the unsigned transactions for your own wallet to sign.

• READ
  ifso_list_payments

  The payments an address sent or received, newest first, 20 at a time.

• READ
  ifso_get_payment

  The current state of one payment, read from the chain.

• READ
  ifso_explain_payment

  One payment in plain words: what it waits for, the deadline, who can do what next and when it comes back.

• READ
  ifso_version

  The running build, the chain and every contract address, to check before approving anything.

• PREP
  ifso_prepare_v2_payment

  A v2 payment in USDG, USDe or ETH with its own payment address, known before any money moves, plus the unsigned data for your wallet to sign. Nothing is signed or sent.

• READ
  ifso_get_v2_payment

  One v2 payment by its payment address: the terms, whether the money arrived, and its live state on the chain.

• PREP
  ifso_create_request

  Ask to be paid: a request link for an amount of USDG, USDe or ETH that the payer opens to fund a payment to you. Nothing moves until they fund it.

• PREP
  ifso_prepare_x402_conditional

  For a seller: x402 payment details where the money waits at the payment's own address and reaches the seller after a release window, unless the buyer disputes.

• READ
  ifso_check_x402_offer

  For a buyer: checks an x402 pay-on-delivery offer against IFSO's own contract before you sign, and refuses one that does not match.

• PREP
  ifso_dispute

  For the buyer, inside the release window: what to sign to dispute a pay-on-delivery payment, and the API call that sends it with IFSO paying the gas. The tool itself signs nothing.

• READ
  ifso_release_status

  The state of a pay-on-delivery payment: waiting, arrived, disputed, paid to the seller or back to the buyer.

It never signs

The IFSO MCP server only reads and prepares. It never signs, never holds a key and never sends anything. When it prepares a payment, you review it and sign in your own wallet. Check the contract addresses with ifso_version before you approve anything.

Set it up

Claude Code: run this once in a terminal.

claude mcp add --transport http ifso https://api.ifso.tech/mcp

Claude Desktop and claude.ai: open Settings, then Connectors, choose Add custom connector and paste the address.

https://api.ifso.tech/mcp

Cursor: add this to ~/.cursor/mcp.json (or .cursor/mcp.json in a project).

{
  "mcpServers": {
    "ifso": {
      "url": "https://api.ifso.tech/mcp"
    }
  }
}

ChatGPT: where your plan offers custom connectors (developer mode), add a remote MCP server with the address above.

VS Code (GitHub Copilot agent mode): add this to .vscode/mcp.json in your project.

{
  "servers": {
    "ifso": {
      "type": "http",
      "url": "https://api.ifso.tech/mcp"
    }
  }
}

Windsurf: add this to ~/.codeium/windsurf/mcp_config.json.

{
  "mcpServers": {
    "ifso": {
      "serverUrl": "https://api.ifso.tech/mcp"
    }
  }
}

Gemini CLI: add this to ~/.gemini/settings.json.

{
  "mcpServers": {
    "ifso": {
      "httpUrl": "https://api.ifso.tech/mcp"
    }
  }
}

Any other MCP client: add a remote (HTTP) MCP server with the address above. Clients that take JSON usually accept this; the key names can differ, so check your client's guide.

{
  "mcpServers": {
    "ifso": {
      "type": "http",
      "url": "https://api.ifso.tech/mcp"
    }
  }
}

Tested with: the official MCP TypeScript client (@modelcontextprotocol/sdk) and the official MCP Python client (mcp), which connected to the live server, listed all 7 tools and called ifso_version, ifso_quote_fees and ifso_list_conditions. On 9 November 2026 the TypeScript client listed all 14 tools on the live server and called ifso_get_v2_payment. The app steps above are setup steps: app menus can change, so if a step looks different, add a remote MCP server with this address.

Try it

• "What kinds of IFSO payments can I make?"
• "What does an IFSO payment on a Polymarket question cost for 20 USDG?"
• "List the IFSO payments for 0x... and explain the newest one."
• "Prepare an IFSO payment of 20 USDG to 0x... that unlocks on December 1."

Limits

60 messages a minute per network, 64 KB per request and 20 messages per batch. No sign-up and no key. Opening https://api.ifso.tech/mcp in a browser shows the same setup steps.