Skip to content

IFSO MCP server

io.github.ifsodev/ifsoifsodevstreamable-httpv1.0.0Scanned

Conditional USDG payments on Robinhood Chain: look up, explain and prepare if-so payments.

7 tools: 1 do something that can't be undone, 2 change things and 4 only read.

Tools: 0 delete, 1 irreversible, 2 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 1
  • 1 finding

Sign-in required, no OAuth metadata. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the IFSO MCP server can do

The IFSO MCP server is published by the GitHub account ifsodev. It has 7 tools. It can do things that cannot be undone, such as sending, paying or publishing (ifso_prepare_payment) and create or change data (2 tools: ifso_version and ifso_quote_fees), but cannot delete data. 4 tools only read.

2 tools bring in text other people can write (ifso_prepare_payment and ifso_list_payments); 1 tool can send data out of your system (ifso_prepare_payment).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Last scanned Nov 9, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Can't be undone 1Claude Code: ask
  • ifso_prepare_paymentTurns a command like "/ifso 0x...Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "ifso_prepare_payment" says "payment": a word that usually means money moves, which cannot be taken back.
    • The input addresses people (input.recipient): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.recipient): what the tool writes goes there.

    Findings

    • Warn

      The server marks "ifso_prepare_payment" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "ifso_prepare_payment" says "payment": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Prepare an IFSO payment (unsigned)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 2Claude Code: ask
  • ifso_quote_feesThe 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: IFSO fees for a payment
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • ifso_versionWhich 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 consta…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: IFSO build and contracts
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • ifso_explain_paymentOne 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 b…No findings

    Why it is in this group

    • The name "ifso_explain_payment" says "explain": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Explain an IFSO payment
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • ifso_get_paymentThe 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 …No findings

    Why it is in this group

    • The name "ifso_get_payment" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: IFSO payment status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • ifso_list_conditionsThe 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 refer…No findings

    Why it is in this group

    • The name "ifso_list_conditions" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: IFSO condition types and limits
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • ifso_list_paymentsThe 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 newe…Reads text others writeNo findings

    Why it is in this group

    • The name "ifso_list_payments" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "web": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: IFSO payments for an address
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 16, 2026, 14:21 UTC, unchanged since Nov 16, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
525
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 525.

Posture changes

  1. Nov 16, 2026
    • HTTP status of an anonymous initialize: 200 to 525
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "ifso_prepare_payment" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "ifso_prepare_payment" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 525; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 3 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 525
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__ifso__ifso_get_payment",
      "mcp__ifso__ifso_list_conditions",
      "mcp__ifso__ifso_list_payments",
      "mcp__ifso__ifso_explain_payment"
    ],
    "ask": [
      "mcp__ifso__ifso_version",
      "mcp__ifso__ifso_prepare_payment",
      "mcp__ifso__ifso_quote_fees"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ifso. Review it before you use it.

Capability tags behind 2 rules
  • mcp__ifso__ifso_prepare_payment untrusted-input, outbound
  • mcp__ifso__ifso_list_payments untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.ifsodev/ifso/verify?hash=f90efbdcc40c479db1a0d3769cf4abb5f71a735be40ae678d672a5b06da32e24" | jq -e '.changed == false'

Pinned hash f90efbdcc40c, from Nov 9, 2026, 05:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.ifsodev/ifso/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.ifsodev/ifso
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.ifsodev/ifso.svg)](https://radar.anlyon.com/servers/io.github.ifsodev/ifso)

Source: MCP Registry · repository. Synced Nov 9, 2026, 06:17 UTC.

IFSO MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the IFSO MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the IFSO MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the IFSO MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: ifso_prepare_payment.

What tools does the IFSO MCP server have?

7 tools: 1 irreversible, 2 write, 4 read. ifso_prepare_payment, ifso_version, ifso_quote_fees, ifso_get_payment, ifso_list_conditions, ifso_list_payments and ifso_explain_payment.

Does the IFSO MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the IFSO MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): ifso_prepare_payment.

Has the IFSO MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 9, 2026.