com.mcparmory/google-search
PYPI · MCPARMORY-GOOGLE-SEARCH · 2 COMPONENTS
Scrape Google search results with SERP data, ads, and knowledge panels
Available components
Last scanned (21 hours ago)
Scores higher than 61% of PyPI servers
Category Search and Retrieval
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 2 of 40 dependencies flagged as unhealthy. 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 176 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 678 tokens (~678/item across 1 items; 1 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "search_google" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 1 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
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.
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 30 Oct 26 0
- Stability: pass → 0.97 functional
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 24 Oct 26 0
- Stability: 0.97 → pass security
- 23 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.97 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 4 Nov 2026 · Analysed pypi/mcparmory-google-search@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 40 packages
| Packages resolved | 40 |
|---|---|
| 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 →
search_google Search Google ~678
Execute a Google search with customizable filters, location targeting, and result pagination. Supports advanced search operators, Knowledge Graph entity lookups, and device-specific results.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Authentication key for API requests. Provide as a query parameter or in the Authorization header using Bearer token format. |
| cr | string | – | Restricts results to documents originating from a specific country, determined by the document's top-level domain or server IP geolocation. |
| device | string | – | The device type for search results. Choose from desktop (default), mobile, or tablet to simulate searches from different device types. |
| engine | string | yes | The search engine identifier. Must be set to 'google' to use Google's search engine. |
| filter | string | – | Controls duplicate content and host crowding filters. Set to '1' (default) to enable filters or '0' to disable them. |
| gl | string | – | Two-letter country code (e.g., 'us', 'gb', 'de') to restrict results to a specific country. Defaults to 'us'. See Google Shopping countries list for all supported codes. |
| hl | string | – | Two-letter language code (e.g., 'en', 'fr', 'ja') to set the search interface language. Defaults to 'en'. Supports all Google interface languages. |
| kgmid | string | – | A Knowledge Graph identifier representing a specific entity. Format: Location identifiers start with /m/ followed by 2-7 characters; general entity identifiers start with /g/ followed by longer alpha… |
| lr | string | – | Restricts results to documents in specific languages using the format lang_XX or multiple languages with pipe separation (e.g., lang_en|lang_de). Google identifies language via TLD, meta tags, or doc… |
| optimization_strategy | string | – | Optimization strategy for the request. Use 'performance' (default) for faster responses or 'ads' to optimize for higher ad collection success rates at the cost of longer processing times. |
| page | integer | – | Results page number to retrieve, starting from 1 (default). Use for pagination through search results. |
| q | string | – | The search query string. Supports Google's advanced search operators (inurl:, site:, intitle:, etc.). Either this or kgmid must be provided. |
| safe | string | – | SafeSearch filtering level. Use 'active' for strict filtering, 'blur' (default) to blur explicit images, or 'off' to disable SafeSearch entirely. |
| time_period_max | string | – | End date for filtering results by publication date. Format: MM/DD/YYYY. Use with time_period_min to define a date range. |
| time_period_min | string | – | Start date for filtering results by publication date. Format: MM/DD/YYYY. Use with time_period_max to define a date range. |
| uule | string | – | Google-encoded location parameter for geographically-targeted results. Cannot be used together with the location parameter. SearchApi generates this automatically when using location. |
| verbatim | string | – | Forces exact keyword matching by disabling spelling corrections, synonyms, and query variations. Set to 'true' to enable. Stricter than nfpr parameter. |
No output schema declared.
No examples provided.
How do I install the com.mcparmory/google-search MCP server?
com.mcparmory/google-search runs locally as a PyPI package, launched with uvx mcparmory-google-search. 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
claude mcp add com-mcparmory-google-search -- uvx mcparmory-google-search
What is the com.mcparmory/google-search MCP server?
com.mcparmory/google-search is an MCP server listed in the public MCP registry as com.mcparmory/google-search. Scrape Google search results with SERP data, ads, and knowledge panels. This page covers its PyPI package (mcparmory-google-search).
Is the com.mcparmory/google-search MCP server safe to use?
com.mcparmory/google-search scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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 com.mcparmory/google-search MCP server expose?
com.mcparmory/google-search exposes 1 tool: search_google. Their descriptions and schemas cost roughly 678 tokens of context every time the server is loaded.
Is the com.mcparmory/google-search MCP server still maintained?
com.mcparmory/google-search is still listed as active in the MCP registry. We last reached this channel on 4 November 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 com.mcparmory/google-search MCP server under?
com.mcparmory/google-search declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.