Is agentleFS MCP server down?
Live status and uptime of the agentleFS remote MCP endpoint. MCP Canary connects to it once a day from outside, lists its tools, and records what changed.
Current status
Up (sign-in required)
100% uptime over 30 days. Checked once a day.
Last 90 days
- Uptime 30 days
- 100%
- Uptime 90 days
- —
- Response time
- —
- Protocol
- —
Endpoint
- URL
- https://mcp.agentlefs.com/mcp
- Transport
- Streamable HTTP
- Sign-in
- unknown
- Category
- File Storage
Sign-in health
agentleFS asks for sign-in. Without credentials, MCP Canary follows the same steps an MCP client takes before it opens the login page.
How to connect agentleFS MCP
agentleFS is a remote server: nothing to install.
Claude Code
claude mcp add --transport http agentlefs https://mcp.agentlefs.com/mcp
Cursor (.cursor/mcp.json)
{ "mcpServers": { "agentlefs": { "url": "https://mcp.agentlefs.com/mcp" } } }
VS Code (.vscode/mcp.json)
{ "servers": { "agentlefs": { "type": "http", "url": "https://mcp.agentlefs.com/mcp" } } }
Claude (web and desktop)
Settings → Connectors → Add custom connector, then paste https://mcp.agentlefs.com/mcp.
Tools
The tool list as the server returned it on the last check. Servers that need sign-in do not list tools without credentials.
Tool changes
A tool added or removed, or an argument or schema changed. Agents that call agentleFS break on these changes without an error on the server side.
- No tool changes seen in the last 90 days.
Incidents
- No incidents in the last 90 days.
Questions
Is the agentleFS MCP server down right now?
The status at the top of this page is the result of the last daily check. MCP Canary connects to https://mcp.agentlefs.com/mcp the way an AI agent does (Streamable HTTP, then legacy SSE), and lists its tools. A failure counts as down only after a second check 30 seconds later fails too.
Why does it say "sign-in required"?
The server answered 401 or 403: it runs and asks for credentials, as OAuth and API key servers do. That counts as up. The check never uses credentials, so the tools behind the sign-in are not listed. It does follow the sign-in chain (the 401 challenge, the protected resource metadata, and the login server) and shows the result under "Sign-in health": if that chain breaks, users cannot connect even though the server answers.
How do I get alerted when agentleFS MCP breaks?
This page checks once a day. To watch it every minute, with a real tool call, assertions on the answer, and email or webhook alerts, set up your own monitor: install the canary CLI and ask your coding agent to monitor it. The 7-day trial needs no card.