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/gemini-cli-extensions/lookerWrote 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/gemini-cli-extensions/looker/looker-dev)<a href="https://agentmods.dev/mcp/gemini-cli-extensions/looker/looker-dev"><img src="https://agentmods.dev/badge/mcp/gemini-cli-extensions/looker/looker-dev.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
looker-dev 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 2d 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.
This is a copy
94% identical to looker — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"looker-dev": {
"command": "npx",
"args": [
"-y",
"@toolbox-sdk/[email protected]",
"--prebuilt",
"looker-dev",
"--stdio"
],
"env_vars": [
"LOOKER_BASE_URL",
"LOOKER_CLIENT_ID",
"LOOKER_CLIENT_SECRET",
"LOOKER_VERIFY_SSL",
"LOOKER_SHOW_HIDDEN_MODELS",
"LOOKER_SHOW_HIDDEN_EXPLORES",
"LOOKER_SHOW_HIDDEN_FIELDS"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. 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.
- 2d ago First seen · 21 lines scan A c02e135071a5
looker-dev is an MCP server published in the GitHub repository gemini-cli-extensions/looker (54 stars, last pushed 2d ago), 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. It is 94% identical to looker, differing in 4 lines, and is treated as a copy.
Other mcp servers, from other repositories
dataplex
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.
firestore
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.
spanner
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.
cloud-sql-mysql
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.
oracledb
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.
cloud-sql-mssql
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.