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/Lambenthan/empiricalwikiWrote 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/lambenthan/empiricalwiki/llm-review)<a href="https://agentmods.dev/mcp/lambenthan/empiricalwiki/llm-review"><img src="https://agentmods.dev/badge/mcp/lambenthan/empiricalwiki/llm-review/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/lambenthan/empiricalwiki/llm-review"><img src="https://agentmods.dev/badge/mcp/lambenthan/empiricalwiki/llm-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
llm-review 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.
This is a copy
100% identical to llm-review — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"llm-review": {
"command": "python3",
"args": [
"mcp-servers/llm-review/server.py"
],
"cwd": "${workspaceFolder}"
}
}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 · 9 lines scan A 87c306d1c19a
llm-review is an MCP server published in the GitHub repository Lambenthan/empiricalwiki (82 stars, last pushed 2mo 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. It is 100% identical to llm-review, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
pm-copilot
MCP server "pm-copilot" as configured in Leo-maomao/pm-copilot. Runs ./scripts/pm_copilot_mcp.py with python3.
mcp-fns-calc
A local MCP server for Russian tax calculations and checks of taxpayer status. It uses a hosted API for fiscal-status checks and needs an access token.
mcp-quipu
Quipu API integration with 18 MCP tools for invoices, expenses, contacts and Spanish VAT reporting. Runs locally from the @nubiia/mcp-quipu npm package. Needs 3 environment variables to run.
carrier-accounting-mcp
MCP Server for insurance carrier accounting — ingest carrier PDFs/Excel, reconcile against Applied Epic, post entries. Built for US insurance agencies. Runs locally from the carrier-accounting-mcp Python package.
thinking-prompts
MCP server "thinking-prompts" as configured in zdrjson/thinking-prompts-skill. Runs locally from the thinking-prompts npm package.
recon
ReCoN: [Reconstruction of multicellular systems from single-cell data to predict perturbation responses and cell programs coordination]. Runs locally from the recon Python package.