IFSO is answering right now. Last checked 1 min ago. It exposes 14 tools. Last commit 10 Nov 2026.
Conditional USDG payments on Robinhood Chain: look up, explain and prepare if-so payments.
Uptime history
9 hours of history
9 hours agonow
100.0%
Uptime 24h
32 of 32 checks
14
Tools
read from the server
612 ms
Response time
average over 24h
0
Stars
last commit 10 Nov 2026
What changed 8
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 10 November 2026. No other catalogue keeps this.
10 Nov
a tool changed version8 times that day
and 7 more, back to 10 November 2026
Nothing serious here today
Today is the operative word: we check IFSO every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.
run in your terminal
claude mcp add ifso --transport http https://api.ifso.tech/mcpSettings → Connectors → Add custom connector, then paste this address
https://api.ifso.tech/mcp~/.codex/config.toml
[mcp_servers.ifso]
url = "https://api.ifso.tech/mcp".cursor/mcp.json
{
"mcpServers": {
"ifso": {
"url": "https://api.ifso.tech/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"ifso": {
"type": "http",
"url": "https://api.ifso.tech/mcp"
}
}
}Available tools 14
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
ifso
ifso_check_x402_offer
Run before signing a 402 that carries the ifso-conditional extension. Recomputes the payment address from the terms against IFSO's own v2.1 factory and refuses: an untrusted factory, a terms hash mismatch, a payTo that is not the terms' address, an amount or asset mismatch, a sender that is not the payer, a refund address that is not the payer, expired terms, a closed window or a window without a referee. Optionally checks the signed EIP-3009 authorization (to, value, from). Read only.
ifso_create_request
Creates a payment request: someone asks to be paid an amount of USDG, USDe or ETH, and gets a link to share. The payer opens the link and funds an if-so payment to them. An optional note (at most 140 characters) and how many days the link stays open (1 to 30, default 7). Nothing moves until the payer funds it.
ifso_dispute
For the buyer, inside the release window: returns the EIP-712 Decision (action 5, dispute) to sign with the buyer's wallet, and the relay call (POST /v1/v2/vaults/{vault}/dispute with the signature) that sends it with IFSO paying the gas. After a dispute only the referee decides (or the buyer's own OK, or the seller's decline); a silent referee means the money comes back at expiry. This tool never signs.
ifso_explain_payment
One if-so payment in plain words, from the same chain read as ifso_get_payment: what it waits for, the deadline, who can do what next (claim, accept, tap OK, decide, settle, send back, cancel) and when and where it comes back if nothing happens. Payment ids are large whole numbers; pass them as a string.
ifso_get_payment
The current state of one if-so payment, read from the chain: status (OPEN, MET, RELEASED, RETURNED, VOIDED, CANCELLED), amount in USDG, sender, recipient or claim link key, expiry and the condition that unlocks it. Payment ids are large whole numbers (up to 78 digits); pass them as a string.
ifso_get_v2_payment
One v2 if-so payment by its payment address: the terms, the asset and amount, whether the money has arrived, and the live state on the chain (not opened yet, OPEN, MET, RELEASED, RETURNED or CANCELLED).
ifso_list_conditions
The kinds of condition an if-so payment can wait for (a date, a price at or by a deadline, a football league result, a Polymarket question, both people tapping OK, or a named referee), with example commands, the price tickers, the timing rules and the amount limits read from the contract. Use the example command format with ifso_prepare_payment.
ifso_list_payments
The if-so payments where an address is the sender or the recipient, newest first, 20 at a time (the same list as the web dashboard, from the IFSO index of the chain, up to the newest 100). Each item has the id, status, amount, the other side and the expiry. Pass nextCursor back as cursor for the next page. For the live chain state of one payment use ifso_get_payment.
ifso_prepare_payment
Turns a command like "/ifso 0x... 20 on 2026-12-01" into a plain preview and the UNSIGNED data to create that if-so payment from the sender's own wallet: two transactions (USDG approve, then create) or one gasless authorization to sign. This server never signs, never holds a key and never sends anything; the sender reviews and signs in their own wallet. Same checks as the site's build step.
ifso_prepare_v2_payment
Builds a v2 if-so payment in USDG, USDe or ETH and returns its own payment address, known before any money moves, so it can be funded from anywhere on Robinhood Chain (any wallet, or the Robinhood app, which can send ETH and USDG to any address). Also returns the UNSIGNED data the sender may sign instead: an EIP-3009 authorization for USDG, a Permit2 signature for USDe, or one fundETH transaction for ETH. The money moves when the condition is met, or comes back to the sender after the expiry. This server never signs and never sends.
ifso_prepare_x402_conditional
For a seller's 402: returns x402 v2 PaymentRequirements (scheme exact, USDG on Robinhood Chain eip155:4663, payTo = the payment's own IFSO v2.1 address) plus the ifso-conditional extension with the full terms. Any facilitator that settles USDG there lands the money at that address. The seller is paid after the release window unless the buyer disputes before it ends; a dispute goes to the named referee, and if the referee stays silent the money comes back to the buyer at expiry. The flat agent fee (0.02 USDG) is added to the amount. Nothing is signed or sent.
ifso_quote_fees
The fee for an if-so payment of one condition kind (TIME, PRICE, SPORTS, MARKET, APPROVE_PARTIES or APPROVE_REFEREE): the flat creation fee, plus the flat result fee for SPORTS and MARKET, read from the contract (the same numbers as ifso_version). With an amount, also the total the sender approves and whether the amount is inside the contract's limits. Fees are flat and never a share of the amount.
ifso_release_status
The state of an x402 conditional payment by its terms hash (the x402 payment identifier): pending (no money yet), settled (the money is at the address), duplicate_swept (a second settle landed and went back to the buyer), disputed, released (paid to the seller) or returned (back to the buyer), with the window end and expiry. Retrying a settle with the same terms lands at the same address, so this tells failed from landed late. Read only.
ifso_version
Which IFSO build is running, the chain id (Robinhood Chain mainnet is 4663), the address of every contract it uses (payments, conditions, outcome resolver, USDG) and the fee constants in base units and USDG. The same answer as GET /v1/version. Check these addresses before approving anything in a wallet.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://api.ifso.tech/mcp | streamable-http | answering | 611 ms | 1 min ago |
Alternatives to IFSO
same job, measured the same wayBorro
by borro
Stock lending on Robinhood Chain: read markets and prepare lends, loans, shorts and credit lines.
Lincoln
by lincolnprotocol-com
Private balance on Robinhood Chain for AI agents: send, swap and withdraw ETH, USDG and stocks.
Toll — coin, agent and pre-sign checks on Robinhood Chain
by t0ll
Robinhood Chain checks for agents: coins, LARP, devs, agents, v4 hooks, pre-sign, Stock Tokens.
Epsilon
by alienbase-xyz
Non-custodial limit, stop-loss and DCA trading on Epsilon (Robinhood Chain) for AI agents
Steve Guard
by stevesignals-api
Solana + Robinhood-Chain token safety & net-USD accumulation intel for trading agents.
Agon Protocol
by agonx402
MCP server for Agon Protocol state reads and prepare-only payment-channel actions.
XDC AI
by 0xbeny
Wallet and payments for AI agents: auto-pay x402 APIs in USDC on XDC, within on-chain limits.
Whiteflow
by vishal4742
USDT payment links, payments and collection summaries on Whitechain testnet. Can't move money.
IFSO — questions
Answers built from our own checks of this server.
What can IFSO do?
It exposes 14 tools, read directly from the server on our last check. Among them: ifso_check_x402_offer, ifso_create_request, ifso_dispute, ifso_explain_payment, ifso_get_payment, ifso_get_v2_payment and 8 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is IFSO working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 32 of 32 checks got a reply (100.0%), average response time 612 ms. The bar chart above shows every period we have measured.
How do I connect IFSO?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does IFSO need an API key?
No. IFSO completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is IFSO?
It answers our handshake in 612 ms on average, which is faster than 17% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is IFSO open source?
The code is open source: it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at api.ifso.tech, which runs on its operator's own terms.