An agent can connect on its own if it already holds SERPAPI_API_KEY.Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
Endpoints
remote
auth
reachable
uptime 30d
p50
protocol
last ok
https://mcp.serpapi.com/mcpstreamable-http
api_key ${SERPAPI_API_KEY}
yes
97%
196 ms
2026-07-28
2026-10-19
Tools (3)
searchread-only
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 clients receive a missing-parameter error. Cancellation does not run a search.
Examples:
Weather: {"params": {"q": "weather in London", "engine": "google"}, "mode": "complete"}
Stock: {"params": {"q": "AAPL stock", "engine": "google"}, "mode": "complete"}
General: {"params": {"q": "coffee shops", "engine": "google_light", "location": "Austin, TX"}, "mode": "complete"}
Compact: {"params": {"q": "news"}, "mode": "compact"}
Markdown: {"params": {"q": "news", "output": "md"}}
Supported engines include (not limited to):
- google
- google_light
- google_flights
- google_hotels
- google_images
- google_news
- google_local
- google_shopping
- google_jobs
- bing
- yahoo
- duckduckgo
- youtube_search
- baidu
- ebay
search_dashboardread-only
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).
search_tableread-only
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.