Monitoring MCP server
online · 100% uptimeSite & competitor monitoring: snapshots, evidence-backed diffs, briefs, price checks, mentions.
B70/100grade B
Adoption
New
Little public usage data yet
Reviews
Write oneNobody has reviewed Monitoring yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Monitoring tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
1 low
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 143ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenanceno repository listed3/15
- Maintainer identityverified namespace with website, no repo4/10
Findings (1)
- lowNo source repository listed
maint.no-repo
Overall 70/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
How Monitoring compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 70/100
- higher than 35% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 30 ms
- faster than 95% of 30,031 servers
Install Monitoring in Claude Code, Cursor or VS Code
claude mcp add --transport http monitoring https://mcp.openhelm.ai/watch/mcp
Monitoring: common questions
- Is Monitoring MCP server safe?
- Mostly: it is graded B (70/100). Read the Monitoring safety report
- How do I install Monitoring?
- It runs remotely at mcp.openhelm.ai. 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 Monitoring need an API key?
- No key to paste: it signs you in with OAuth when your client connects.
- Is Monitoring maintained?
- The latest release is v0.1.0.
- Is Monitoring up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Monitoring compare with other MCP servers?
- safety score 70/100 (higher than 35% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 30 ms (faster than 95% of 30,031 servers). Full comparison.