Serper.live
NPM · @SERPER-LIVE/MCP · 2 COMPONENTS
Live Google search results, domain positions and open markets via the Serper.live SERP API.
Available components
Last scanned (4 hours ago)
Scores higher than 92% of npm servers
Category Marketing and SEO
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 Security100
- 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
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to serper-live/serper-live-mcp). View diagnostics → Pass
- 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 Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 711 tokens (~237/item across 3 items; 3 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 Management57
- Stability observed for 17 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
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.50 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 2.1.2 → 2.2.0 functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +16
- Malware scan: unverified → 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 5 Nov 2026 · Analysed npm/@serper-live/mcp@2.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | serper-live/serper-live-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/serper-live/serper-live-mcp/.github/workflows/publish.yml@refs/tags/v2.2.0 |
| Rekor log index | 3688374342 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:0016d7ee26362802193904d46953ae879e848cdd824869898236ec27eb52c07dbb569e47d3cefa28879746e78835da992daea69504d9346d09ccb02ce |
Background: How many MCP packages publish verified provenance →
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| 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 →
domain_position Domain position in Google ~311
Find where a domain ranks in Google's organic results for a keyword, in a country and on a device, right now. Prefer it over google_search when only one site matters: it returns that site's best position and every other position, or a note that the site is outside the checked depth. A subdomain counts as the domain: example.com also matches blog.example.com. Billed like google_search, per page of 10 results of depth that received results (https://serper.live/pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Two-letter code of the market to search in, e.g. "US", "GB", "DE", "FR", "TR": Google sees a visitor from this country. Call list_countries for the markets that are open right now. |
| depth | integer | – | How many organic results to check, 1–100. Default: 10. Use 30 or more to see positions beyond the first page. |
| device | string | – | Browser persona Google sees. Desktop and mobile rankings often differ. Default: desktop. |
| domain | string | yes | Domain to look for, e.g. "example.com". Scheme, path and a leading www are ignored. |
| language | string | – | Google interface language (hl), e.g. "en", "de", "fr", "uk". Defaults to the language of the country; the market itself is set by country. |
| query | string | yes | Search keyword, exactly as a person would type it into Google. |
No output schema declared.
No examples provided.
google_search Live Google search ~332
Run a live Google search for a country, language and device and return the organic results in Google's order: position, title, URL, domain and snippet, plus the questions of Google's "People also ask" block and its related searches. Ads, sitelinks, video and image blocks are left out, so position is the organic rank. Every call is a real, uncached search that usually takes 2–3 seconds and is billed to the Serper.live balance per page of up to 10 results that received results, after the free searches of the account (https://serper.live/pricing); a search that finds nothing costs nothing. Use it to see the whole result list; to check where one site ranks, use domain_position instead.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Two-letter code of the market to search in, e.g. "US", "GB", "DE", "FR", "TR": Google sees a visitor from this country. Call list_countries for the markets that are open right now. |
| device | string | – | Browser persona Google sees. Desktop and mobile rankings often differ. Default: desktop. |
| language | string | – | Google interface language (hl), e.g. "en", "de", "fr", "uk". Defaults to the language of the country; the market itself is set by country. |
| limit | integer | – | How many organic results to return, 1–100. Default: 10. Each page of 10 that receives results is billed. |
| query | string | yes | Search keyword, exactly as a person would type it into Google. |
No output schema declared.
No examples provided.
list_countries Open Serper.live markets ~68
List the countries Serper.live can search right now, with the default Google interface language of each. Call it when unsure whether a market is open, then pass a returned code as country to google_search or domain_position. Desktop and mobile are available in every market. Free, no token needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Serper.live MCP server?
Serper.live runs locally as an npm package, launched with npx -y @serper-live/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 · @serper-live/mcp
claude mcp add serper-live-serper-live-mcp -- npx -y @serper-live/mcp
What is the Serper.live MCP server?
Serper.live is an MCP server listed in the public MCP registry as io.github.serper-live/serper-live-mcp. Live Google search results, domain positions and open markets via the Serper.live SERP API. This page covers its npm package (@serper-live/mcp).
Is the Serper.live MCP server safe to use?
Serper.live scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Serper.live MCP server expose?
Serper.live exposes 3 tools: google_search, domain_position, list_countries. Their descriptions and schemas cost roughly 711 tokens of context every time the server is loaded.
Is the Serper.live MCP server still maintained?
Serper.live is still listed as active in the MCP registry. We last reached this channel on 5 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 Serper.live MCP server under?
Serper.live declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.