io.github.sarahpark/google-search-console
NPM · @SARAHPARK/GOOGLE-SEARCH-CONSOLE-MCP · SCANNED SEP 20
Google Search Console MCP server — search analytics, URL inspection, and sitemaps
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 Security89
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects uuid 9.0.1, reached via googleapis > googleapis-common > uuid. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 41 of 121 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 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 356 tokens (~89/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the io.github.sarahpark/google-search-console MCP server?
io.github.sarahpark/google-search-console runs locally as an npm package, launched with npx -y @sarahpark/google-search-console-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @sarahpark/google-search-console-mcp
claude mcp add sarahpark-google-search-console -- npx -y @sarahpark/google-search-console-mcp
{
"mcpServers": {
"sarahpark-google-search-console": {
"command": "npx",
"args": [
"-y",
"@sarahpark/google-search-console-mcp"
]
}
}
} {
"servers": {
"sarahpark-google-search-console": {
"command": "npx",
"args": [
"-y",
"@sarahpark/google-search-console-mcp"
]
}
}
} codex mcp add sarahpark-google-search-console -- npx -y @sarahpark/google-search-console-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sarahpark-google-search-console": {
"type": "local",
"command": [
"npx",
"-y",
"@sarahpark/google-search-console-mcp"
],
"enabled": true
}
}
} openclaw mcp add sarahpark-google-search-console --command npx --arg -y --arg @sarahpark/google-search-console-mcp
mcp_servers:
sarahpark-google-search-console:
command: "npx"
args: ["-y", "@sarahpark/google-search-console-mcp"] {
"McpServers": {
"sarahpark-google-search-console": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@sarahpark/google-search-console-mcp"
]
}
}
} assistant mcp add sarahpark-google-search-console -t stdio -c npx -a -y @sarahpark/google-search-console-mcp
{
"mcpServers": {
"sarahpark-google-search-console": {
"command": "npx",
"args": [
"-y",
"@sarahpark/google-search-console-mcp"
]
}
}
} 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.
- 20 Sept 26 +35
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- License: fail → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- Licence: MIT functional
- Package version: 1.0.1 → 1.1.0 functional
- 19 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 18 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 12 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 11 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 5 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 3 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 1 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
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/@sarahpark/google-search-console-mcp@1.1.0
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 121 packages
| Packages resolved | 121 |
|---|---|
| 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 →
inspect_url ~61
Inspect a URL to check its indexing status, crawl info, and any issues Google found.
| Name | Type | Req | Description |
|---|---|---|---|
| inspectionUrl | string | yes | The full URL to inspect (must belong to the site) |
| siteUrl | string | yes | Site URL as it appears in Search Console |
No output schema declared.
No examples provided.
list_sitemaps ~40
List all sitemaps submitted for a site in Google Search Console.
| Name | Type | Req | Description |
|---|---|---|---|
| siteUrl | string | yes | Site URL as it appears in Search Console |
No output schema declared.
No examples provided.
list_sites ~23
List all sites (properties) you have access to in Google Search Console.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_analytics ~232
Query search analytics data from Google Search Console. Returns clicks, impressions, CTR, and position for your site.
| Name | Type | Req | Description |
|---|---|---|---|
| countryFilter | string | – | Filter by country (ISO 3166-1 alpha-3, e.g. USA, GBR) |
| deviceFilter | string | – | Filter by device type |
| dimensions | string | – | Comma-separated dimensions: query, page, country, device, searchAppearance, date |
| endDate | string | yes | End date in YYYY-MM-DD format |
| pageFilter | string | – | Filter by page URL. Prefix with regex: for regex matching. |
| queryFilter | string | – | Filter by search query. Prefix with regex: for regex matching. |
| rowLimit | number | – | Max rows to return (default 100, max 25000) |
| searchType | string | – | Type of search results to query |
| siteUrl | string | yes | Site URL exactly as it appears in Search Console (e.g. https://example.com/ or sc-domain:example.com) |
| startDate | string | yes | Start date in YYYY-MM-DD format |
No output schema declared.
No examples provided.
What is the io.github.sarahpark/google-search-console MCP server?
io.github.sarahpark/google-search-console is an MCP server listed in the public MCP registry as io.github.sarahpark/google-search-console. Google Search Console MCP server, search analytics, URL inspection, and sitemaps. This page covers its npm package (@sarahpark/google-search-console-mcp).
Is the io.github.sarahpark/google-search-console MCP server safe to use?
io.github.sarahpark/google-search-console scores 68 out of 100 on VerifyMCP. We recorded 1 known advisory against 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.sarahpark/google-search-console MCP server expose?
io.github.sarahpark/google-search-console exposes 4 tools: list_sites, search_analytics, inspect_url, list_sitemaps. Their descriptions and schemas cost roughly 356 tokens of context every time the server is loaded.
Is the io.github.sarahpark/google-search-console MCP server still maintained?
io.github.sarahpark/google-search-console 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.sarahpark/google-search-console MCP server under?
io.github.sarahpark/google-search-console declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.