io.github.lazymac2x/mcpwatch
NPM · MCPWATCH-MCP · SCANNED SEP 20
Audit MCP servers from inside Claude Code. 10 OWASP checks, A-F grade, live leaderboard.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 161 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 396 tokens (~99/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.lazymac2x/mcpwatch MCP server?
io.github.lazymac2x/mcpwatch runs locally as an npm package, launched with npx -y mcpwatch-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcpwatch-mcp
claude mcp add lazymac2x-mcpwatch -- npx -y mcpwatch-mcp
{
"mcpServers": {
"lazymac2x-mcpwatch": {
"command": "npx",
"args": [
"-y",
"mcpwatch-mcp"
]
}
}
} {
"servers": {
"lazymac2x-mcpwatch": {
"command": "npx",
"args": [
"-y",
"mcpwatch-mcp"
]
}
}
} codex mcp add lazymac2x-mcpwatch -- npx -y mcpwatch-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lazymac2x-mcpwatch": {
"type": "local",
"command": [
"npx",
"-y",
"mcpwatch-mcp"
],
"enabled": true
}
}
} openclaw mcp add lazymac2x-mcpwatch --command npx --arg -y --arg mcpwatch-mcp
mcp_servers:
lazymac2x-mcpwatch:
command: "npx"
args: ["-y", "mcpwatch-mcp"] {
"McpServers": {
"lazymac2x-mcpwatch": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcpwatch-mcp"
]
}
}
} assistant mcp add lazymac2x-mcpwatch -t stdio -c npx -a -y mcpwatch-mcp
{
"mcpServers": {
"lazymac2x-mcpwatch": {
"command": "npx",
"args": [
"-y",
"mcpwatch-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +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.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +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.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/mcpwatch-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_badge_url ~61
Return the URL of a live MCPWatch SVG grade badge for a GitHub repository. Drop this into any README to show the current MCPWatch grade.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | GitHub owner |
| repo | string | yes | GitHub repository name |
No output schema declared.
No examples provided.
get_leaderboard ~97
Fetch the current MCPWatch leaderboard of public MCP servers ranked by security grade. Returns the most recently scanned set with per-repo grade, score, and finding count. Use this to pick a safe MCP server from a set of candidates.
| Name | Type | Req | Description |
|---|---|---|---|
| grade_filter | string | – | Optional letter grade filter (A, B, C, D, F) |
| limit | integer | – | Maximum number of entries to return (default: 20) |
No output schema declared.
No examples provided.
scan_directory ~150
Run the MCPWatch security scanner on a local directory. Returns a 0-100 score, A-F letter grade, and findings from the 10 OWASP MCP Top 10 checks (command injection, path traversal, SSRF, prompt injection via tool descriptions, unauthenticated mutations, secret leakage, over-permissive filesystem scopes, missing rate limits, outdated dependencies, missing input schema validation).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Optional name for the target (defaults to the directory basename) |
| path | string | yes | Absolute path to the directory to scan |
| sarif | boolean | – | If true, return findings as a SARIF v2.1.0 document for GitHub Code Scanning |
No output schema declared.
No examples provided.
scan_github_repo ~88
Fetch the latest MCPWatch scan result for a public GitHub repository from the live crawler. Use this when you want to audit an MCP server by its GitHub owner/repo name instead of cloning it locally. Returns the same grade + findings shape as scan_directory.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | GitHub owner (user or org) |
| repo | string | yes | GitHub repository name |
No output schema declared.
No examples provided.
What is the io.github.lazymac2x/mcpwatch MCP server?
io.github.lazymac2x/mcpwatch is an MCP server listed in the public MCP registry as io.github.lazymac2x/mcpwatch. Audit MCP servers from inside Claude Code. 10 OWASP checks, A-F grade, live leaderboard. This page covers its npm package (mcpwatch-mcp).
Is the io.github.lazymac2x/mcpwatch MCP server safe to use?
io.github.lazymac2x/mcpwatch scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.lazymac2x/mcpwatch MCP server expose?
io.github.lazymac2x/mcpwatch exposes 4 tools: scan_directory, scan_github_repo, get_leaderboard, get_badge_url. Their descriptions and schemas cost roughly 396 tokens of context every time the server is loaded.
Is the io.github.lazymac2x/mcpwatch MCP server still maintained?
io.github.lazymac2x/mcpwatch is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.lazymac2x/mcpwatch MCP server under?
io.github.lazymac2x/mcpwatch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.