Search Analyst MCP Server

by tidewellsoftware Your server? Claim it

not responding

Search Analyst is listed as active in the registry but did not answer our last check.

Google Search Console + Bing analysis: traffic drops, decaying pages, keyword gaps, URL inspection

Uptime history 27 hours of history · worst hour 0%

27 hours agonow

4.3%

Uptime 24h

4 of 92 checks

—

Tools

hidden behind auth

139 ms

Response time

average over 24h

open, no key

Access

streamable-http

Search Analyst does not always answer

Over the last week it answered 10.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add search-analyst --transport http https://search.tidewellsoftware.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://search.tidewellsoftware.com/mcp

~/.codex/config.toml

[mcp_servers.search-analyst]
url = "https://search.tidewellsoftware.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "search-analyst": {
      "url": "https://search.tidewellsoftware.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "search-analyst": {
      "type": "http",
      "url": "https://search.tidewellsoftware.com/mcp"
    }
  }
}

Endpoints

URL	Transport	State	Latency	Checked
https://search.tidewellsoftware.com/mcp	streamable-http	answering	34 ms	3 min ago

Alternatives to Search Analyst

same job, measured the same way

Google Search Console MCP

by mcpsearchconsole

Google Search Console SEO analytics, keyword rankings, URL inspection, sitemaps, PageSpeed checks.

answering

Google Search Console

by sarahpark

Google Search Console MCP server — search analytics, URL inspection, and sitemaps

124 installs/wk local only

Google Gsc

by mharnett

Google Search Console MCP: search analytics, URL inspection, site management.

76 installs/wk local only

Google Search Console MCP

by a1-x-tech

MCP server for the Google Search Console API: search analytics, sitemaps, URL inspection, sites.

415 installs/wk local only

Google Search Console

by ni-c

MCP server for Google Search Console: properties, sitemaps, search analytics and URL inspection

95 installs/wk local only

Gsc

by mikusnuz

MCP server for Google Search Console & Indexing API — search analytics, sitemaps, URL inspection

148 installs/wk local only

Google Search Console MCP Server

by conorbronsdon

Google Search Console for AI agents: search analytics, sitemaps, URL inspection.

59 installs/wk local only

Google Search Console MCP

by scalably

Read-only Google Search Console MCP: Search Analytics, sitemaps, URL inspection. 5 tools.

172 installs/wk local only

Search Analyst — questions

Answers built from our own checks of this server.

Is Search Analyst working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 4 of 92 checks got a reply (4.3%), average response time 139 ms. The bar chart above shows every period we have measured.

The registry lists Search Analyst as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Search Analyst?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Search Analyst need an API key?

No. Search Analyst completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.

How fast is Search Analyst?

It answers our handshake in 139 ms on average, which is faster than 85% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.