Cloud storage and content workspace built for AI agents. Gives agents their own workspaces to create, organize, search, and share files alongside your team. - **Files & folders** — full CRUD, versions, locks, previews for 10+ formats, chunked uploads up to 1GB - **Semantic search** — find files by meaning, not just keywords - **AI chat (RAG)** — ask questions across a whole workspace with citations - **Sharing & portals** — send, receive, or exchange files with password protection and expiration - **Webhooks** — real-time notifications for file events - **Ownership transfer** — agents can build a workspace, then hand it off to a human who keeps the agent's admin access Docs: https://api.fast.io/llms.txt · Setup: https://mcp.fast.io/skill.md
fastio-mcp is a remote MCP server published at mcp.fast.io. It has been probed 7 times since 9/10/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 817 ms, a delay an agent will notice. It exposes a broad tool surface of 19 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
intent — Description is overly technical, lacks clear use-case triggers for agent invocationshare — Functionally overlaps with 'fileshare' despite distinct 'durable single-file' focusmetadata — Vague parameter references (e.g., 'fields-list' without schema details)how-to — Implied 'explain-only' behavior not clearly differentiated from actionable toolsdownload — Mentions 'zip-url' but lacks explicit file-size or format constraintsRisk: medium
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/fastio-fastio-mcp)<a href="https://mcpmetrics.io/servers/fastio-fastio-mcp"><img src="https://mcpmetrics.io/badge/fastio/fastio-mcp/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-11 13:13:33 | Legacy | 400 | 509 | 200 | 1419 | 2025-11-25 |
| 2026-09-11 11:20:19 | Legacy | 400 | 413 | 200 | 1606 | 2025-11-25 |
| 2026-09-11 09:28:19 | Legacy | 400 | 319 | 200 | 1633 | 2025-11-25 |
| 2026-09-11 07:35:54 | Legacy | 400 | 376 | 200 | 1623 | 2025-11-25 |
| 2026-09-11 05:44:28 | Legacy | 400 | 546 | 200 | 1416 | 2025-11-25 |
| 2026-09-11 03:50:39 | Legacy | 400 | 817 | 200 | 1767 | 2025-11-25 |
| 2026-09-10 21:16:35 | Auth-gated | 401 | 420 | 401 | 361 | — |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.