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/evergreen-it-dev/folioWrote 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/evergreen-it-dev/folio/claude-code-folio)<a href="https://agentmods.dev/mcp/evergreen-it-dev/folio/claude-code-folio"><img src="https://agentmods.dev/badge/mcp/evergreen-it-dev/folio/claude-code-folio/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/evergreen-it-dev/folio/claude-code-folio"><img src="https://agentmods.dev/badge/mcp/evergreen-it-dev/folio/claude-code-folio.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
folio 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 6d 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
{
"folio": {
"type": "http",
"url": "${user_config.folio_mcp_url}",
"headers": {
"Authorization": "Bearer ${user_config.folio_token}"
}
}
}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.
- 6d ago First seen · 9 lines scan A 4f12805d4ead
folio is an MCP server published in the GitHub repository evergreen-it-dev/folio (69 stars, last pushed today), 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-10-09.
Other mcp servers, from other repositories
tela
Self-hostable team wiki; agents read & write it via MCP; Atlas turns your repo into a cited wiki. Runs locally from the tela-mcp npm package. Needs 2 environment variables to run.
tela
MCP server "tela", hosted remotely at telawiki.com, as configured in zcag/tela.
core
MCP server "core" as configured in asdecided/core. Runs in Docker (ghcr.io/asdecided/core:mcp-v0.29.0).
jdocmunch-mcp
Token-efficient MCP server for structured documentation retrieval via section-level indexing. Runs locally from the jdocmunch-mcp Python package.
context
MCP server "context", hosted remotely at mcp.context.lc, as configured in Supa-Media/context.
wikikit
MCP server "wikikit" as configured in AvalancheAI-labs/agent-wiki-kit. Runs locally from the wikikit Python package.