Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Semscraper

REMOTE · MCP.SEMSCRAPER.COM

Real Google and Google Maps SERPs for AI assistants: pixel positions, AI Overviews and sources.

+3 this week 72 Trust /100

Last scanned (9 minutes ago)

Scores higher than 62% of remote servers

Reachable. Last reached 23 Oct 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

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 Security74
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2520 tokens (~315/item across 8 items; 8 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 Management23
  • Stability observed for 7 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
Changelog

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.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 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.

  • 21 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.

  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 16 Oct 26 +36
    • Transport: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • Authorization: fail → partial ▲ security
    • First check of Judged manipulation: pass security
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ 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: fail functional
    • First check of Tool coverage: 100 functional
  • 10 Oct 26 33

    First indexed and scored.

Diagnostics

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 23 Oct 2026 · Probed https://mcp.semscraper.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.semscraper.com CN=YE1,O=Let's Encrypt,C=US 20 Sept 2026 19 Dec 2026 ECDSA 256 ECDSA-SHA384 5dc2c2f3837e56ce8e40e7ba401ae8fd09f
SANs: *.semscraper.com, semscraper.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.semscraper.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
semscraper.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.semscraper.com/mcp Verified 200
http (plaintext) http://mcp.semscraper.com/mcp HTTPS enforced 301 https://mcp.semscraper.com/mcp
MCP tools · 8 exposed · ~2,037 tokens

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 →

Tool Tokens
ai_overview_sources ~171

Computes, on the server, which domains Google cites in the AI Overviews of searches already created (google_search IDs): for each domain, the number of keywords where it is cited, the number of mentions, the keywords and its best position on the page. Also returns how many searches have an AI Overview. Free. Best tool to answer "which sites does Google cite in its AI Overviews on these keywords": one small answer instead of every SERP. Based on source URLs, not on brand names.

NameTypeReqDescription
idsarrayyesIDs of google_search searches (serp_...).
topinteger–Number of domains returned, most cited first.
wait_secondsinteger–How long to wait for searches still running, in seconds (default 45, max 55).

No output schema declared.

No examples provided.

get_balance ~23

Returns the balance of the Semscraper account, in euros. Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_queue_status ~47

Returns how many searches of the account are pending, processing or done. Free. The account has its own queue: the robots serve accounts in turn, so a large batch flows through gradually.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_serp_results ~285

Returns searches already created (google_search or google_maps), by their IDs (serp_...), e.g. the pending_ids of a previous call. Free: the searches were paid when created.

NameTypeReqDescription
blocksarray–Only return these result blocks, e.g. ["organic"] or ["ai_overview*"] (a trailing * matches a prefix). Block types: organic, paid_top, paid_bottom, local_pack, people_also_ask, featured_snippet, know…
domainstring–Only return the positions of this domain (e.g. "example.com", subdomains included) in every block, with its best organic rank and whether it appears in the AI Overview, instead of the whole SERP. Muc…
idsarrayyesIDs returned by a previous search (serp_...).
max_items_per_blockinteger–Maximum number of items returned per block, to keep the answer short.
wait_secondsinteger–How long this call waits for searches still running, in seconds (default 45, max 55). Call again while pending_ids remain.

No output schema declared.

No examples provided.

google_maps ~519

Collects the listings of a Google Maps search for one or more keywords, in the order Google Maps shows them, from a given place. Each listing comes with its rank, name (title), CID, category (type), address, website, rating, review count, opening status and the snippet shown. Use it for local SEO, local competition and market research. Paid from the account balance, same price as google_search. Returns rating and review count, not the full text of reviews.

NameTypeReqDescription
depthinteger–Number of Google result pages to collect, 1 (about 10 results) to 10 (about 100). Each extra page costs more and takes longer.
domainstring–Only return the positions of this domain (e.g. "example.com", subdomains included) in every block, with its best organic rank and whether it appears in the AI Overview, instead of the whole SERP. Muc…
geolocationstring–Place the search is made from: "City, Region, Country" or "latitude,longitude", with an optional zoom suffix ("43.7102,7.2620,16z"). Strongly recommended: Maps results depend on the location.
keywordsarrayyesKeywords to search, one search per keyword (max 100). Google operators work (site:, inurl:, intitle:, quotes, -term). No comma inside a keyword.
languagestring–Interface language code, e.g. fr, en, de, es, it, pt, ja. Must form a valid pair with location (see list_google_versions).
locationstring–Google version as a country code: fr for google.fr, de for google.de, br for google.com.br, jp for google.co.jp, us for google.com. Must form a valid pair with language (see list_google_versions).
max_items_per_blockinteger–Maximum number of items returned per block, to keep the answer short.
priorityinteger–Priority in the account queue, 1 to 10 (10 first). Use a high value for a few urgent searches when a large batch is already running.
wait_secondsinteger–How long this call waits for the results, in seconds (default 45, max 55). Searches still running are returned in pending_ids: fetch them with get_serp_results. Use 0 to start a large batch and retur…

No output schema declared.

No examples provided.

google_search ~699

Collects the real Google results page (SERP) for one or more keywords, rendered in a real browser, and returns every block (organic results, ads, local pack, People Also Ask, AI Overview with its citations and sources...) with, for each item, its rank in its block (rank_type), its rank on the page (rank_serp), its Google page and its pixel position. Use it to know what Google actually shows for a query, in a given country, language, city and device. Paid from the account balance: about EUR 0.0003 per keyword for the first page, EUR 0.0002 per extra page. Takes about 30 seconds per keyword (about a minute for 10 pages); the tool waits for the results. Returns titles, snippets and URLs, not the full content of the pages.

NameTypeReqDescription
blocksarray–Only return these result blocks, e.g. ["organic"] or ["ai_overview*"] (a trailing * matches a prefix). Block types: organic, paid_top, paid_bottom, local_pack, people_also_ask, featured_snippet, know…
depthinteger–Number of Google result pages to collect, 1 (about 10 results) to 10 (about 100). Each extra page costs more and takes longer.
devicestring–Device to emulate.
domainstring–Only return the positions of this domain (e.g. "example.com", subdomains included) in every block, with its best organic rank and whether it appears in the AI Overview, instead of the whole SERP. Muc…
geolocationstring–Optional city-level geolocation: "City, Region, Country" (e.g. "Lyon, Rhone, France") or a GPS position "latitude,longitude" (e.g. "43.7102,7.2620").
keywordsarrayyesKeywords to search, one search per keyword (max 100). Google operators work (site:, inurl:, intitle:, quotes, -term). No comma inside a keyword.
languagestringyesInterface language code, e.g. fr, en, de, es, it, pt, ja. Must form a valid pair with location (see list_google_versions).
locationstringyesGoogle version as a country code: fr for google.fr, de for google.de, br for google.com.br, jp for google.co.jp, us for google.com. Must form a valid pair with language (see list_google_versions).
max_items_per_blockinteger–Maximum number of items returned per block, to keep the answer short.
priorityinteger–Priority in the account queue, 1 to 10 (10 first). Use a high value for a few urgent searches when a large batch is already running.
wait_secondsinteger–How long this call waits for the results, in seconds (default 45, max 55). Searches still running are returned in pending_ids: fetch them with get_serp_results. Use 0 to start a large batch and retur…

No output schema declared.

No examples provided.

list_google_versions ~88

Lists the supported Google versions as location / language pairs (186 Google domains, 117 languages), to pick valid location and language values. Free. Filter with a country domain, a code or a language name to keep the answer short.

NameTypeReqDescription
filterstring–Text to look for in the domain, codes or language name, e.g. "google.de", "br", "Deutsch".

No output schema declared.

No examples provided.

list_searches ~205

Lists the searches of the account, most recent first (ID, engine, keyword, device, location, language, depth, geolocation, status, whether the results were already fetched, cost, creation date), without their results. Free. Covers every search made with the account, through this server or the API. Use it to find IDs (e.g. "the last 10 searches", "today's searches"), and whenever a google_search or google_maps call failed, timed out or lost its answer: the searches were probably created and paid already, so fetch them with get_serp_results instead of searching again.

NameTypeReqDescription
cursorstring–next_cursor from a previous call, to get the following page.
datestring–Only the searches created that day, format YYYY-MM-DD (server time, Europe/Paris).
limitinteger–Number of searches returned (default 20).
statusstring–Only the searches with this status.

No output schema declared.

No examples provided.

Install

How do I install the Semscraper MCP server?

Semscraper is a hosted endpoint at https://mcp.semscraper.com/mcp, 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.semscraper.com

# add to Claude Code
claude mcp add --transport http com-semscraper-semscraper 'https://mcp.semscraper.com/mcp'
Common questions

What is the Semscraper MCP server?

Semscraper is an MCP server listed in the public MCP registry as com.semscraper/semscraper. Real Google and Google Maps SERPs for AI assistants: pixel positions, AI Overviews and sources. This page covers its hosted endpoint (https://mcp.semscraper.com/mcp).

Is the Semscraper MCP server safe to use?

Semscraper scores 72 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 Semscraper MCP server expose?

Semscraper exposes 8 tools: google_search, google_maps, get_serp_results, ai_overview_sources, list_searches, and 3 more. Their descriptions and schemas cost roughly 2,037 tokens of context every time the server is loaded.

Does the Semscraper MCP server require authentication?

No. We connected to Semscraper without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Semscraper MCP server still maintained?

Semscraper is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.