mcpbeat Sign in

IndexPulse MCP Server

answering

IndexPulse is answering right now. Last checked 9 min ago.

Bing Webmaster, IndexNow and Google Search Console for AI: rankings, indexing gaps, AI crawlers.

Uptime history 67 hours of history
67 hours agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
126 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check IndexPulse every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add indexpulse --transport http https://indexpulse.puzaricloud.in/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "indexpulse": {
      "url": "https://indexpulse.puzaricloud.in/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.indexpulse]
url = "https://indexpulse.puzaricloud.in/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "indexpulse": {
      "url": "https://indexpulse.puzaricloud.in/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "indexpulse": {
      "url": "https://indexpulse.puzaricloud.in/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://indexpulse.puzaricloud.in/mcp streamable-http sign-in 148 ms 9 min ago

Alternatives to IndexPulse

same job, measured the same way
Google Search Console
by b77

Search rankings, clicks, and indexing for your site — in chat.

answering
Google Search Console
by akzar1el

Google Search Console MCP for analytics, indexing, sitemaps, and SEO diagnostics.

112 installs/wk local only
GSC Wizard
by gscwizard

SEO analysis of your Google Search Console, Bing Webmaster Tools and GA4 data. Google sign-in.

answering
SEO Webmaster MCP
by jvnndev

Read-only SEO and GEO audits with Google Search Console, Bing, and website crawling.

42 installs/wk local only
Murkuz SEO
by murkuz

Query your Google Search Console, GA4 and Bing Webmaster data across every site you run.

answering
Gsc
by mikusnuz

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

836 installs/wk local only
Google E-commerce (GA4, Search Console, Merchant Center)
by mooneyes

Read-only GA4, Search Console, Merchant Center, Tag Manager, Indexing and PageSpeed for shops.

352 installs/wk local only
Google Webtools MCP
by stufently

Google Search Console + GA4 for AI agents: properties, reports, indexing, verification, SEO.

local only

IndexPulse — questions

Answers built from our own checks of this server.

Why is there no tool list for IndexPulse?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is IndexPulse working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 126 ms. The bar chart above shows every period we have measured.
How do I connect IndexPulse?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to IndexPulse?
No API key is involved. IndexPulse answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is IndexPulse?
It answers our handshake in 126 ms on average, which is faster than 80% 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.