com.mcparmory/google-search-console
PYPI · MCPARMORY-GOOGLE-SEARCH-CONSOLE · 2 COMPONENTS · SCANNED SEP 20
Query search analytics, manage sitemaps, and inspect site URLs and status
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 Security37
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- 2 of 46 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 130 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1458 tokens (~132/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 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
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the com.mcparmory/google-search-console MCP server?
com.mcparmory/google-search-console runs locally as a PyPI package, launched with uvx mcparmory-google-search-console. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcparmory-google-search-console
claude mcp add com-mcparmory-google-search-console -- uvx mcparmory-google-search-console
{
"mcpServers": {
"com-mcparmory-google-search-console": {
"command": "uvx",
"args": [
"mcparmory-google-search-console"
]
}
}
} {
"servers": {
"com-mcparmory-google-search-console": {
"command": "uvx",
"args": [
"mcparmory-google-search-console"
]
}
}
} codex mcp add com-mcparmory-google-search-console -- uvx mcparmory-google-search-console
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-google-search-console": {
"type": "local",
"command": [
"uvx",
"mcparmory-google-search-console"
],
"enabled": true
}
}
} openclaw mcp add com-mcparmory-google-search-console --command uvx --arg mcparmory-google-search-console
mcp_servers:
com-mcparmory-google-search-console:
command: "uvx"
args: ["mcparmory-google-search-console"] {
"McpServers": {
"com-mcparmory-google-search-console": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcparmory-google-search-console"
]
}
}
} assistant mcp add com-mcparmory-google-search-console -t stdio -c uvx -a mcparmory-google-search-console
{
"mcpServers": {
"com-mcparmory-google-search-console": {
"command": "uvx",
"args": [
"mcparmory-google-search-console"
]
}
}
} 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −2
- 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 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 −17
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.80 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 pypi/mcparmory-google-search-console@1.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Dependencies 46 packages
| Packages resolved | 46 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| 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 →
add_site Add Site ~58
Adds a website to your Search Console account, enabling you to monitor and manage its search performance.
| Name | Type | Req | Description |
|---|---|---|---|
| siteUrl | string | yes | The complete URL of the website to add to Search Console (e.g., domain, subdomain, or URL prefix). |
No output schema declared.
No examples provided.
delete_site Delete Site ~85
Removes a website property from your Search Console account, preventing further monitoring and analysis of that site.
| Name | Type | Req | Description |
|---|---|---|---|
| siteUrl | string | yes | The site URL or domain property identifier as it appears in Search Console. Use the full URL format (e.g., http://www.example.com/) for URL-prefix properties or the domain format (e.g., sc-domain:exa… |
No output schema declared.
No examples provided.
delete_sitemap Delete Sitemap ~123
Removes a sitemap from the Sitemaps report. Note that this action does not prevent Google from crawling the sitemap or previously indexed URLs from that sitemap.
| Name | Type | Req | Description |
|---|---|---|---|
| feedpath | string | yes | The complete URL of the sitemap file to delete (e.g., http://www.example.com/sitemap.xml). This must be the exact sitemap URL you want to remove from the report. |
| siteUrl | string | yes | The site's URL including the protocol (e.g., http://www.example.com/ or https://www.example.com/). This identifies which site the sitemap belongs to. |
No output schema declared.
No examples provided.
get_site Get Site ~86
Retrieves detailed information about a specific site property registered in Google Search Console, including its configuration and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| siteUrl | string | yes | The site URL or domain property identifier as it appears in Search Console. Use the full URL format (e.g., http://www.example.com/) for URL-prefix properties or the domain format (e.g., sc-domain:exa… |
No output schema declared.
No examples provided.
get_sitemap Get Sitemap ~96
Retrieves detailed information about a specific sitemap for a website, including its status and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| feedpath | string | yes | The complete URL path to the sitemap file. Must be a valid, fully-qualified URL such as http://www.example.com/sitemap.xml. |
| siteUrl | string | yes | The website's URL including the protocol (http or https). Must be a valid, fully-qualified URL such as http://www.example.com/. |
No output schema declared.
No examples provided.
inspect_url_index_status Inspect URL Index Status ~160
Inspect the indexing status of a specific URL within a Search Console property. Returns detailed information about whether the URL is indexed and any associated issues.
| Name | Type | Req | Description |
|---|---|---|---|
| inspectionUrl | string | – | The URL to inspect for indexing status. Must be a valid URL that belongs to the property specified in siteUrl. |
| languageCode | string | – | The language for translated issue messages in IETF BCP-47 format (e.g., en-US, de-CH). Defaults to English (US) if not specified. |
| siteUrl | string | – | The Search Console property URL in either URL-prefix format (e.g., http://www.example.com/) or domain property format (e.g., sc-domain:example.com). The inspectionUrl must belong to this property. |
No output schema declared.
No examples provided.
list_sitemaps List Sitemaps ~135
Retrieves all sitemaps submitted for a website or included in a sitemap index file. Use this to view the complete list of sitemaps Google has discovered for your site.
| Name | Type | Req | Description |
|---|---|---|---|
| siteUrl | string | yes | The website's URL including the protocol (http:// or https://). For example: http://www.example.com/ or https://example.com/. This identifies which site's sitemaps to retrieve. |
| sitemapIndex | string | – | Optional URL pointing to a sitemap index file that aggregates multiple sitemaps. When provided, returns only the sitemaps referenced within that index file rather than all submitted sitemaps. |
No output schema declared.
No examples provided.
list_sites List Sites ~33
Retrieves a list of all Search Console sites that the authenticated user has access to. This includes both verified and unverified properties.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
query_search_analytics Query Search Analytics ~476
Query Google Search Console analytics data with custom filters and grouping. Returns aggregated performance metrics (clicks, impressions, CTR, position) for your specified dimensions and date range.
| Name | Type | Req | Description |
|---|---|---|---|
| aggregationType | string | – | How to aggregate the returned data: AUTO (default, required if filtering/grouping by page), BY_PROPERTY (aggregate all data for the same property), BY_PAGE (aggregate by canonical URI), or BY_NEWS_SH… |
| dataState | string | – | Which data state to retrieve: FINAL (complete data only), ALL (complete and partial data), or HOURLY_ALL (includes hourly data). Defaults to FINAL if not specified. |
| dimensionFilterGroups | array | – | Zero or more filter groups to narrow results by dimension values (e.g., query contains 'buy', country equals 'USA'). Filters are applied without requiring those dimensions to be in the grouping. |
| dimensions | array | – | Zero or more dimensions to group results by (e.g., query, page, country, device). Results are grouped in the order specified. At least one dimension is typically needed for meaningful results. |
| endDate | string | – | End date for the query range in YYYY-MM-DD format (PST/UTC-8). Must be greater than or equal to the start date and is included in the range. |
| rowLimit | string | – | Maximum number of rows to return in the response. Must be between 1 and 25,000 inclusive. Defaults to 1,000 if not specified. |
| searchType | string | – | Filter results to a specific search type: WEB (default), IMAGE, VIDEO, NEWS, DISCOVER, or GOOGLE_NEWS. |
| siteUrl | string | yes | The site URL to query, including protocol (e.g., http://www.example.com/ or https://example.com). Must match a verified property in Search Console. |
| startDate | string | – | Start date for the query range in YYYY-MM-DD format (PST/UTC-8). Must be less than or equal to the end date and is included in the range. |
| startRow | string | – | Zero-based index of the first row to return, used for pagination. Must be a non-negative integer. Defaults to 0 if not specified. |
No output schema declared.
No examples provided.
submit_sitemap Submit Sitemap ~119
Submits a sitemap to Google Search Console for a specified site. This enables Google to discover and index the URLs listed in your sitemap.
| Name | Type | Req | Description |
|---|---|---|---|
| feedpath | string | yes | The complete URL path to the sitemap file. Must be a valid, fully-qualified URL pointing to the actual sitemap resource (e.g., http://www.example.com/sitemap.xml). |
| siteUrl | string | yes | The site's URL including the protocol (http or https). Must be a valid, fully-qualified URL with trailing slash (e.g., http://www.example.com/). |
No output schema declared.
No examples provided.
test_mobile_friendly Test Mobile Friendly ~87
Tests whether a given URL is mobile-friendly by analyzing its mobile rendering and usability. Optionally returns a screenshot of the mobile view.
| Name | Type | Req | Description |
|---|---|---|---|
| requestScreenshot | boolean | – | Whether to include a screenshot of the URL as rendered on a mobile device in the test results. |
| url | string | – | The complete URL to test for mobile-friendliness, including the protocol (http or https). |
No output schema declared.
No examples provided.
What is the com.mcparmory/google-search-console MCP server?
com.mcparmory/google-search-console is an MCP server listed in the public MCP registry as com.mcparmory/google-search-console. Query search analytics, manage sitemaps, and inspect site URLs and status. This page covers its PyPI package (mcparmory-google-search-console).
Is the com.mcparmory/google-search-console MCP server safe to use?
com.mcparmory/google-search-console scores 62 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 com.mcparmory/google-search-console MCP server expose?
com.mcparmory/google-search-console exposes 11 tools: query_search_analytics, get_sitemap, submit_sitemap, delete_sitemap, list_sitemaps, and 6 more. Their descriptions and schemas cost roughly 1,458 tokens of context every time the server is loaded.
Is the com.mcparmory/google-search-console MCP server still maintained?
com.mcparmory/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.