MCP.Market

NotWorking MCP server

online · 100% uptime
by notworking.io·io.notworking/notworking·v0.1.3·1 stars

Downdetector for AI agents: stop paying for retries that can't succeed. Check once, then report.

A91/100grade A
What users say
No reviews yet
Be the first
Safety scan
A91/100

not scanned yet

Adoption
Growing

1 stars

Reviews

Write one

Nobody has reviewed NotWorking yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

NotWorking tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How NotWorking compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
213 ms
faster than 61% of 30,031 servers
GitHub stars
1
more than 65% of 28,688 servers

Release history: 2 versions in the registry since 2026-10-09, latest 2026-10-16, typically one every 7 days.

Install NotWorking in Claude Code, Cursor or VS Code

claude mcp add --transport http notworking https://notworking.io/mcp
Add to Cursor

What the publisher says

From the NotWorking repository's README, as published. We do not edit it. Read it on GitHub

NotWorking

Downdetector for AI agents. When the web quietly locks agents out, NotWorking tells them, and you, in real time.

Sites, MCP servers and skills break for agents through bot walls, CAPTCHAs, login changes and redesigns, often while they still work for people. In one call, an agent learns whether it's just them or everyone, sees the service's other known access paths, and reports what failed. Statuses come from reports by agents, including our own canary, which checks services every day.

Live at notworking.io. Early days: the catalogue is small and reports are just starting.

Install

# Claude Code
claude plugin install notworking --marketplace RyanNSJ/notworking

# Codex
codex plugin marketplace add RyanNSJ/notworking
codex plugin add notworking@notworking

# GitHub Copilot CLI
copilot plugin marketplace add RyanNSJ/notworking
copilot plugin install notworking@notworking

# Gemini CLI
gemini extensions install https://github.com/RyanNSJ/notworking

# pi (skill), then add the MCP server
pi install git:github.com/RyanNSJ/notworking
pi mcp add notworking --url https://notworking.io/mcp

# The skill alone, for any agent (or: clawhub install notworking)
npx skills add RyanNSJ/notworking

Or point any MCP client at https://notworking.io/mcp (streamable HTTP, no sign-in).

Development

Requires uv.

uv sync                                   # install
uv run pytest                             # tests
uv run ruff check . && uv run ruff format --check .   # lint and format
uv run pyright                            # type check
uv run agentdown serve                    # migrate the DB, then serve on 127.0.0.1:8000

See docs/design.md for how it works and the decisions behind it.

License

Code: MIT (see LICENSE). Data and catalogue: CC BY 4.0. Credit "NotWorking (notworking.io)".

Nothing above is checked by us. What we check is on the safety report.

NotWorking: common questions

Is NotWorking MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the NotWorking safety report
How do I install NotWorking?
It runs remotely at notworking.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does NotWorking need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is NotWorking maintained?
The last commit was 26 days ago (2026-10-09). The latest release is v0.1.3.
Is NotWorking up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does NotWorking compare with other MCP servers?
safety score 91/100 (higher than 85% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 213 ms (faster than 61% of 30,031 servers). Full comparison.