# NotWorking (remote · notworking.io)

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

- Trust score: 84/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `notworking.io`: 84/100 (this document), [markdown](https://verifymcp.io/servers/io-notworking-notworking/notworking.md), [page](https://verifymcp.io/servers/io-notworking-notworking/notworking)

## Channel facts

- Endpoint: `https://notworking.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 860 tokens (~430/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the NotWorking MCP server?

NotWorking is a hosted endpoint at https://notworking.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-notworking-notworking 'https://notworking.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-notworking-notworking": {
      "url": "https://notworking.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-notworking-notworking": {
      "type": "http",
      "url": "https://notworking.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-notworking-notworking]
url = "https://notworking.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-notworking-notworking": {
      "type": "remote",
      "url": "https://notworking.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-notworking-notworking --url 'https://notworking.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-notworking-notworking:
    url: "https://notworking.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-notworking-notworking": {
      "Transport": "http",
      "Url": "https://notworking.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-notworking-notworking -t streamable-http -u 'https://notworking.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-notworking-notworking": {
      "type": "http",
      "url": "https://notworking.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 84, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-04 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (2)

### `check_status` (~240 tokens)

Is it down for everyone?

Is 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 and 7 days as context), the what_failed values and how to report. Unlisted targets return their own counts and status, with listed: false.

Input parameters:

- `target` (string, required): The URL, access-path id or service name
- `type`: Optional, to disambiguate: site, route, mcp or skill

### `report` (~445 tokens)

Report an access path failure

Report 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.; robots_disallow: The site's robots.txt asks automated agents not to fetch this 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.

Input parameters:

- `agent_type`: Optional: which agent you are; 'other' if not listed
- `country`: Optional ISO-3166 alpha-2 country code, like SG
- `note`: Optional, at most 280 characters, no personal data. Never shown to other agents.
- `target` (string, required): The access-path id (or URL) you used
- `type`: Optional: site, route, mcp or skill. Use mcp for an MCP server that isn't in the catalogue, since its name can look like a domain
- `what_failed` (array, required): How it failed: one or more values

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-notworking-notworking/notworking#diagnostics

## Score history

- 2026-11-06: 84
- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 80
- 2026-10-29: 80
- 2026-10-28: 79
- 2026-10-27: 79
- 2026-10-26: 78
- 2026-10-25: 78
- 2026-10-24: 78
- 2026-10-23: 77
- 2026-10-22: 77
- 2026-10-21: 76
- 2026-10-20: 76
- 2026-10-19: 75
- 2026-10-18: 75
- 2026-10-17: 74
- 2026-10-16: 74
- 2026-10-15: 73
- 2026-10-14: 73
- 2026-10-13: 72
- 2026-10-12: 72
- 2026-10-11: 71
- 2026-10-10: 71

## Common questions

### What is the NotWorking MCP server?

NotWorking is an MCP server listed in the public MCP registry as io.notworking/notworking. Downdetector for AI agents: stop paying for retries that can't succeed. Check once, then report. This page covers its hosted endpoint (https://notworking.io/mcp).

### Is the NotWorking MCP server safe to use?

NotWorking scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the NotWorking MCP server expose?

NotWorking exposes 2 tools: check_status, report. Their descriptions and schemas cost roughly 685 tokens of context every time the server is loaded.

### Does the NotWorking MCP server require authentication?

No. We connected to NotWorking without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the NotWorking MCP server still maintained?

NotWorking is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the NotWorking MCP server?

VerifyMCP ran 13 checks on NotWorking, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://notworking.io/mcp
- Repository: https://github.com/RyanNSJ/notworking
- Website: https://notworking.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-notworking-notworking/notworking.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-notworking-notworking/notworking/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-notworking-notworking/notworking.json
- HTML version of this page: https://verifymcp.io/servers/io-notworking-notworking/notworking