# Fallback (remote · fallback.factrail.online)

Tiny paid recovery and decision utilities for autonomous agents.

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `fallback.factrail.online`: 69/100 (this document), [markdown](https://verifymcp.io/servers/baronsigma-fallback-agent-tools/fallback.md), [page](https://verifymcp.io/servers/baronsigma-fallback-agent-tools/fallback)

## Channel facts

- Endpoint: `https://fallback.factrail.online/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0-beta.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 467 tokens (~116/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Fallback MCP server?

Fallback is a hosted endpoint at https://fallback.factrail.online/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http baronsigma-fallback-agent-tools 'https://fallback.factrail.online/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "baronsigma-fallback-agent-tools": {
      "url": "https://fallback.factrail.online/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "baronsigma-fallback-agent-tools": {
      "type": "http",
      "url": "https://fallback.factrail.online/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.baronsigma-fallback-agent-tools]
url = "https://fallback.factrail.online/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "baronsigma-fallback-agent-tools": {
      "type": "remote",
      "url": "https://fallback.factrail.online/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add baronsigma-fallback-agent-tools --url 'https://fallback.factrail.online/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  baronsigma-fallback-agent-tools:
    url: "https://fallback.factrail.online/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "baronsigma-fallback-agent-tools": {
      "Transport": "http",
      "Url": "https://fallback.factrail.online/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add baronsigma-fallback-agent-tools -t streamable-http -u 'https://fallback.factrail.online/mcp'
```

### Other

```json
{
  "mcpServers": {
    "baronsigma-fallback-agent-tools": {
      "type": "http",
      "url": "https://fallback.factrail.online/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `source_route` (~134 tokens)

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.

Input parameters:

- `domain` (string)
- `goal` (string, required)
- `max_candidates` (integer)
- `preferred_formats` (array)
- `require_official` (boolean)
- `start_url` (string)

### `error_route` (~110 tokens)

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.

Input parameters:

- `attempt` (integer)
- `error` (string)
- `goal` (string)
- `request` (object)
- `response` (object)

### `request_repair` (~112 tokens)

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.

Input parameters:

- `constraints` (object)
- `error` (string)
- `error_route` (object)
- `goal` (string)
- `request` (object, required)
- `response` (object)
- `schema`

### `stop_search` (~111 tokens)

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.

Input parameters:

- `checks` (array)
- `goal` (string)
- `remaining_routes` (array)
- `risk` (string)
- `search_budget` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/baronsigma-fallback-agent-tools/fallback#diagnostics

## Score history

- 2026-11-04: 69
- 2026-11-03: 69
- 2026-11-02: 68
- 2026-11-01: 68
- 2026-10-31: 67
- 2026-10-30: 67
- 2026-10-29: 66
- 2026-10-28: 66
- 2026-10-27: 66
- 2026-10-26: 65
- 2026-10-25: 65
- 2026-10-24: 64
- 2026-10-23: 64
- 2026-10-22: 63
- 2026-10-21: 63
- 2026-10-20: 62
- 2026-10-19: 62
- 2026-10-18: 61
- 2026-10-17: 61
- 2026-10-16: 60
- 2026-10-15: 60
- 2026-10-14: 59
- 2026-10-13: 59
- 2026-10-12: 59
- 2026-10-10: 58
- 2026-10-08: 57

## Common questions

### What is the Fallback MCP server?

Fallback is an MCP server listed in the public MCP registry as io.github.baronsigma/fallback-agent-tools. Tiny paid recovery and decision utilities for autonomous agents. This page covers its hosted endpoint (https://fallback.factrail.online/mcp).

### Is the Fallback MCP server safe to use?

Fallback scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Fallback MCP server expose?

Fallback exposes 4 tools: source_route, error_route, request_repair, stop_search. Their descriptions and schemas cost roughly 467 tokens of context every time the server is loaded.

### Does the Fallback MCP server require authentication?

No. We connected to Fallback without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Fallback MCP server still maintained?

Fallback is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://fallback.factrail.online/mcp
- Repository: https://github.com/baronsigma/fallback-agent-tools
- Website: https://fallback.factrail.online/
- Changelog RSS feed: https://verifymcp.io/servers/baronsigma-fallback-agent-tools/fallback.xml
- Changelog JSON feed: https://verifymcp.io/servers/baronsigma-fallback-agent-tools/fallback.json
- HTML version of this page: https://verifymcp.io/servers/baronsigma-fallback-agent-tools/fallback