All servers · Build & deploy
NotWorking
io.notworking/notworking · v0.1.3
Tools changed (7 days)
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Can write (some tools are not declared read-only) |
| Capabilities declared | prompts, resources, tools |
| Tool definitions | 2 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Downdetector for AI agents: stop paying for retries that can't succeed. Check once, then report.
Connect
streamable-http · https://notworking.io/mcp
claude mcp add --transport http notworking https://notworking.io/mcp{
"mcpServers": {
"notworking": {
"url": "https://notworking.io/mcp"
}
}
}Tools as reported by the server
check_statusIs it down or blocking agents for everyone, or just you? Use when a site, URL, MCP server or skill isn't working: down, unreachable or an outage, a timeout, blocked (access denied, 403, 429 rate limited, a Cloudflare 'Just a moment' challenge, a CAPTCHA), a login loop, an MCP server that won't connereportReport that an access path failed for you. Use the access-path id from check_status, or the URL you used. Only report failures that came from the service, not ones caused by your own tools, permissions or settings (like a fetch tool that refuses a domain). Anonymous. Never include personal data, boo
Tool changes
- 2026-10-18: check_status, report
- 2026-10-16: check_status, report
Repository · Website · JSON · Text for agents · Registry updated 2026-10-16