HasData Google Search (SERP)
REMOTE · MCP.HASDATA.COM · 3 COMPONENTS
Google SERP as JSON: organic, AI Overview, People Also Ask, AI Mode, news, shopping. No Cloud setup.
Last scanned (21 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 5348 tokens (~267/item across 20 items; 10 tools + 10 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 Management37
- Stability observed for 11 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 23. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +44
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.17 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 39
First indexed and scored.
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 16 Oct 2026 · Probed https://mcp.hasdata.com/mcp?apis=google_serp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.hasdata.com | CN=YR1,O=Let's Encrypt,C=US | 20 Aug 2026 | 18 Nov 2026 | RSA 2048 | SHA256-RSA | 5cef740443d03259c4ef72de38826f9d2a3 |
| SANs: mcp.hasdata.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.hasdata.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| hasdata.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="Authorization is required: connect with OAuth or send an x-api-key header", scope="mcp:tools", resource_metadata="https://mcp.hasdata.com/.well-known/oauth-protected-resource/mcp"
Bearer error="invalid_token", error_description="Authorization is required: connect with OAuth or send an x-api-key header", scope="mcp:tools", resource_metadata="https://mcp.hasdata.com/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Protected resource metadata
| Document | https://mcp.hasdata.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.hasdata.com/mcp |
| Authorisation server | https://mcp.hasdata.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.hasdata.com/mcp?apis=google_serp | Verified | 200 | |
| http (plaintext) | http://mcp.hasdata.com/mcp?apis=google_serp | HTTPS enforced | 308 | https://mcp.hasdata.com/mcp?apis=google_serp |
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 →
hasdata_google_serp_ai_mode_getAiModeResponse google_serp_ai_mode: GET / ~335
Get AI Mode SERP Results Captures Gemini-powered AI Mode answers from Google Search. Returns the conversational response text, cited source links, subtopic breakdowns, and, when continuable is set, a subsequentRequestToken for multi-turn continuation. Use for next-gen search interfaces, AI-answer monitoring, citation tracking, content research agents, building question-answering pipelines grounded in live Google results, and person/company data enrichment — e.g. asking `Who is the CEO of HasData?`, `What is Roman Milyushkevich's LinkedIn?`, `HasData founder email`, `HasData Instagram handle` to get a synthesized answer plus source URLs in one call, ideal for lead enrichment, sales research, people search, and filling in contact/attribute gaps for CRM records.
| Name | Type | Req | Description |
|---|---|---|---|
| continuable | boolean | – | Whether to continue an existing AI Mode conversation. |
| gl | string | – | The two-letter country code for the country you want to limit the search to. Provide one exact documented value (245 allowed), e.g. `ac`, `af`. |
| hl | string | – | The two-letter language code for the language you want to use for the search. Provide one exact documented value (159 allowed), e.g. `af`, `ak`. |
| location | string | – | Google canonical location for the search. |
| q | string | yes | Specify the search term for which you want to scrape the SERP. |
| subsequentRequestToken | string | – | Token used to continue a previous AI Mode request. |
| uule | string | – | The encoded location parameter. |
No output schema declared.
No examples provided.
hasdata_google_serp_ai_overview_getAiOverviewResponse google_serp_ai_overview: GET / ~129
Get AI Overview Results Fetches the lazy-loaded Google AI Overview block via a pageToken returned by the Google SERP API (token valid for 1 minute). Returns the AI-generated answer text, referenced source URLs, and expanded subtopic sections. Use as a follow-up call to Google SERP for tracking AI citations in SEO, fact-checking answers against sources, and LLM retrieval pipelines grounded in live Google results.
| Name | Type | Req | Description |
|---|---|---|---|
| pageToken | string | yes | Token from `aiOverview` block in Google SERP API. Valid for 1 minute. |
No output schema declared.
No examples provided.
hasdata_google_serp_events_getEventInformation google_serp_events: GET / ~195
Get Google Event Details Looks up a single Google event by the `pageToken` returned in a `google/serp` response's `eventsResults` array (or the ready-to-call `hasdataLink` next to it). Returns the venue name/rating/reviews/website/phone, a map link, a description, ticket sources (with official/unofficial flags), and the primary ticket link — details the SERP events widget does not show inline. The `pageToken` expires a few minutes after it is minted, so fetch it and call this endpoint promptly. Use to enrich an events search result with full venue and ticketing information.
| Name | Type | Req | Description |
|---|---|---|---|
| pageToken | string | yes | Token identifying a single event, taken from the `pageToken` field of an `eventsResults` entry in a `google/serp` response. Expires a few minutes after it is minted. |
No output schema declared.
No examples provided.
hasdata_google_serp_immersive_product_getImmersive_e29f691177 google_serp_immersive_product: GET / ~230
Get Immersive Product Information Expands the Google Shopping Immersive Product pop-up given an immersiveProductPageToken from the Google Shopping API, with optional moreStores (up to ~13 merchants instead of 3–5) and nextPageToken for paginating stores. Returns multi-store offers (merchant, price, shipping, URL), product specs, images, ratings, and the storesNextPageToken. Use for price-comparison bots, merchant discovery, dropshipping research, and aggregating full offer lists per product.
| Name | Type | Req | Description |
|---|---|---|---|
| moreStores | boolean | – | Fetch additional store results in a single search. By default it returns 3–5 stores, and when true it returns up to 13 or the maximum available for the product. |
| nextPageToken | string | – | Token used to retrieve the next page of store results. |
| pageToken | string | yes | Token for displaying more product info in the Google immersive pop-up, available in the Google Shopping API response as the `immersiveProductPageToken` property. |
No output schema declared.
No examples provided.
hasdata_google_serp_news_getGoogleNews google_serp_news: GET / ~385
Get Google News Results Retrieves Google News results by free-text query, topicToken (World, Business, Technology, etc.), sectionToken, publicationToken (e.g. CNN, BBC), or storyToken (full-coverage cluster with sort by relevance/date). Returns article title, snippet, source publisher, published date, thumbnail, and URL, plus tokens for navigating topics, sub-sections, and story clusters. Use for news monitoring, brand/PR tracking, topical aggregators, publisher-specific feeds, and drilling into full story coverage.
| Name | Type | Req | Description |
|---|---|---|---|
| gl | string | – | The two-letter country code for the country you want to limit the search to. Provide one exact documented value (245 allowed), e.g. `ac`, `af`. |
| hl | string | – | The two-letter language code for the language you want to use for the search. Provide one exact documented value (159 allowed), e.g. `af`, `ak`. |
| publicationToken | string | – | Token for a specific publisher such as CNN or BBC. Not allowed with `q`, `storyToken`, or `topicToken`. |
| q | string | – | Free-text query as used on news.google.com. Not allowed with `topicToken`, `storyToken`, or `publicationToken`. |
| sectionToken | string | – | Token for a sub-section under a topic, for example Business → Economy. Use only when `topicToken` or `publicationToken` is present. |
| so | string | – | Sort order for articles in a story. Use only with storyToken. |
| storyToken | string | – | Token for a single news story cluster (the “Full coverage” page). |
| topicToken | string | – | Token for a Google News topic such as World, Business, or Technology. Not allowed with `q`, `storyToken`, or `publicationToken`. |
No output schema declared.
No examples provided.
hasdata_google_serp_product_getProductInformation google_serp_product: GET / ~525
Get Product Information Pulls detailed product data from Google Shopping by productId with searchType (offers, specs, reviews) and rich filters (free shipping, used-condition, sort by price/total price/deals/seller rating, reviews count). Returns product title, images, price, ratings, specs, merchant offers (seller, shipping, condition, total price), and review text depending on searchType. Use for price intelligence, catalog enrichment, review mining, competitor spec comparison, and building shopping assistants that surface the cheapest or highest-rated offer.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Google domain to use. Default is google.com. Provide one exact documented value (195 allowed), e.g. `google.ac`, `google.ad`. |
| filter | string | – | Filter parameter for refining search results. Supports various filters for offers and reviews. Multiple filters can be passed using a comma. The available filters are: Offers filters: - `freeship:1`… |
| gl | string | – | The two-letter country code for the country you want to limit the search to. Provide one exact documented value (245 allowed), e.g. `ac`, `af`. |
| hl | string | – | The two-letter language code for the language you want to use for the search. Provide one exact documented value (159 allowed), e.g. `af`, `ak`. |
| location | string | – | Google canonical location for the search. |
| productId | string | yes | The product ID to get results for. |
| searchType | string | – | Parameter for fetching specific product information, such as 'offers', 'specs', or 'reviews'. |
| start | number | – | This parameter specifies the number of search results to skip and is used for pagination. For example, a value of 0 (default) indicates the first page of results, 10 refers to the second page, and 20… |
| uule | string | – | The encoded location parameter. |
No output schema declared.
No examples provided.
hasdata_google_serp_serp_getSearchResults google_serp_serp: GET / ~1,059
Get Google Search Results Full-featured Google Search scraper with location/uule, country (gl), language (hl, lr), domain, device type, safesearch, time/date filters via tbs (qdr, cdr), and tbm vertical selection (images, videos, news, shopping, local), plus offset/num pagination (num capped at 10 without tbm). Returns organic results (title, link, snippet, position), ads, knowledge graph, related searches, People Also Ask, local pack, featured snippets, AI Overview pageToken, and rich SERP features. Use for SEO rank tracking, keyword research, SERP-feature monitoring, competitor analysis, grounding LLMs with fresh location-aware search data, and especially for person/company data enrichment — e.g. finding a person's LinkedIn/Instagram/Twitter profile (`Roman Milyushkevich LinkedIn`, `HasData Instagram`), a company's CEO/founder/leadership (`HasData CEO`, `HasData founder`), contact emails (`Roman Milyushkevich HasData email`), phone numbers, GitHub profiles, press mentions, or any public attribute of a person or business by running a targeted query and parsing the top organic results.
| Name | Type | Req | Description |
|---|---|---|---|
| deviceType | string | – | Specify the device type for the search. |
| domain | string | – | Google domain to use. Default is google.com. Provide one exact documented value (195 allowed), e.g. `google.ac`, `google.ad`. |
| filter | number | – | Defines whether to enable or disable the filters for 'Similar Results' and 'Omitted Results'. Set to 1 (default) to enable these filters, or 0 to disable them. |
| gl | string | – | The two-letter country code for the country you want to limit the search to. Provide one exact documented value (245 allowed), e.g. `ac`, `af`. |
| hl | string | – | The two-letter language code for the language you want to use for the search. Provide one exact documented value (159 allowed), e.g. `af`, `ak`. |
| kgmid | string | – | Google Knowledge Graph ID. |
| location | string | – | Google canonical location for the search. |
| lr | array | – | The 'lr' parameter specifies the language of the websites to return results from. This parameter filters results based on the language of the web content. |
| lsig | string | – | Additional Google Place ID. |
| ludocid | string | – | The Google Place ID for a specific location. |
| nfpr | number | – | Controls if auto-corrected results are shown. 0 includes them (default), 1 shows only the original query. Google may still return auto-corrected results if no others are available. |
| num | number | – | Number of results per page, ranging from 10 to 100. |
| q | string | yes | Specify the search term for which you want to scrape the SERP. |
| safe | string | – | Adult Content Filtering option. |
| si | string | – | Google Cached Search Parameters ID. |
| start | number | – | This parameter specifies the number of search results to skip and is used for implementing pagination. For example, a value of 0 (default) indicates the first page of results, 10 refers to the second… |
| tbm | string | – | Specify the type of search. |
| tbs | string | – | This parameter supports various filters that can be combined by separating them with a comma. Here are examples of these filters: - Specific Time Range: `cdr:1,cd_min:10/17/2018,cd_max:3/8/2021` -… |
| uule | string | – | The encoded location parameter. |
No output schema declared.
No examples provided.
hasdata_google_serp_serp_light_getSearchResults google_serp_serp_light: GET / ~876
Get Google Light Search Results Google Search scraper served from the lightweight no-JS layout, cheaper and faster than the full SERP API. Returns organic results (title, link, displayed link, snippet, sitelinks, extensions, date, rating and review count), AI Overview with its text blocks and source references, answer box (featured snippet, calculator, unit and currency conversion, local time), knowledge graph, related questions, related searches, inline images, local pack, search filters, pagination, spelling correction and the location Google actually applied. Shopping, top stories, news, videos and jobs blocks are not served in this layout. Supports location/uule, country (gl), language (hl/lr), domain, safesearch, and time/date filters via tbs (qdr, cdr) with offset/num pagination (num capped at 10). Use for high-volume keyword monitoring, bulk rank tracking, backlink discovery, and AI Overview presence tracking.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Google domain to use. Default is google.com. Provide one exact documented value (195 allowed), e.g. `google.ac`, `google.ad`. |
| filter | number | – | Defines whether to enable or disable the filters for 'Similar Results' and 'Omitted Results'. Set to 1 (default) to enable these filters, or 0 to disable them. |
| gl | string | – | The two-letter country code for the country you want to limit the search to. Provide one exact documented value (245 allowed), e.g. `ac`, `af`. |
| hl | string | – | The two-letter language code for the language you want to use for the search. Provide one exact documented value (159 allowed), e.g. `af`, `ak`. |
| location | string | – | Google canonical location for the search. |
| lr | array | – | The 'lr' parameter specifies the language of the websites to return results from. This parameter filters results based on the language of the web content. |
| num | number | – | Number of results per page, ranging from 10 to 100. |
| q | string | yes | Specify the search term for which you want to scrape the SERP. |
| safe | string | – | Adult Content Filtering option. |
| start | number | – | This parameter specifies the number of search results to skip and is used for implementing pagination. For example, a value of 0 (default) indicates the first page of results, 10 refers to the second… |
| tbs | string | – | This parameter supports various filters that can be combined by separating them with a comma. Here are examples of these filters: - Specific Time Range: `cdr:1,cd_min:10/17/2018,cd_max:3/8/2021` -… |
| uule | string | – | The encoded location parameter. |
No output schema declared.
No examples provided.
hasdata_google_serp_shopping_getSearchResults google_serp_shopping: GET / ~762
Get Shopping Search Results Scrapes Google Shopping listings for a query with location/uule, country/language/domain, time/date filters, device type, shoprs filter-helper IDs, and offset pagination. Returns product title, price, merchant/source, rating, reviews count, thumbnail, product link, productId, immersiveProductPageToken, and filter chips with hasdata_link for refining by brand/price/condition/promotions. Use for e-commerce price tracking, catalog building, promotion discovery, and feeding productIds into the Product API or tokens into the Immersive Product API for deeper data.
| Name | Type | Req | Description |
|---|---|---|---|
| deviceType | string | – | Specify the device type for the search. |
| domain | string | – | Google domain to use. Default is google.com. Provide one exact documented value (195 allowed), e.g. `google.ac`, `google.ad`. |
| gl | string | – | The two-letter country code for the country you want to limit the search to. Provide one exact documented value (245 allowed), e.g. `ac`, `af`. |
| hl | string | – | The two-letter language code for the language you want to use for the search. Provide one exact documented value (159 allowed), e.g. `af`, `ak`. |
| location | string | – | Google canonical location for the search. |
| q | string | yes | Specify the search term for which you want to scrape the SERP. |
| shoprs | string | – | Specifies the helper ID for applying search filters. Must be used with the updated `q` parameter, which includes the selected filter (e.g., Coffee sale). To apply filters, use the `hasdata_link` fro… |
| start | number | – | This parameter specifies the number of search results to skip and is used for implementing pagination. For example, a value of 0 (default) indicates the first page of results, 40 refers to the second… |
| tbs | string | – | This parameter supports various filters that can be combined by separating them with a comma. Here are examples of these filters: - Specific Time Range: `cdr:1,cd_min:10/17/2018,cd_max:3/8/2021` -… |
| uule | string | – | The encoded location parameter. |
No output schema declared.
No examples provided.
hasdata_google_serp_short_videos_getShortVideosSearchResults google_serp_short_videos: GET / ~462
Get Short Videos Search Results Scrapes the Google Short Videos carousel (TikTok, YouTube Shorts, Instagram Reels, etc.) for a query with location/uule, country (gl/cr), language (hl/lr), device type, and page-based pagination. Supports Google's advanced filters (tbs). Returns video title, thumbnail, duration, source platform, channel/creator, direct video URL, the platform's video ID and profile handle, and ready-to-call HasData API links (hasdataLinks) for the video's comments, transcript, profile, posts or channel. Use for short-form content discovery, viral-trend monitoring, influencer research, cross-platform video aggregation, and sourcing short clips to summarize or embed in LLM responses.
| Name | Type | Req | Description |
|---|---|---|---|
| cr | string | – | The country code for the country you want to limit the search to. Provide one exact documented value (237 allowed), e.g. `countryAF`, `countryAL`. |
| deviceType | string | – | Specify the device type for the search. |
| gl | string | – | The two-letter country code for the country you want to limit the search to. Provide one exact documented value (245 allowed), e.g. `ac`, `af`. |
| hl | string | – | The two-letter language code for the language you want to use for the search. Provide one exact documented value (159 allowed), e.g. `af`, `ak`. |
| location | string | – | Google canonical location for the search. |
| lr | array | – | The 'lr' parameter specifies the language of the websites to return results from. This parameter filters results based on the language of the web content. |
| page | number | – | Page number for paginated results, where 0 is the first page. |
| q | string | yes | Search query term for retrieving short videos results. |
| tbs | string | – | Google advanced search filters, combined with commas. For example: - `qdr:h`, `qdr:d`, `qdr:w`, `qdr:m`, `qdr:y` - Show videos from the past hour, day, week, month, or year. |
| uule | string | – | The encoded location parameter. |
No output schema declared.
No examples provided.
How do I install the HasData Google Search (SERP) MCP server?
HasData Google Search (SERP) is a hosted endpoint at https://mcp.hasdata.com/mcp?apis=google_serp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.hasdata.com
claude mcp add --transport http com-hasdata-google-search 'https://mcp.hasdata.com/mcp?apis=google_serp'
What is the HasData Google Search (SERP) MCP server?
HasData Google Search (SERP) is an MCP server listed in the public MCP registry as com.hasdata/google-search. Google SERP as JSON: organic, AI Overview, People Also Ask, AI Mode, news, shopping. No Cloud setup. This page covers its hosted endpoint (https://mcp.hasdata.com/mcp?apis=google_serp).
Is the HasData Google Search (SERP) MCP server safe to use?
HasData Google Search (SERP) scores 86 out of 100 on VerifyMCP. 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 HasData Google Search (SERP) MCP server expose?
HasData Google Search (SERP) exposes 10 tools: hasdata_google_serp_ai_mode_getAiModeResponse, hasdata_google_serp_ai_overview_getAiOverviewResponse, hasdata_google_serp_events_getEventInformation, hasdata_google_serp_immersive_product_getImmersive_e29f6911…, hasdata_google_serp_news_getGoogleNews, and 5 more. Their descriptions and schemas cost roughly 4,958 tokens of context every time the server is loaded.
Does the HasData Google Search (SERP) MCP server require authentication?
Yes. HasData Google Search (SERP) asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the HasData Google Search (SERP) MCP server still maintained?
HasData Google Search (SERP) is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.