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/esenbora/befall-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/esenbora/befall-mcp/befall)<a href="https://agentmods.dev/mcp/esenbora/befall-mcp/befall"><img src="https://agentmods.dev/badge/mcp/esenbora/befall-mcp/befall/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/esenbora/befall-mcp/befall"><img src="https://agentmods.dev/badge/mcp/esenbora/befall-mcp/befall.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
befall 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 1mo 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
{
"befall": {
"command": "npx",
"args": [
"-y",
"befall",
"mcp"
]
}
}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.
- 1mo ago First seen · 10 lines scan A f5f50c0d7acd
befall is an MCP server published in the GitHub repository esenbora/befall-mcp (0 stars, last pushed 1mo 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
code-context
Local code search for AI coding agents: a CLI and MCP server with hybrid keyword + semantic search and SQL relevance-ranked aggregation over an index that lives in plain files. No accounts, no keys, no server. Runs locally from the @infino-ai/code-context npm package.
tapp
Autonomous QA for iOS + web — agents get a deterministic ship/no-ship verdict, no test code. Runs locally from the tapp-mcp npm package.
stremai
StremAI MCP: shared memory for AI coding agents. Connected agents can recall. OAuth + local stdio. Runs locally from the aiagentsbay-mcp npm package.
rhizome-mcp
MCP server "rhizome-mcp" as configured in Odrin/rhizome-mcp. Launched with rhizome-mcp serve.
fcop
Canonical 25-tool stdio MCP adapter for FCoP 4.0 Core; explicit historical compatibility and optional Relay. Runs locally from the fcop-mcp Python package. Needs 1 environment variable to run.
agent-mcp-hub
One MCP server bridging the Codex, Cursor, OpenCode, Claude, and Antigravity CLI agents. Runs locally from the agent-mcp-hub npm package.