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/powehi-eu/google-suite-seo-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/powehi-eu/google-suite-seo-mcp/google_search_console)<a href="https://agentmods.dev/mcp/powehi-eu/google-suite-seo-mcp/google_search_console"><img src="https://agentmods.dev/badge/mcp/powehi-eu/google-suite-seo-mcp/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/powehi-eu/google-suite-seo-mcp/google_search_console"><img src="https://agentmods.dev/badge/mcp/powehi-eu/google-suite-seo-mcp/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 11d 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": "gsc-mcp",
"startup_timeout_sec": 30,
"env": {
"GOOGLE_SERVICE_ACCOUNT_FILE": "${GOOGLE_SERVICE_ACCOUNT_FILE}"
}
}
}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.
- 11d ago First seen · 9 lines scan A 4a69e26a7f66
google_search_console is an MCP server published in the GitHub repository powehi-eu/google-suite-seo-mcp (5 stars, last pushed 1mo 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
adloop
MCP server "adloop" as configured in kLOsk/adloop. Runs locally from the . Python package.
mcp-google-analytics
GA4 MCP that reads AND writes: reports, funnels, audits, and server-side events. 26 tools. Runs locally from the mcp-google-analytics npm package. Needs 4 environment variables to run.
google-analytics
GA4 MCP server that reads AND writes: run reports and funnels (Data API), audit your setup (custom dimensions, key events, compatibility checks), and send events server-side (Measurement Protocol v2). Runs locally from the mcp-google-analytics npm package. Needs 2 environment variables to run.
google-analytics-mcp
Model Context Protocol for Google Analytics 4 (Data API) allowing autonomous agents to query dimensions and metrics. Gives agents analysis-ready GA4 access with schema discovery, server-side aggregation, and smart defaults. Runs locally from the google-analytics-mcp Python package. Needs 2 environment variables to run.
google-analytics
Google Analytics 4: 27 read-only tools across the Data API and the Admin API. Runs locally from the @getmcpads/google-analytics-mcp-server npm package. Needs 4 environment variables to run.
google-measurement-mcp
MCP server for the Google measurement stack — GA4, Search Console, and Tag Manager in one server. Read tools always on, write tools behind an explicit flag, destructive operations omitted by design. Runs locally from the google-measurement-mcp npm package.