io.github.ifsodev/ifso
IFSO
Is the IFSO MCP server down? Yes. It has given no valid answer since 2026-11-11: TLS error (HTTP 525).
Conditional USDG payments on Robinhood Chain: look up, explain and prepare if-so payments.
TLS error down since 2026-11-11 · probed 2026-11-14 · unchanged since 2026-11-13 · HTTP 525
Streamable HTTP error: Error POSTing to endpoint: {"type":"https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/err- Endpoint
- https://api.ifso.tech/mcp (streamable-http)
- Host
- api.ifso.tech
- Repository
- https://github.com/ifsodev/ifso
- Website
- https://ifso.tech/mcp
- Registry
- active, updated 2026-11-09 · registry entry
- Changes
- 4 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Servers that mention conditional or robinhood.
- hood. — .hood name service ag.hood/name-service · alive
- DripMetrics ai.dripmetrics/mcp · alive
- ai.firmbrain/x402-services · not found
- Otto Data — Robinhood Chain app.ottodata/otto · server error
- BlockVectra Docs: Robinhood Chain & EVM com.blockvectra/docs · alive
- AI Agent Tokenized Stock OS dev.aatos/aatos · alive
- dev.xroot/token-operations · alive
- Hermes Agent Data Services (x402) io.github.AjiGhufron9999/x402-agent-data · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-13 11:36 | TLS error | ||||
| 2026-11-11 11:30 | refused | ||||
| 2026-11-10 11:44 | alive | 1.0 s | 14 | 6.0k | 3.7k |
| 2026-11-09 12:09 | alive | 896 ms | 10 | 4.2k | 2.5k |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-11-11, in every probe since then.
- The TLS handshake fails: an expired or mismatched certificate, or an unsupported protocol version.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.