Data · Remote MCP server
SearchConsole.ai
Read-only Search Console analytics, URL inspection, indexing diagnostics, and sitemaps.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.searchconsole/searchconsole-ai- Version
- 1.0.1
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP
- Published
- 2026-09-22
- Updated
- 2026-09-22
- Publisher
- ai.searchconsole
- Namespace
- Namespace verified by the MCP Registry via the domain searchconsole.ai · how
- Website
- searchconsole.ai/?ref=mcp-registry
- Repository
- github.com/AndreyAzimov/searchconsole-ai
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://searchconsole.ai/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect SearchConsole.ai
SearchConsole.ai is a remote MCP server: there is nothing to install. Its endpoint is https://searchconsole.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More data servers
| Server | Runs |
|---|---|
| search-mcpWeb search and clean-text page fetch for AI agents, with SSRF protection. | Remote · HTTPLive check: ✓ handshake |
| search-rotationMCP server for web search and page extraction across the free tiers of several providers. | Local · stdio |
| searchapi.ioGive AI assistants access to real-time search data through SearchApi. | Remote · HTTP |
| SearchAtlasSearchAtlas AI Agent - SEO, content, PPC, authority building, and site management. | Local · stdio |
| SearchcraftFull-text search for Next.js. BM25 scoring and fuzzy matching, no external service. | Local · stdio |
| SearcherLiteSEO data for Google keywords, domains, backlinks and AI visibility. Pay per lookup, no subscription. | Remote · HTTPLive check: sign-in required |
| Searcherries: AI Visibility & SEOConnect AI agents to your AI visibility and SEO data: competitors, citations, GSC, GA4, Bing. | Remote · HTTPLive check: sign-in required |
| SearchLinkGoogle Search Console in your AI: overview, opportunities, index gaps, page checks, long history. | Remote · HTTPLive check: sign-in required |