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/Sprintra-io/sprintra-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/sprintra-io/sprintra-mcp/sprintra)<a href="https://agentmods.dev/mcp/sprintra-io/sprintra-mcp/sprintra"><img src="https://agentmods.dev/badge/mcp/sprintra-io/sprintra-mcp/sprintra/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/sprintra-io/sprintra-mcp/sprintra"><img src="https://agentmods.dev/badge/mcp/sprintra-io/sprintra-mcp/sprintra.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sprintra 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 12d 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
{ "sprintra": { "command": "npx", "args": [ "-y", "@sprintra/mcp" ], "env": { "VIBEPILOT_MODE": "local", "SUPABASE_DATABASE_URL": "", "GEMINI_API_KEY": "" } } }
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.
- 12d ago First seen · 14 lines scan A e79c0bcf0167
sprintra is an MCP server published in the GitHub repository Sprintra-io/sprintra-mcp (3 stars, last pushed 2mo 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
codebase-memory
MCP server "codebase-memory" as configured in BernhardJackiewicz/architect-to-product. Launched with codebase-memory-mcp.
toon-memory
Offline persistent memory for AI coding agents — 35 tools, 80% fewer calls, no LLM. Runs locally from the toon-memory npm package. Needs 6 environment variables to run.
memorix
Local-first project memory with legacy MCP and 2026 discovery compatibility. Runs locally from the memorix npm package.
state-memory-mcp
MCP server "state-memory-mcp" as configured in putervision/state-memory-mcp. Launched with state-memory-mcp run.
speclock
Enforce project constraints from CLAUDE.md, AGENTS.md, and .cursorrules before AI-generated edits, commands, and commits. Runs locally from the speclock npm package.
engram
Ranked local code-graph context for AI coding agents. Intercepts reads + greps. Apache-2.0. Runs locally from the engramx npm package. Needs 5 environment variables to run.