SerpApi
REMOTE · MCP.SERPAPI.COM
Official SerpApi MCP server for Google, Bing, and other search engines.
Available components
Last scanned (20 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 21 Nov 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability46
- 33% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1258 tokens (~179/item across 7 items; 4 tools + 3 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 Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 33% of tool parameters carry a description.Partial
- Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
- Supports UI / widget rendering.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 12 Nov 26 0
- Server version: 2.2.0 → 2.3.0 functional
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 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
- 4 Nov 26 −1
- Tool coverage: 50% → 33% ▼ functional
- Schema quality: 158 → 179 ▼ functional
- Tool coverage: 33% → 50% ▲ functional
- Server version: 2.1.0 → 2.2.0 functional
- New tool “extract” functional
- 3 Nov 26 0
- Server version: 2.0.0 → 2.1.0 functional
- 22 Oct 26 0
- Stability: 0.97 → pass security
- 29 Sept 26 0
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → partial ▲ 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 21 Nov 2026 · Probed https://mcp.serpapi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.serpapi.com | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 26 Oct 2026 | 11 May 2027 | RSA 2048 | SHA256-RSA | c69831d0f3cf69578a3d53d6d5619ae |
| SANs: mcp.serpapi.com | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.serpapi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| serpapi.com. | No DS | 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.serpapi.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.serpapi.com/mcp | Inconclusive | 405 |
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 →
extract SerpApi extract ~309
Extract content from a public http(s) URL, discover site URLs, or crawl pages. API options go in params: url is required; params.mode is scrape (default), map, or crawl. See serpapi://engines/extract for all options. Top-level mode controls the response: - complete (default): full JSON. - compact: native Markdown by default. params.output selects the format and overrides either default: - "md": return native Markdown unchanged in either response mode. - "json": return JSON, with filtering determined by the response mode. Compact JSON removes metadata. For scrape responses containing markdown, it also keeps only markdown and any error field. include_markdown=false or an explicit json_restrictor skips this extra filtering. Map/crawl and responses without markdown keep their remaining fields. Use complete with output="json" for full JSON. Crawl max_pages defaults to 10 (maximum 100). Each successfully extracted, uncached page consumes one credit. Examples: Full scrape JSON: {"params":{"url":"https://example.com"},"mode":"complete"} Scrape Markdown: {"params":{"url":"https://example.com"},"mode":"compact"} Map URLs as JSON: {"params":{"url":"https://example.com","mode":"map"},"mode":"complete"} Crawl pages as Markdown: {"params":{"url":"https://example.com","mode":"crawl","max_pages":2},"mode":"compact"}
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | – |
| params | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search SerpApi search ~707
Universal search tool supporting all SerpApi engines and result types. When to use: - Any query needing live, structured SERP data: web results, news, product listings, job postings, local businesses, flight/hotel prices, video results, images, stock/weather cards, knowledge graph entities. Engine discovery via MCP resources: - serpapi://engines lists all engines supported by this tool. - serpapi://engines/<engine> provides engine-specific parameters and supported options. - Example: serpapi://engines/google_news Input schema: params: JSON object containing SerpApi engine parameters. Common parameters: - q: Search query. Required for most engines. - engine: SerpApi engine name. Defaults to "google_light". - location: Optional geographic location for localized results. - output: Optional response format. Omit for JSON (default), or set to "md" for Markdown. Engine-specific parameters are available via MCP resources: - serpapi://engines lists all supported engines. - serpapi://engines/<engine> provides parameters and options for one engine. mode: Response mode. Defaults to "complete". - "complete": Return the full SerpApi response. - "compact": Remove metadata fields from JSON responses. Markdown is returned unchanged. Output schema: structuredContent.result contains the response string: serialized JSON or unchanged Markdown. The same string is included in text content. Tool failures preserve this wrapper and set isError to true. Guided search: Searches can request missing engine parameters from supporting clients using the engine catalog and engine-specific rules. Flights collect airports and dates, hotels collect the destination and stay dates, and directions collect missing endpoints. Other cli…
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | Response mode (default: "complete") - "complete": Returns the full response - "compact": Removes metadata fields from JSON responses; Markdown is unchanged |
| params | – | – | Dictionary of SerpApi engine-specific parameters. Common parameters include: - q: Search query (required for most engines) - engine: Search engine to use (default: "google_light") - location: Geograp… |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_dashboard SerpApi search (dashboard) ~86
Interactive dashboard variant of `search`: returns summary metrics, a source breakdown chart, and a results table with a click-to-expand detail panel, all rendered in the conversation. Same params as `search`. Use for a richer visual overview of a query's results. Automatically selects an engine-specific dashboard when available (e.g. google_flights gets price intelligence charting).
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | – | – |
No output schema declared.
No examples provided.
search_table SerpApi search (table) ~60
Interactive UI variant of `search`: returns organic results as a sortable, searchable table rendered in the conversation. Same params as `search`. Use when the host supports MCP Apps and the user wants to browse results visually rather than read JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | – | – |
No output schema declared.
No examples provided.
How do I install the SerpApi MCP server?
SerpApi is a hosted endpoint at https://mcp.serpapi.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.serpapi.com
claude mcp add --transport http serpapi-serpapi-mcp 'https://mcp.serpapi.com/mcp'
What is the SerpApi MCP server?
SerpApi is an MCP server listed in the public MCP registry as io.github.serpapi/serpapi-mcp. Official SerpApi MCP server for Google, Bing, and other search engines. This page covers its hosted endpoint (https://mcp.serpapi.com/mcp).
Is the SerpApi MCP server safe to use?
SerpApi scores 74 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 SerpApi MCP server expose?
SerpApi exposes 4 tools: search_dashboard, search_table, extract, search. Their descriptions and schemas cost roughly 1,162 tokens of context every time the server is loaded.
Does the SerpApi MCP server require authentication?
No. We connected to SerpApi without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SerpApi MCP server still maintained?
SerpApi is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the SerpApi MCP server?
VerifyMCP ran 13 checks on SerpApi, covering TLS certificate, Authorization, HSTS header, DNSSEC and 9 more. One item could not be completed, a gap on our side rather than a finding about SerpApi: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.