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/yifanyifan897645/webcheck-mcpWrote 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/yifanyifan897645/webcheck-mcp/webcheck)<a href="https://agentmods.dev/mcp/yifanyifan897645/webcheck-mcp/webcheck"><img src="https://agentmods.dev/badge/mcp/yifanyifan897645/webcheck-mcp/webcheck/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/yifanyifan897645/webcheck-mcp/webcheck"><img src="https://agentmods.dev/badge/mcp/yifanyifan897645/webcheck-mcp/webcheck.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
webcheck 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 9d 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
{
"webcheck": {
"command": "npx",
"args": [
"-y",
"webcheck-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.
- 9d ago First seen · 10 lines scan A 0eaa35c22af6
webcheck is an MCP server published in the GitHub repository yifanyifan897645/webcheck-mcp (3 stars, last pushed 4mo 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
speclock
Enforce project constraints from CLAUDE.md, AGENTS.md, and .cursorrules before AI-generated edits, commands, and commits. Runs locally from the speclock npm package.
architect-to-product
MCP server that turns software architectures into tested, secure products. Runs locally from the architect-to-product npm package.
codebase-memory
MCP server "codebase-memory" as configured in BernhardJackiewicz/architect-to-product. Launched with codebase-memory-mcp.
toon-memory
Offline persistent memory for AI coding agents — 35 tools, 80% fewer calls, no LLM. Runs locally from the toon-memory npm package. Needs 6 environment variables to run.
uiverse-mcp
MCP server "uiverse-mcp" as configured in Fabi-SPL/uiverse-mcp. Runs locally from the uiverse-mcp npm package.
sprintra
The project brain for AI coding agents — memory, decisions, sprints, knowledge base via MCP. Runs locally from the @sprintra/mcp npm package. Needs 3 environment variables to run.