monitoringoutage-detectionmcpagent-access
Checks whether websites, MCP servers, and skills are failing for agents or experiencing a broader outage.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
One-click editor setup isn’t available for this listing yet — we don’t have a confirmed install command, and we’d rather show nothing than point your editor at the wrong package or host. Follow the project’s own setup instructions, linked above.
Manual Client & Custom JSON ConfigExpand JSON ▾
No confirmed setup config for this listing yet. We only publish a config block when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for NotWorking, and we’d rather show nothing than a guess you’d paste into your client. Follow the project’s own setup instructions for the current steps.
Overview
Use cases
Check whether an agent-facing website outage affects other users
Compare recent reports for an MCP server that will not connect
Identify whether a CAPTCHA or bot block is service-wide
Report a failed skill or API access path anonymously
Key features
Check service status by URL, name, or access-path ID
Show one-hour reports with 24-hour context
List alternate access paths for known services
Classify agent failures with standard categories
Submit anonymous access-failure reports
Capabilities & Tool Schemas (2)
Inspect callable tools, capabilities, and parameters exposed to AI agents by NotWorking.
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 connect or a tool that errors, or a skill that fails. Look up a service by the URL you used, an access-path id (clawhub:<owner>/<slug>, skills.sh:<owner>/<repo>/<skill>, an MCP Registry name like io.github.<owner>/<server>) or a service name. Returns a one-sentence summary, the service, every listed access path with a description and failure reports from the last hour (and the last 24 hours as context), the what_failed values and how to report. Unlisted targets return their own counts and status, with listed: false.
reportReport 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, booking details, credentials or full URLs with query strings. target is which access path failed; what_failed is how, from this list (the same for every service): site_unreachable: The site or server could not be reached at all, for example a DNS error, a timeout or a 5xx server error.; bot_block: The service refused the agent: an access-denied page, a 403 or 429 error, a bot wall or a challenge page.; captcha: A CAPTCHA or 'are you human?' check stopped the agent.; login_auth: Logging in or authenticating failed, for example a login loop, a new login step or rejected credentials.; api_error: An API the agent used returned an error or an unexpected response.; mcp_error: An MCP server failed to connect, initialise, list its tools or run a tool.; skill_failed: A skill could not be installed, or it ran but errored or produced a wrong result.; payment: A payment or checkout step failed or was blocked.; specific_page: One particular page or step failed while the rest of the service seemed to work.; other: Something else went wrong.
How NotWorking works
What NotWorking MCP server does
NotWorking MCP server provides outage and access-failure checks for websites, MCP servers, and agent skills. It is intended for cases where a service may still work for people but fails when accessed by an agent. The service collects reports from agents and a daily canary, then exposes recent status information through MCP.
The catalogue can identify services by the URL used, a service name, or an access-path identifier. Supported identifier formats include clawhub:<owner>/<slug>, skills.sh:<owner>/<repo>/<skill>, and MCP Registry names such as io.github.<owner>/<server>.
This server belongs in the Monitoring category when an agent needs evidence about whether a failure is local or shared. The catalogue is described as small and reports are still accumulating, so an absent or sparse result is not proof that a service is healthy.
How it works
The check_status tool returns a short status summary, the matched service, its listed access paths, descriptions, and failure reports. Results cover reports from the previous hour, with the previous 24 hours included for context. The response also includes the recorded what_failed values and instructions for submitting a report. If the target is not in the catalogue, the response returns its own counts and status with listed: false.
The report tool records an anonymous failure against an access-path identifier or the URL used. Reports should describe a failure caused by the service itself, rather than a restriction from the agent’s own permissions, settings, or fetch tools. Failure categories include unreachable services, bot blocks, CAPTCHAs, authentication failures, API errors, MCP errors, skill failures, payment problems, page-specific failures, and other issues.
Setup and configuration
NotWorking MCP server is available at https://notworking.io/mcp as a streamable HTTP MCP endpoint and does not require sign-in. Any MCP client that can connect to that endpoint can use it. The README also documents installation through Claude Code, Codex, Gemini CLI, pi, and the skills CLI. The repository includes a local development path using uv sync and uv run agentdown serve, which serves on 127.0.0.1:8000 after migrating the database.
Tools and capabilities
check_status: inspect a service, URL, access path, or service name and compare recent reports.report: submit an anonymous report for a failed access path.- Classify failures using the shared
what_failedvalues across services. - Review alternate listed access paths and their descriptions.
Limitations and notes
NotWorking MCP server should not receive personal data, booking details, credentials, or full URLs containing query strings. The report tool is for service-caused failures, not problems created by local tools, permissions, or settings. The catalogue and report history are early-stage, and unlisted targets are explicitly marked rather than treated as catalogue-confirmed services.
The code is licensed under MIT. The data and catalogue use CC BY 4.0 and require credit to “NotWorking (notworking.io)” when applicable.
Related MCP Servers
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
GitHub stars
2
Stargazers on the source repository.
Last commit
1d ago
Most recent push to the default branch.
Tools exposed
2
Callable tools this server registers over MCP.
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about NotWorking
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/notworking)HTML Embed
<a href="https://allmcps.com/mcp/notworking"><img src="https://allmcps.com/api/badge/notworking?style=directory" alt="NotWorking on AllMCPs" /></a>Technical Specs & Signals
CategoryMonitoring
PricingFree
53Quality signal: Good · 53/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership10/20
Documentation & tools25/30
Adoption & activity5/15
Community engagement0/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
What it can do
From the 2 tools this server returned when we ran it.
Handles credentials · 1Makes network requests · 2Read-only tools · 2
Observed 2026-10-15 in an isolated sandbox. A description of reach, not a security audit.
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.
Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.