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/swarm-ai-research/swarmWrote 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/swarm-ai-research/swarm/sqlite_runs)<a href="https://agentmods.dev/mcp/swarm-ai-research/swarm/sqlite_runs"><img src="https://agentmods.dev/badge/mcp/swarm-ai-research/swarm/sqlite_runs.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
sqlite_runs 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 3d 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
{
"sqlite_runs": {
"command": "uvx",
"args": [
"mcp-server-sqlite",
"--db-path",
"runs/runs.db"
]
}
}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.
- 3d ago First seen · 10 lines scan A 788446a9d2e3
sqlite_runs is an MCP server published in the GitHub repository swarm-ai-research/swarm (41 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-09-03.
Other mcp servers, from other repositories
postgres
Lets the agent inspect a PostgreSQL database schema and run read-only SQL queries against it. Runs locally from the @modelcontextprotocol/server-postgres npm package.
sql-server-mcp
Local, single-user MCP server for read-only SQL Server / MS Fabric queries - one process per tenant. Runs locally from the sql-server-mcp Python package.
mcp-server-neon
Lets the agent create and manage Neon Postgres projects, branches and databases and run SQL. Runs locally from the @neondatabase/mcp-server-neon npm package.
cloud-sql-postgres
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.
neo4j-mcp-gateway
MCP server "neo4j-mcp-gateway" as configured in jeffneo/neo4j-mcp-gateway. Runs locally from the neo4j-mcp-gateway Python package.
mcp-server-db
MCP server "mcp-server-db" as configured in MadlyFriese/pg-readonly-mcp. Runs locally from the mcp-server-db Python package.