Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/lazymac2x/mcpwatchWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/lazymac2x/mcpwatch/mcp-server-mcpwatch)<a href="https://agentmods.dev/mcp/lazymac2x/mcpwatch/mcp-server-mcpwatch"><img src="https://agentmods.dev/badge/mcp/lazymac2x/mcpwatch/mcp-server-mcpwatch/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/lazymac2x/mcpwatch/mcp-server-mcpwatch"><img src="https://agentmods.dev/badge/mcp/lazymac2x/mcpwatch/mcp-server-mcpwatch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcpwatch scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"mcpwatch": {
"command": "npx",
"args": [
"-y",
"mcpwatch-mcp"
],
"env": {}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 10 lines scan A 953700ac571a
mcpwatch is an MCP server published in the GitHub repository lazymac2x/mcpwatch (0 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
smart-data-extractor
Cloudflare Workers MCP server wrapper: smart-data-extractor. Runs locally from the lazymac-mcp-smart-data-extractor npm package.
agent-workflow-engine
Cloudflare Workers MCP server: agent-workflow-engine. Remote server at api.lazy-mac.com.
urantia-papers
Free, open MCP server for The Urantia Papers. 197 papers, 14,500+ paragraphs, 4,400+ entities. Remote server at api.urantia.dev.
api-mock-server
Cloudflare Workers MCP server: api-mock-server. Remote server at api.lazy-mac.com.
code-explainer
Cloudflare Workers MCP server: code-explainer. Remote server at api.lazy-mac.com.
api-mock-generator
MCP server "api-mock-generator" as configured in lazymac2x/api-mock-generator. Runs locally from the @lazymac/api-mock-generator npm package.