A side-by-side look at the NotWorking and MCP Victoriametrics MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose NotWorking for monitoring work; choose MCP Victoriametrics for monitoring over a hosted endpoint. You can also run both side by side in one mcpServers block.
check_status, report.VM_INSTANCE_ENTRYPOINT, VMC_API_KEY, VM_INSTANCE_TYPE, MCP_SERVER_MODE, MCP_LISTEN_ADDR.Rows where the two servers differ are marked.
| Spec | N NotWorking | |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 53/100 · Good | 45/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Free |
| Required env vars | None listed | VM_INSTANCE_ENTRYPOINTVMC_API_KEYVM_INSTANCE_TYPEMCP_SERVER_MODEMCP_LISTEN_ADDR |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 236 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 2 | Not listed |
| Full listing | View NotWorking | View MCP Victoriametrics |
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.No tool names declared yet. Check the project README from the listing page.
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
No confirmed install command for NotWorking yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"mcp-victoriametrics": {
"url": "https://play-mcp.victoriametrics.com/mcp"
}
}
}