io.github.pijusz/mcp-gsc
NPM · MCP-GSC · SCANNED SEP 20
Google Search Console MCP server — query performance, sitemaps, indexing & more
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 41 of 118 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 50 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1699 tokens (~80/item across 21 items; 21 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.pijusz/mcp-gsc server?
io.github.pijusz/mcp-gsc runs locally as an npm package, launched with npx -y mcp-gsc. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-gsc
claude mcp add pijusz-mcp-gsc -- npx -y mcp-gsc
{
"mcpServers": {
"pijusz-mcp-gsc": {
"command": "npx",
"args": [
"-y",
"mcp-gsc"
]
}
}
} {
"servers": {
"pijusz-mcp-gsc": {
"command": "npx",
"args": [
"-y",
"mcp-gsc"
]
}
}
} codex mcp add pijusz-mcp-gsc -- npx -y mcp-gsc
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pijusz-mcp-gsc": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-gsc"
],
"enabled": true
}
}
} openclaw mcp add pijusz-mcp-gsc --command npx --arg -y --arg mcp-gsc
mcp_servers:
pijusz-mcp-gsc:
command: "npx"
args: ["-y", "mcp-gsc"] {
"McpServers": {
"pijusz-mcp-gsc": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-gsc"
]
}
}
} assistant mcp add pijusz-mcp-gsc -t stdio -c npx -a -y mcp-gsc
{
"mcpServers": {
"pijusz-mcp-gsc": {
"command": "npx",
"args": [
"-y",
"mcp-gsc"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.77 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/mcp-gsc@0.1.7
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 118 packages
| Packages resolved | 118 |
|---|---|
| Deprecated | 1 |
| Stale | 40 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
batch_inspect_urls ~63
Inspect up to 10 URLs simultaneously. Returns categorized results (indexed, not indexed, issues). Each URL counts against the daily 2,000 and per-minute 600 URL Inspection limits.
| Name | Type | Req | Description |
|---|---|---|---|
| site_url | string | – | – |
| urls | array | yes | – |
No output schema declared.
No examples provided.
cannibalization ~72
Detect keyword cannibalization — multiple pages ranking for the same query. Uses query + page dimensions to find overlap.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | – |
| min_impressions | number | – | – |
| mode | string | – | – |
| site_url | string | – | – |
| start_date | string | yes | – |
No output schema declared.
No examples provided.
compare_periods ~89
Compare two date ranges with delta calculations (absolute change + percentage change) for each dimension value. Makes 2 API calls.
| Name | Type | Req | Description |
|---|---|---|---|
| dimensions | array | – | – |
| end_date_1 | string | yes | – |
| end_date_2 | string | yes | – |
| site_url | string | – | – |
| start_date_1 | string | yes | – |
| start_date_2 | string | yes | – |
No output schema declared.
No examples provided.
content_decay ~78
Detect pages/queries where impressions have dropped significantly compared to their historical peak within the 16-month API window.
| Name | Type | Req | Description |
|---|---|---|---|
| decay_threshold | number | – | – |
| dimension | string | – | – |
| end_date | string | yes | – |
| min_impressions | number | – | – |
| site_url | string | – | – |
| start_date | string | yes | – |
No output schema declared.
No examples provided.
ctr_anomalies ~69
Detect queries/pages with abnormally low or high CTR relative to their position. Uses expected CTR curves per position bucket and flags deviations.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | – |
| min_impressions | number | – | – |
| site_url | string | – | – |
| start_date | string | yes | – |
No output schema declared.
No examples provided.
device_country_breakdown ~50
Performance breakdown by device type and/or country.
| Name | Type | Req | Description |
|---|---|---|---|
| breakdown | string | yes | – |
| end_date | string | yes | – |
| site_url | string | – | – |
| start_date | string | yes | – |
No output schema declared.
No examples provided.
export_csv ~160
Export search analytics data to a CSV file. Auto-paginates internally (25K rows per API call) to write the full dataset, bypassing the tool response row cap. IMPORTANT: The GSC API has an absolute ceiling of 25,000 rows per query (sorted by impressions descending). For very large sites, this means the export will contain the top 25K query/page combinations, not the complete long tail. This is a Google API limitation, not a tool limitation.
| Name | Type | Req | Description |
|---|---|---|---|
| dimension_filters | array | – | – |
| dimensions | array | – | – |
| end_date | string | yes | – |
| output_path | string | – | – |
| site_url | string | – | – |
| start_date | string | yes | – |
| type | string | – | – |
No output schema declared.
No examples provided.
get_property_details ~33
Get verification info, ownership, and permissions for a specific Google Search Console property.
| Name | Type | Req | Description |
|---|---|---|---|
| site_url | string | yes | – |
No output schema declared.
No examples provided.
get_sitemap ~46
Get detailed info for a specific sitemap including content breakdown by type (web, image, video, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| site_url | string | – | – |
| sitemap_url | string | yes | – |
No output schema declared.
No examples provided.
indexing_coverage ~60
Batch-inspect user-provided URLs and categorize by indexing status: indexed, not indexed, canonical mismatch, robots blocked, fetch error, other. Respects URL Inspection rate limits.
| Name | Type | Req | Description |
|---|---|---|---|
| site_url | string | – | – |
| urls | array | yes | – |
No output schema declared.
No examples provided.
inspect_url ~60
Inspect a URL's indexing status, crawl info, rich results, mobile usability, and canonical URLs. Counts against the daily 2,000 and per-minute 600 URL Inspection limits.
| Name | Type | Req | Description |
|---|---|---|---|
| site_url | string | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
list_properties ~26
List all Google Search Console properties you have access to, with permission levels and verification status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sitemaps ~47
List all sitemaps for a property with status, type, indexed URL counts, errors/warnings.
| Name | Type | Req | Description |
|---|---|---|---|
| site_url | string | – | – |
| sitemap_index | string | – | – |
No output schema declared.
No examples provided.
opportunity_finder ~67
Find queries with improving impressions but low clicks, new emerging queries, and declining performers. Makes 2 API calls to compare periods.
| Name | Type | Req | Description |
|---|---|---|---|
| comparison_days | number | – | – |
| end_date | string | yes | – |
| site_url | string | – | – |
| start_date | string | yes | – |
No output schema declared.
No examples provided.
performance_overview ~67
Aggregate metrics (total clicks, impressions, avg CTR, avg position) plus a daily trend breakdown for a property. Single API call.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | – |
| site_url | string | – | – |
| start_date | string | yes | – |
| type | string | – | – |
No output schema declared.
No examples provided.
position_tracking ~79
Track position changes for specific queries or pages over time. Uses date dimension with query/page filters. Returns daily or weekly averages.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | – |
| granularity | string | – | – |
| pages | array | – | – |
| queries | array | – | – |
| site_url | string | – | – |
| start_date | string | yes | – |
No output schema declared.
No examples provided.
quick_wins ~100
Find high-impression, low-CTR queries in striking distance (position 4-20). These are opportunities to improve rankings and CTR with small content or SEO tweaks.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | – |
| max_ctr | number | – | – |
| max_position | number | – | – |
| min_impressions | number | – | – |
| min_position | number | – | – |
| site_url | string | – | – |
| start_date | string | yes | – |
No output schema declared.
No examples provided.
search_analytics ~335
Query Google Search Console search performance data (clicks, impressions, CTR, position) with filtering and grouping. DIMENSIONS: query, page, country, device, date, searchAppearance, hour - "hour" requires data_state="hourly_all" and is limited to the last 10 days - "searchAppearance" CANNOT be combined with "query" or "page" (API restriction) TYPE: web (default), image, video, news, discover, googleNews - "discover" = Google Discover feed. "googleNews" = Google News tab (distinct from "news") DATA STATE: Controls data freshness. - "all" (default) includes recent incomplete data matching the GSC dashboard - "final" returns only confirmed data with a 2-3 day lag, useful for stable reporting - "hourly_all" enables hourly granularity but data may be incomplete for the current day BRAND FILTER: Set to "brand_only" or "non_brand_only" to auto-filter queries by your domain name. Country codes use ISO 3166-1 alpha-3 format (e.g., 'usa', 'gbr', 'deu') — NOT alpha-2.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_filter | string | – | – |
| data_state | string | – | – |
| dimension_filters | array | – | – |
| dimensions | array | – | – |
| end_date | string | yes | – |
| row_limit | number | – | – |
| site_url | string | – | – |
| start_date | string | yes | – |
| start_row | number | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
sitemap_health ~42
Analyze all sitemaps: error/warning patterns, submission freshness (days since last submitted), indexed vs submitted ratio per sitemap.
| Name | Type | Req | Description |
|---|---|---|---|
| site_url | string | – | – |
No output schema declared.
No examples provided.
top_movers ~88
Biggest gains and drops in clicks/impressions/position between two periods. Period A = start_date to end_date. Period B = the comparison_days before start_date.
| Name | Type | Req | Description |
|---|---|---|---|
| comparison_days | number | – | – |
| end_date | string | yes | – |
| limit | number | – | – |
| metric | string | – | – |
| site_url | string | – | – |
| start_date | string | yes | – |
No output schema declared.
No examples provided.
weekly_seo_report ~68
All-in-one SEO report: runs performance overview + quick wins + top movers + indexing issues summary. Returns a combined markdown report.
| Name | Type | Req | Description |
|---|---|---|---|
| comparison_days | number | – | – |
| end_date | string | yes | – |
| site_url | string | – | – |
| start_date | string | yes | – |
No output schema declared.
No examples provided.
What is the io.github.pijusz/mcp-gsc server?
io.github.pijusz/mcp-gsc is listed in the public MCP registry as io.github.pijusz/mcp-gsc. Google Search Console MCP server, query performance, sitemaps, indexing & more. This page covers its npm package (mcp-gsc).
Is the io.github.pijusz/mcp-gsc server safe to use?
io.github.pijusz/mcp-gsc scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.pijusz/mcp-gsc server expose?
io.github.pijusz/mcp-gsc exposes 21 tools: list_properties, get_property_details, search_analytics, list_sitemaps, get_sitemap, and 16 more. Their descriptions and schemas cost roughly 1,699 tokens of context every time the server is loaded.
Is the io.github.pijusz/mcp-gsc server still maintained?
io.github.pijusz/mcp-gsc is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.pijusz/mcp-gsc server under?
io.github.pijusz/mcp-gsc declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.