Fallback MCP server
Commit 6 Okt 2026Menyediakan utilitas pemulihan dan pengambilan keputusan yang deterministik bagi autonomous agent untuk mendiagnosis kegagalan, memperbaiki request, dan menemukan sumber data.
Juga dikenal sebagai baronsigma/fallback-agent-tools, fallback-agent-tools
- Stars
- 0
- Tools
- 4
- Unduhan, 30 hari
- —
- Versi terbaru
- 0.1.0-beta.1
- Commit terakhir
- 6 Okt 2026
- Lisensi
- MIT
Apa itu Fallback MCP?
Menyediakan utilitas pemulihan dan pengambilan keputusan yang deterministik bagi autonomous agent untuk mendiagnosis kegagalan, memperbaiki request, dan menemukan sumber data. Server ini menyediakan 4 tool, seperti source_route, error_route, request_repair.
Ringkasan dibuat dari README proyek
Tentang Fallback MCP server
Fallback menyediakan rangkaian utilitas deterministik yang dirancang untuk membantu autonomous agent dalam menghadapi kegagalan dan titik pengambilan keputusan. Alih-alih mengandalkan loop reasoning yang mahal saat agent mengalami kendala, tool ini menawarkan fungsi kecil dan terspesialisasi untuk mendiagnosis error atau menemukan data. Layanan ini tersedia sebagai hosted MCP endpoint atau melalui HTTP API, menggunakan model x402 V2 pay-per-call di Base mainnet dengan USDC. Anda tidak memerlukan akun atau API key, karena pengguna menyetujui pembayaran untuk setiap pemanggilan tool secara spesifik.
Developer dapat menggunakan tool spesifik seperti source_route untuk menemukan format data yang dapat dibaca mesin, error_route untuk mengklasifikasikan request yang gagal, request_repair untuk menyarankan perbaikan minor berdasarkan bukti yang ada, dan stop_search untuk menentukan apakah investigasi lebih lanjut sepadan dengan biayanya. Sistem ini dibangun untuk presisi, menawarkan tindakan terukur seperti menemukan API atau dataset dari domain tertentu. Setiap pemanggilan tool memiliki batasan yang ditentukan, seperti maksimum 8 direct HTTP request dan total waktu eksekusi 12 detik per panggilan.
Apa yang bisa Anda lakukan dengannya
- 1Menemukan sumber data yang dapat dibaca mesinAgent dapat mengidentifikasi cara terbaik untuk mengakses dataset tertentu dalam format JSON atau CSV dari penerbit yang sudah diketahui.
- 2Mendiagnosis dan pulih dari kegagalan requestKetika sebuah API atau pemanggilan tool gagal, agent dapat mengklasifikasikan error tersebut untuk menentukan tindakan aman selanjutnya.
- 3Memperbaiki request yang malformedAgent dapat mengusulkan perubahan minimal pada sebuah request menggunakan bukti yang tersedia agar request tersebut menjadi valid.
- 4Mengoptimalkan pengeluaran pencarianAgent dapat memutuskan apakah melanjutkan pencarian secara ekonomis dapat dibenarkan berdasarkan bukti yang ada saat ini.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal Fallback MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal Fallback MCP di Claude Code
$ claude mcp add --transport http fallback-agent-tools https://fallback.factrail.online/mcpInstal Fallback MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"fallback-agent-tools": {
"url": "https://fallback.factrail.online/mcp"
}
}
}Instal Fallback MCP di VS Code
.vscode/mcp.json
{
"servers": {
"fallback-agent-tools": {
"type": "http",
"url": "https://fallback.factrail.online/mcp"
}
}
}Instal Fallback MCP di VS Code CLI
$ code --add-mcp '{"name":"fallback-agent-tools","type":"http","url":"https://fallback.factrail.online/mcp"}'Instal Fallback MCP di Codex
$ codex mcp add fallback-agent-tools --url https://fallback.factrail.online/mcpInstal Fallback MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.fallback-agent-tools] url = "https://fallback.factrail.online/mcp"
Instal Fallback MCP di Gemini CLI
$ gemini mcp add -s user --transport http fallback-agent-tools https://fallback.factrail.online/mcpInstal Fallback MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"fallback-agent-tools": {
"url": "https://fallback.factrail.online/mcp",
"type": "http"
}
}
}Tool Fallback MCP 4
Terdeteksi dari READMEsource_routeerror_routerequest_repairstop_search
| source_route | — | |
| error_route | — | |
| request_repair | — | |
| stop_search | — |
Pengecekan otomatis
Berjalan 15 Nov 2026Laporan lengkap →Belum diverifikasi. Sebuah server memerlukan skor 80, tidak ada temuan serius, dan data yang cukup untuk kami periksa. Cara kerja checks · Yang perlu diperbaiki untuk menambah poin
- Source repository terhubung dan dapat dijangkaubaronsigma/fallback-agent-tools is public and reachablegithub.com/baronsigma/fallback-agent-tools ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernyaTidak diperiksa
- Provenance build (atestasi Sigstore)Tidak diperiksa
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-10-06github.com/baronsigma/fallback-agent-tools ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerTidak diperiksa
- Tidak ada advisory kritis pada paket atau dependensinyaTidak diperiksa
- Tidak ada instruksi tersembunyi untuk model4 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelNo tool named like delete, drop or execLolos
- Endpoint remote merespons handshake MCPinitialize answered with protocol 2025-06-18 in 490 msLolos
README
Lihat di GitHubFallback
______ _ _
| ____| | | |
| |__ __ _ | | |__ __ _ ___| | __
| __|/ _` || | '_ \ / _` |/ __| |/ /
| | | (_| || | |_) | (_| | (__| <
|_| \__,_||_|_.__/ \__,_|\___|_|\_\
find the route forward
Fallback
Tiny paid recovery and decision utilities for autonomous agents.
When an agent gets stuck, Fallback helps it find the next safe move without wasting a large reasoning loop.
source_route Where should I look? ($0.02)
error_route Why did this fail? ($0.002)
request_repair Can I safely fix the request? ($0.005)
stop_search Is another search worth it? ($0.003)
Use Fallback
Pay-per-call tools that help AI agents find sources, diagnose failures, repair requests, and decide when to stop searching. Fallback gives autonomous agents small, deterministic utilities for the moments where automation gets stuck: finding the right source, diagnosing a failed request, repairing a request from available evidence, and deciding whether another search or paid retrieval is worth the cost.
Hosted service
MCP endpoint: https://fallback.factrail.online/mcp\
HTTP API base: https://fallback.factrail.online\
Payment: x402 V2 pay-per-call. Check each live challenge for network, asset, amount, and recipient.
Agent skill: skill.md
OpenAPI: openapi.json
Network: Base mainnet, canonical USDC
Release: v0.1.0-beta.1
Tools
source_route($0.02): Where should I look? Find likely authoritative or machine-readable sources.error_route($0.002): Why did my call fail? Classify a failed request and recommend a bounded next action.request_repair($0.005): Can I safely fix the request? Propose the smallest change supported by caller-supplied evidence.stop_search($0.003): Is further searching worth it? Decide whether more bounded search effort is justified by the evidence and remaining cost.
These tools do not replace agent reasoning, and stop_search never proves universal absence.
When an agent should use this
Use source_route when an agent knows what it needs and which publisher (a domain or start URL), but not how to get it in machine-readable form: an API, OpenAPI spec, bulk download, dataset or feed.
- Good fit: "Get the latest population dataset from Eurostat", "Find a JSON/CSV route for this agency's statistics", before the agent starts browsing page by page.
- Not a fit: general web research, answering a factual question, or verifying a fact (for source-backed facts, see FACTRAIL MCP).
How to read the result:
status: routes_found: try routes in order.scoreis a deterministic ranking, not a probability or confidence.status: no_suitable_route_found: nothing suitable within the checked scope (seechecked.direct_probes). This is not evidence that no route exists. The agent should look elsewhere (another host, the publisher's open-data portal), not conclude "there is no API".- Always read
limitations. It says, for example, whether external search was unavailable or candidate inspection was capped.
Limits per call: at most 8 direct HTTP requests, 12 s total, 1 MiB per response, and at most 1 external search request. No LLM inference. The hosted beta currently runs deterministic discovery only (no search provider configured).
Access: hosted MCP https://fallback.factrail.online/mcp (Streamable HTTP) or the HTTP tool routes, x402 pay-per-call (each challenge declares its payment network and amount; no account or API key). To try it without payment, self-host with PAYMENT_MODE=disabled (see Local development). Machine-readable summary: llms.txt. More detail: Using Fallback with agents.
Fallback is publicly launched. See the current launch and distribution status, product rename impact audit, discovery/distribution readiness audit, and telemetry and 30-day KPI definitions.
When to use error_route
Use it after an HTTP, API, MCP, or tool request fails when the safe next action is unclear. It classifies supplied evidence and returns bounded retry guidance. Do not use it when recovery is already obvious or the task needs deeper domain reasoning; it does not execute requests or invent undocumented fixes.
Requirements
- Current Node.js LTS (Node 24 at scaffold creation; supported engine is Node 22+)
- npm
Local development
npm install
cp .env.example .env
npm run generate
npm run dev
The server exposes /, /healthz, /readyz, /catalog.json, /openapi.json, /llms.txt, /llms-full.txt, /skill.md, /.well-known/x402.json, /.well-known/mcp/server-card.json, and the Streamable HTTP MCP endpoint at /mcp. Both HTTP and MCP dispatch through the shared runtime handler registry. PAYMENT_MODE=disabled supports local development; paid deployments must explicitly select test or production and provide complete x402 configuration.
Verification
npm test
npm run typecheck
npm run lint
npm run benchmark:source-route
npm run benchmark:error-route
npm run verify:catalog
npm run release:check
30-second start
Connect an x402-compatible agent to https://fallback.factrail.online/mcp, call the matching tool after a concrete failure or search decision, and approve only the network, token, recipient, and amount shown by its payment challenge. HTTP clients can use POST /v1/tools/{tool_id} on the hosted origin. See skill.md for examples and schemas.
Architecture
src/core/registry.ts is the one canonical tool registry. Every discovery surface and distribution artifact is derived from it. Each tool gets a directory under src/tools/ with a contract and handler; future tool tests and fixtures belong alongside the matching contract test/fixture directories. HTTP and MCP adapters must call the same tool handler. Payment middleware and marketplace integrations stay outside tool logic.
The service supports x402 V2 per-call payment without accounts or API keys. The server only receives payment at X402_PAY_TO; no receiving wallet private key is required. Paid startup fails closed if the required network, receiving address, facilitator URL, or production URL is missing or invalid. See deployment and payment setup.
Example
{
"goal": "Download the latest population dataset",
"start_url": "https://ec.europa.eu/eurostat/",
"preferred_formats": ["csv", "json"]
}
Call POST /v1/tools/source_route with a goal and either start_url or domain. The result is limited to the checked scope; a missing result does not mean that no route exists. Direct site discovery runs without external search credentials. If Tavily or Brave is configured and direct discovery is insufficient, the tool can make at most one search request.
See PRODUCT, ARCHITECTURE, TOOL_ADMISSION, DISTRIBUTION, and RELEASE.
Related: FACTRAIL MCP
Fallback comes from the same author and design rule as FACTRAIL MCP: agent tools should report what they checked, not only what they found. FACTRAIL answers "what is established about this fact, and from which source?" by returning evidence envelopes with support levels, unresolved fields and receipts ("unknown is better than invented"). Fallback answers "where can I get this data?" ("absence is not proof of nonexistence"). The two are independent services with no code dependency, and you can use either one alone.
Pertanyaan tentang Fallback MCP
Bagaimana cara menambahkan Fallback MCP ke Claude Code?
Jalankan claude mcp add --transport http fallback-agent-tools https://fallback.factrail.online/mcp di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan Fallback MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Tool apa yang disediakan Fallback MCP?
Server ini menyediakan 4 tool, termasuk source_route, error_route, request_repair, stop_search.
Apa kegunaan dari tool source_route?
Tool ini membantu agent menemukan sumber yang kemungkinan besar bersifat otoritatif atau dapat dibaca mesin seperti API, spesifikasi OpenAPI, atau dataset ketika agent mengetahui penerbitnya tetapi tidak mengetahui rute data spesifiknya.
Bagaimana tool error_route membantu sebuah agent?
Tool ini mengklasifikasikan alasan mengapa sebuah request gagal dan merekomendasikan tindakan selanjutnya yang terukur untuk membantu agent melakukan pemulihan.
Apakah tool stop_search membuktikan bahwa suatu informasi tidak ada?
Tidak, tool ini memutuskan apakah pencarian lebih lanjut sepadan dengan biayanya, tetapi tidak pernah membuktikan ketiadaan informasi secara universal.
Bagaimana sistem pembayaran untuk tool ini ditangani?
Layanan ini menggunakan model x402 V2 pay-per-call, di mana agent menyetujui network, asset, jumlah, dan penerima yang ditampilkan dalam payment challenge.