Fallback MCP server
io.github.baronsigma/fallback-agent-toolsbaronsigmastreamable-httpv0.1.0-beta.1Scanned
Tiny paid recovery and decision utilities for autonomous agents.
4 tools: 3 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 2
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 Fallback MCP server can do
The Fallback MCP server is published by the GitHub account baronsigma. It has 4 tools. It can create or change data (3 tools: error_route, request_repair and stop_search), but cannot delete data. 1 tool only reads.
2 tools can send data out of your system (error_route and request_repair).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 16, 2026, version 0.1.0-beta.1.
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.
4 tools
Changes things 3Claude Code: ask
error_routeDiagnose a failed API, HTTP, MCP, or tool request and return a bounded safe next action.Can send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a URL (input.request.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Diagnose a failed API, HTTP, MCP, or tool request and return a bounded safe next action. Use it after a request fails when the safe next step is unclear. Provide a status, response, or error text; it does not execute requests or verify undocumented fixes. Price: $0.002 USD per call via x402.
request_repairRepair a failed API or HTTP request using only supplied schema and error evidence.Can send data outNo findings
Why it is in this group
- The name "request_repair" says "request": a word for a change.
What it can reach
- outboundThe input takes a URL (input.request.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Repair a failed API or HTTP request using only supplied schema and error evidence. Use after error_route identifies a request-shape or input problem. Returns the smallest justified request changes and abstains when evidence is insufficient. Price: $0.005 USD per call via x402.
stop_searchDecide whether another search or paid retrieval is worth the cost based on the scope already checked.No findings
Why it is in this group
- The name "stop_search" says "stop": a word for a change.
Description, as the server wrote it Decide whether another search or paid retrieval is worth the cost based on the scope already checked. Use after several search or source checks when you need to decide whether to continue or return a scoped not-found result. It does not prove universal absence and performs no searches itself. Price: $0.003 USD per call via x402.
Only reads 1Show 1 read-only tool
source_routeFind likely authoritative or machine-readable sources when you know what information you need but not where to retrieve it.No findings
Why it is in this group
- The description's first verb is "find": a word for reading.
Description, as the server wrote it Find likely authoritative or machine-readable sources when you know what information you need but not where to retrieve it. Provide a goal and optional publisher domain or start URL; it returns ranked candidate routes and bounded evidence. Use it before blind searching. Do not use it when you already have the correct source or only need reasoning over supplied context. Price: $0.02 USD per call via x402.
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 or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- 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.
Looked at Nov 20, 2026, 19:02 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://fallback.factrail.online/mcp: tools/list returned 4 tools to an anonymous client, including error_route (write), request_repair (write), stop_search (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0-beta.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http fallback-agent-tools https://fallback.factrail.online/mcpclaude mcp add --transport http fallback-agent-tools https://fallback.factrail.online/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__fallback-agent-tools__source_route"
],
"ask": [
"mcp__fallback-agent-tools__error_route",
"mcp__fallback-agent-tools__request_repair",
"mcp__fallback-agent-tools__stop_search"
],
"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 fallback-agent-tools. Review it before you use it.
Capability tags behind 2 rules
- mcp__fallback-agent-tools__error_route outbound
- mcp__fallback-agent-tools__request_repair outbound
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.baronsigma/fallback-agent-tools/verify?hash=112f2cfc52fc8936de22cd045e14c8dda99ab3c00d1bc7263f2ddcc0e02badf5" | jq -e '.changed == false'Pinned hash 112f2cfc52fc, from Nov 16, 2026, 11:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.baronsigma/fallback-agent-tools/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.baronsigma/fallback-agent-tools)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:23 UTC.
Fallback MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Fallback MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Fallback MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Fallback MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Fallback MCP server have?
- 4 tools: 3 write, 1 read. error_route, request_repair, stop_search and source_route.
Does the Fallback MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Fallback MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): error_route and request_repair.
Has the Fallback MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.