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/sanjibani/storedge-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/sanjibani/storedge-mcp/storedge_mcp)<a href="https://agentmods.dev/mcp/sanjibani/storedge-mcp/storedge_mcp"><img src="https://agentmods.dev/badge/mcp/sanjibani/storedge-mcp/storedge_mcp/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/sanjibani/storedge-mcp/storedge_mcp"><img src="https://agentmods.dev/badge/mcp/sanjibani/storedge-mcp/storedge_mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
storedge_mcp 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 10d 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
{ "storedge_mcp": { "command": "uvx", "args": [ "storedge_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.
- 10d ago First seen · 8 lines scan A c77f2c0409af
storedge_mcp is an MCP server published in the GitHub repository sanjibani/storedge-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
airtable-mcp-server
A Model Context Protocol server that provides read and write access to Airtable databases. This server enables LLMs to inspect database schemas, then read and write records. Runs locally from the airtable-mcp-server npm package.
adeu
MCP server "adeu" as configured in dealfluence/adeu. Runs locally from the adeu-server Python package.
cc-audit
MCP server "cc-audit" as configured in ryo-ebata/cc-audit. Launched with ./target/release/cc-audit serve.
jobgpt-mcp-server
Job search automation, auto apply, resume builder, application tracking, and recruiter outreach. Runs locally from the jobgpt-mcp-server npm package. Needs 1 environment variable to run.
lain
High-performance knowledge graph MCP server for AI coding agents with semantic search. Runs locally from the @spuentesp/lain-mcp npm package.
molecare-mcp
Educational dermatology knowledge and lesion tooling. No credentials needed. Not a medical device. Runs locally from the molecare-mcp npm package. Needs 5 environment variables to run.