Skip to content

Early access Governed MCP calls open to beta partners in March 2027. The MCP tracker and scanner are free to use today.

Stackduke Radar

SerpApi MCP server

Featured official server

Changed

4 tools · Last check that passed 4 Nov 2026, 12:15 UTC

SerpApi's own remote MCP server gives an agent live search results from Google, Bing, YouTube, eBay and other engines, through the SerpApi account its API key belongs to. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.

All 4 tools

ToolCounted as
extractSaid to only read
searchSaid to only read
search_dashboardSaid to only read
search_tableSaid to only read

The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.

Recent checks

23 of the last 23 checks passed

A check passes when the server lists its tools. Checked at https://mcp.serpapi.com/mcp.

Recent changes

  1. 4 Nov 2026, 12:15 UTC, after a check on 3 Nov 2026, 12:01 UTC

    1 tool added: extract.

  2. 3 Nov 2026, 12:01 UTC, after a check on 2 Nov 2026, 13:18 UTC

    Inputs or outputs changed on search_dashboard, search_table.

From the scan of 4 Nov 2026, 12:43 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.

What to watch for
How to limit it

With SerpApi's own settings, as its documentation describes them. Stackduke has not tested them.

  • Send the API key in an Authorization header, as SerpApi recommends. SerpApi notes that a key in the address can appear in request logs. SerpApi's MCP server documentation
What Stackduke is designed to do

Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.

It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.

Stackduke is not affiliated with or endorsed by SerpApi. The SerpApi name belongs to its owner and is used here only to name its MCP server.

How the tracker works, and every other server it checks, is on the tracker page. The scanner and its data are open source at github.com/Stackduke/mcp-scanner.