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/jeffgreendesign/textrawlWrote 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/jeffgreendesign/textrawl/textrawl-local)<a href="https://agentmods.dev/mcp/jeffgreendesign/textrawl/textrawl-local"><img src="https://agentmods.dev/badge/mcp/jeffgreendesign/textrawl/textrawl-local/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/jeffgreendesign/textrawl/textrawl-local"><img src="https://agentmods.dev/badge/mcp/jeffgreendesign/textrawl/textrawl-local.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
textrawl-local 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 today.
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
{
"textrawl-local": {
"url": "http://localhost:3000/mcp",
"description": "Local Textrawl development server"
}
}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.
- today First seen · 6 lines scan A 44091c6d27c3
textrawl-local is an MCP server published in the GitHub repository jeffgreendesign/textrawl (5 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-16.
Other mcp servers, from other repositories
context-server
Lightweight MCP server for semantic search over organizational markdown. Runs locally from the context-server Python package.
pageindex-local-windows
MCP server "pageindex-local-windows" as configured in jamesbubenik/pageindex-local-mcp. Runs C:\Users\user\pageindex-local-mcp\dist\index.js with node. Needs 9 environment variables to run.
pageindex-local
MCP server "pageindex-local" as configured in jamesbubenik/pageindex-local-mcp. Runs /home/user/pageindex-local-mcp/dist/index.js with node. Needs 9 environment variables to run.
iwe
Markdown knowledge base as agent memory. Runs against the notes directory it is started in. Runs locally from the @iwe-org/mcp npm package.
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.
parse
Deterministic DOCX/PPTX/XLSX/PDF parser: track changes, comments, headers, footers, merged cells. Runs locally from the @ailang/parse npm package. Needs 2 environment variables to run.