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/thein-art/mcp-server-google-search-consoleWrote 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/thein-art/mcp-server-google-search-console/google-search-console)<a href="https://agentmods.dev/mcp/thein-art/mcp-server-google-search-console/google-search-console"><img src="https://agentmods.dev/badge/mcp/thein-art/mcp-server-google-search-console/google-search-console/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/thein-art/mcp-server-google-search-console/google-search-console"><img src="https://agentmods.dev/badge/mcp/thein-art/mcp-server-google-search-console/google-search-console.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
google-search-console 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
{
"google-search-console": {
"command": "node",
"args": [
"dist/index.js"
],
"env": {
"GSC_OAUTH_CLIENT_FILE": "${GSC_OAUTH_CLIENT_FILE}"
}
}
}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 · 11 lines scan A 8697b80de420
google-search-console is an MCP server published in the GitHub repository thein-art/mcp-server-google-search-console (1 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
mcp-search-console
Google Search Console integration for Model Context Protocol (MCP). Runs locally from the mcp-search-console Python package. Needs 3 environment variables to run.
mcp-google-ads-server
MCP server "mcp-google-ads-server" as configured in johnoconnor0/google-ads-mcp. Runs locally from the mcp-google-ads-server Python package.
seo-audit-console
Technical SEO in Claude: GSC + crawl + DataForSEO - audit, market sizing, content recon. Runs locally from the @houtini/seo-audit-console npm package. Needs 9 environment variables to run.
gsc
MCP server for Google Search Console & Indexing API — search analytics, sitemaps, URL inspection. Runs locally from the @mikusnuz/gsc-mcp npm package. Needs 4 environment variables to run.
google-search-console-mcp
MCP server for Google Search Console: properties, sitemaps, search analytics and URL inspection. Runs locally from the @ni-c/google-search-console-mcp npm package. Needs 11 environment variables to run.
gsc-seo
MCP server "gsc-seo" as configured in ayhammouda/gsc-seo-mcp. Runs ${CLAUDE_PROJECT_DIR:-.}/dist/cli.js with node. Needs 3 environment variables to run.