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/antohins/seo-tools-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/antohins/seo-tools-mcp/gsc)<a href="https://agentmods.dev/mcp/antohins/seo-tools-mcp/gsc"><img src="https://agentmods.dev/badge/mcp/antohins/seo-tools-mcp/gsc/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/antohins/seo-tools-mcp/gsc"><img src="https://agentmods.dev/badge/mcp/antohins/seo-tools-mcp/gsc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
gsc 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 9d 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": {
"command": "npx",
"args": [
"-y",
"seo-tools-mcp-gsc"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 8. 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.
- 9d ago First seen · 9 lines scan A d066e3f59c7d
gsc is an MCP server published in the GitHub repository antohins/seo-tools-mcp (3 stars, last pushed 4d 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
xmlriver-mcp
MCP server for XMLRiver — Google/Yandex SERP parsing and Wordstat frequency data via XML API. Runs locally from the xmlriver-mcp Python package.
yandex-webmaster-mcp
Query Yandex Webmaster indexing, queries, diagnostics and backlinks, and recrawl, via an AI agent. Runs locally from the @boxlab/yandex-webmaster-mcp npm package. Needs 2 environment variables to run.
yandex-webmaster
Model Context Protocol (MCP) server for Yandex Webmaster — query indexing, search queries, diagnostics and backlinks, and submit URLs for recrawl through an AI agent. Runs locally from the @boxlab/yandex-webmaster-mcp npm package.
tracetify-mcp
Find competitors, trace how they grew, watch what they ship — plus your Search Console. Runs locally from the tracetify-mcp npm package. Needs 1 environment variable to run.
mcp
Track keyword rankings, research SEO opportunities, and manage bisibility projects with AI agents. Runs locally from the @bisibility/mcp npm package. Needs 5 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.