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/orifisher2/sqlikeWrote 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/orifisher2/sqlike/sqlike-mcp)<a href="https://agentmods.dev/mcp/orifisher2/sqlike/sqlike-mcp"><img src="https://agentmods.dev/badge/mcp/orifisher2/sqlike/sqlike-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/orifisher2/sqlike/sqlike-mcp"><img src="https://agentmods.dev/badge/mcp/orifisher2/sqlike/sqlike-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sqlike-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
{
"sqlike-mcp": {
"command": "npx",
"args": [
"-y",
"@sqlike/mcp"
],
"env": {
"SQLIKE_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.
- 10d ago First seen · 12 lines scan A b6f67991d738
sqlike-mcp is an MCP server published in the GitHub repository orifisher2/sqlike (6 stars, last pushed yesterday), licensed Apache-2.0. 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
dryrun
PostgreSQL schema intelligence from a committed snapshot. No connection, no credentials. Runs locally from the @boringsql/dryrun npm package.
remem
Local-first automatic memory for Claude Code and Codex: capture, distill, recall from SQLite. Runs locally from the @remem-ai/remem npm package.
dbconvert-streams
Read-only SQL across PostgreSQL, MySQL, S3 buckets and local data files — one query can join across all of them. MCP server. Runs locally from the @dbconvert/stream-mcp npm package. Needs 1 environment variable to run.
postgres
MCP server "postgres" as configured in gabrimatic/mcp-web-search-tool. Runs in Docker (mcp/postgres).
mysql-mcp
MCP server "mysql-mcp" as configured in neverinfamous/mysql-mcp. Runs in Docker (docker.io/writenotenow/mysql-mcp:v1.0.0).
schemabrain
The trust and intelligence layer between AI agents and your database. Runs locally from the schemabrain Python package. Needs 1 environment variable to run.