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/wiber/thetacog-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/wiber/thetacog-mcp/thetacog-mcp-source)<a href="https://agentmods.dev/mcp/wiber/thetacog-mcp/thetacog-mcp-source"><img src="https://agentmods.dev/badge/mcp/wiber/thetacog-mcp/thetacog-mcp-source/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/wiber/thetacog-mcp/thetacog-mcp-source"><img src="https://agentmods.dev/badge/mcp/wiber/thetacog-mcp/thetacog-mcp-source.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
thetacog-mcp-source 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 yesterday.
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
{ "thetacog-mcp-source": { "command": "npx", "args": [ "-y", "thetacog-mcp-source" ] } }
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.
- yesterday First seen · 9 lines scan A 7455d898d21b
thetacog-mcp-source is an MCP server published in the GitHub repository wiber/thetacog-mcp (1 stars, last pushed yesterday), 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-09-30.
Other mcp servers, from other repositories
strands-docs
A Model Context Protocol server that provides knowledge about building AI agents with Strands Agents. Runs locally from the strands-agents-mcp-server Python package.
impri
Impri MCP server — human-in-the-loop approval inbox for AI agents. Runs locally from the @impri/mcp npm package. Needs 2 environment variables to run.
mdan-method
MDAN — AI-driven development methodology: agents, step-by-step wizards, multi-agent debate and a context graph, as IDE commands and an MCP server. Runs locally from the mdan-method npm package.
perceive
Compact, ref-stable, reachability-filtered perception for AI browser agents. Runs locally from the perceive Python package.
blackveil-dns
MCP server "blackveil-dns", hosted remotely at dns-mcp.blackveilsecurity.com, as configured in MadaBurns/bv-mcp.
creedspace-mcp-server
Constitutional-AI safety guardrails for any LLM — personas, constitutions, adjudication. Runs locally from the @creedspace/mcp-server npm package.