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/pvoo/bigquery-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/pvoo/bigquery-mcp/bigquery)<a href="https://agentmods.dev/mcp/pvoo/bigquery-mcp/bigquery"><img src="https://agentmods.dev/badge/mcp/pvoo/bigquery-mcp/bigquery/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/pvoo/bigquery-mcp/bigquery"><img src="https://agentmods.dev/badge/mcp/pvoo/bigquery-mcp/bigquery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
bigquery 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 1mo 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
{
"bigquery": {
"command": "uvx",
"args": [
"bigquery-mcp",
"--project",
"your-project-id",
"--location",
"US",
"--max-bytes-billed",
"21474836480"
]
}
}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.
- 1mo ago First seen · 14 lines scan A f7fc7a80653a
bigquery is an MCP server published in the GitHub repository pvoo/bigquery-mcp (10 stars, last pushed 4mo 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
graphmemory-ide
MCP server "graphmemory-ide" as configured in elementalcollision/GraphMemory-IDE. Runs locally from the graphmemory-ide npm package.
db-explorer
MCP server "db-explorer", hosted remotely at db-explorer-mcp.fastmcp.app, as configured in AYUSH-148/DB-Explorer-MCP.
amnesic
The MCP server with the most ironic name in the registry — persistent semantic memory for your SQL databases. Runs locally from the amnesic Python package.
bq-readonly-mcp
Read-only BigQuery MCP server with auto-LIMIT, dry-run cost guard, and ADC auth — for Claude, Cursor, Windsurf, Copilot, and other MCP clients. Runs locally from the bq-readonly-mcp Python package.
anydb-mcp
Universal database connector for AI agents (Cursor, Claude, Gemini, Zed, Cline). Zero-config MCP server for PostgreSQL, MySQL, SQLite, MongoDB, and Redis. Runs locally from the anydb-mcp npm package.
same
Persistent memory for AI coding agents. Local-first SQLite + vector search, 12 MCP tools. Runs locally from the @sgx-labs/same npm package. Needs 1 environment variable to run.