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/willianpinho/large-file-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/willianpinho/large-file-mcp/redis)<a href="https://agentmods.dev/mcp/willianpinho/large-file-mcp/redis"><img src="https://agentmods.dev/badge/mcp/willianpinho/large-file-mcp/redis.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
redis 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- redis — 100% identical, 0 lines differ
What it actually says
{
"redis": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-redis"
],
"env": {
"REDIS_URL": "${REDIS_URL}"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 4. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 8d ago First seen · 12 lines scan A 956098b3a919
redis is an MCP server published in the GitHub repository willianpinho/large-file-mcp (19 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-30.
Other mcp servers, from other repositories
cctx-mcp
MCP server for AI agents — structured code analysis that cuts token usage by 87%. Runs locally from the cctx-mcp Python package.
misata
Outcome-conformant synthetic data: realistic multi-table test data that hits the revenue curves, rates, and aggregates you declare, exactly. From a sentence, YAML, or your database. No ML model, no real data. MCP server for AI agents. Runs locally from the misata Python package.
titen-memory
Evidence-grounded agent memory with mandatory provenance, on local SQLite or Cloudflare D1. Runs locally from the titen-memory npm package. Needs 2 environment variables to run.
claudedesktop-warnerco-schematica
MCP server "claudedesktop-warnerco-schematica" as configured in timothywarner-org/context-engineering. Runs locally from the warnerco-mcp Python package. Needs 1 environment variable to run.
mcp-redis-diagnostics
MCP server for Redis diagnostics — analyze memory usage, slowlog, client connections, and keyspace health with AI-powered recommendations. Runs locally from the mcp-redis-diagnostics npm package. Needs 1 environment variable to run.
mcp-java-backend-suite
Complete MCP suite for Java backend developers — database analysis, JVM diagnostics, migration risk, Spring Boot actuator analysis, and Redis diagnostics. Runs locally from the mcp-java-backend-suite npm package.