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/ayhammouda/gsc-seo-mcpInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote 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/ayhammouda/gsc-seo-mcp/gsc-seo)<a href="https://agentmods.dev/mcp/ayhammouda/gsc-seo-mcp/gsc-seo"><img src="https://agentmods.dev/badge/mcp/ayhammouda/gsc-seo-mcp/gsc-seo/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/ayhammouda/gsc-seo-mcp/gsc-seo"><img src="https://agentmods.dev/badge/mcp/ayhammouda/gsc-seo-mcp/gsc-seo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
gsc-seo 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 2mo 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
{
"gsc-seo": {
"type": "stdio",
"command": "node",
"args": [
"${CLAUDE_PROJECT_DIR:-.}/dist/cli.js",
"stdio"
],
"env": {
"GSC_SEO_MCP_ALLOWED_PROPERTIES": "${GSC_SEO_MCP_ALLOWED_PROPERTIES}",
"GSC_SEO_MCP_AUTH_MODE": "${GSC_SEO_MCP_AUTH_MODE:-stored}",
"GSC_SEO_MCP_MODE": "read_only"
}
}
}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.
- 2mo ago First seen · 15 lines scan A c3f396e4d326
gsc-seo is an MCP server published in the GitHub repository ayhammouda/gsc-seo-mcp (0 stars, last pushed 2d 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-google-search-console
MCP server for the Google Search Console API: search analytics, sitemaps, URL inspection, sites. Runs locally from the mcp-google-search-console npm package. Needs 8 environment variables to run.
google-search-console-mcp
The GSC 'Intel Engine' for the evolving search landscape. Authoritative visibility governance and AI overview citation analysis via Model Context Protocol. Runs locally from the google-search-console-mcp Python package. Needs 2 environment variables to run.
search-console-mcp
Google Search Console for any MCP client - 30-second login, no Google Cloud project. Read-only. Runs locally from the search-console-mcp-server npm package.
mcp-google-business
MCP server for Google Business Profile: locations, reviews, local posts and performance metrics. Runs locally from the mcp-google-business npm package. Needs 11 environment variables to run.
google-search-console
MCP server for Google Search Console: query performance data, inspect URLs, check indexing, and generate HTML SEO audit reports from Claude, Cursor, Zed, and any Model Context Protocol client. Runs locally from the mcp-google-search-console Python package. Needs 4 environment variables to run.
google-search-console-mcp
MCP server for Google Search Console: query performance data, inspect URLs, check indexing, and generate HTML SEO audit reports from Claude, Cursor, Zed, and any Model Context Protocol client. Runs locally from the mcp-google-search-console Python package. Needs 6 environment variables to run.