mcp-gsc is an MCP server that connects Google Search Console, a service for inspecting website search performance, to AI assistants so users can ask questions about SEO data in natural language. SEO professionals use it to analyze their Google Search Console data, and the catalogue entries provide related skills, a plugin, an instruction, and MCP configuration.
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.
npx skills add AminForou/mcp-gsc --skill seo-weekly-reportgit clone --depth 1 https://github.com/AminForou/mcp-gscWrote 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/skills/aminforou/mcp-gsc/seo-weekly-report)<a href="https://agentmods.dev/skills/aminforou/mcp-gsc/seo-weekly-report"><img src="https://agentmods.dev/badge/skills/aminforou/mcp-gsc/seo-weekly-report/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/skills/aminforou/mcp-gsc/seo-weekly-report"><img src="https://agentmods.dev/badge/skills/aminforou/mcp-gsc/seo-weekly-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00031 | $0.00276 |
| Opus 5.5 | $0.00012 | $0.00110 |
| Sonnet 5.5 | $0.00006 | $0.00055 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
seo-weekly-report 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- seo-weekly-report — 100% identical, 0 lines differ
- seo-weekly-report — 100% identical, 0 lines differ
- seo-weekly-report — 100% identical, 0 lines differ
- seo-weekly-report — 86% identical, 4 lines differ
What it actually says
SEO Weekly Report
Generate a full weekly SEO performance report for a Google Search Console property.
Steps
- Call
list_propertiesto confirm the exactsite_urlto use. - Call
get_performance_overviewwithdays=28to retrieve totals (clicks, impressions, CTR, position) and the daily trend. - Call
compare_search_periodscomparing the last 28 days against the prior 28-day period, usingdimensions=queryandlimit=20. - Flag any queries where clicks dropped by more than 20% between periods.
- Call
get_search_analyticswithdimensions=queryandrow_limit=10to get the top 10 queries by clicks. - Summarize all results in a structured report with:
- Overall performance snapshot (totals + period-over-period change)
- Alerts: queries with >20% click decline
- Top 10 queries by clicks
- One-sentence recommendation for each alert
Output format
Present the report as a clear markdown document with headings, a summary table, and an action list.
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 · 27 lines · 31 tokens per session scan A 0ec707d5ba76
seo-weekly-report is a skill published in the GitHub repository AminForou/mcp-gsc (2,065 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 276 once invoked, about $0.0001 per session on Opus 5.5. 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-30.
Other skills, from other repositories
google-search-console-cli
Google Search Console data analysis and site management via google-search-console-cli. Use when the user wants to check search performance, analyze queries, inspect URL index status, manage sitemaps, or view site properties. Triggers: "Search Console", "search performance", "search queries", "GSC", "index status"…
brand-visibility
Analyzes 'Branded' vs 'Non-Branded' performance to see if you are a 'Reference' or a 'Destination'.
citation-opportunities
Identifies 'Information Gaps' where your site ranks #1 but has low CTR.
intent-efficiency
Aggregates metrics by 'User Intent' (Informational vs. Transactional).
intent-segmentation
Segments traffic into 'Searchers' (Keyword-based) vs. 'Prompters' (Natural Language).
search-appearance-audit
Contrast standard vs. featured results bypassing GSC API limitations.