Ext Ops Panel
Open dashboard
Comparison

rankpulse vs Google Search Console

rankpulse is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.

rankpulse is a plugin bundle for AI coding tools published by Stéphane Truphème. No marketplace we read lists it any more. Google Search Console is an MCP server published by AKzar1el. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplacerankpulseGoogle Search Console
Community marketplace captain-marketing/rankpulse Removed on 2026-10-18
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.40-registry.1
Downloads/month (npm): 3 559
Downloads/week (npm): 94
Forks (GitHub): 1
Stars (GitHub): 6
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

rankpulse vs Google Search Console
Factrankpulseno longer listed · Google Search Console
Marketplaces that list it (differs)01
Stars (GitHub) (differs)36
Forks (GitHub) (differs)01
Last release (differs)Not published2026-10-27
Where it runs (differs)Installs as a plugin bundleOn your machine (@digestseo/mcp-gsc)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 06, secrets among them: 2
Hooks it runs (differs)3Not published
Parts of the bundle (differs)20Not a bundle
LicenceMITMIT
Repository (differs)github.com/captain-marketing/rankpulsegithub.com/akzar1el/mcp-gsc
Changes in the last 7 days (differs)05
First seen (differs)2026-10-152026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of rankpulse

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • TrafficBud SEO

    Real SEO data for AI assistants: page audits, Keyword Planner volumes, Search Console history.

    by trafficbud.io · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • Searcherries: AI Visibility & SEO

    Connect AI agents to your AI visibility and SEO data: competitors, citations, GSC, GA4, Bing.

    by searcherries.com · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • Ahrefs

    Research keywords, backlinks, rankings, and site health.

    by Cursor · Plugin bundle

    Listed on: Cursor: cursor/plugins · Describes nearly the same job

  • SEOPro AI

    Turn Search Console data into SEO actions, content, publishing, indexing, and AI insights.

    by alpha-ai-labs · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • Visibly AI — SEO MCP Server

    Remote SEO/GEO MCP: Search Console, keyword research, backlinks, competitor & on-page audits.

    by AntonioBlago · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • FastestRank SEO Intelligence

    Live SEO intelligence, rank tracking, site audits, and backlink analysis for AI agents.

    by fastestrank · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

rankpulse

In its own words, on Community GitHub marketplaces:

Live SEO data layer for Claude Code. Powered by DataForSEO, Google Search Console, and GA4.

Google Search Console

In its own words, on Official MCP Registry:

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

How to run each

rankpulse

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Google Search Console

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET (secret), TOKEN_ENCRYPTION_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only rankpulse asks for

  • DATAFORSEO_FULL_RESPONSE
  • DATAFORSEO_SIMPLE_FILTER

Only Google Search Console asks for

  • GOOGLE_CLIENT_ID
  • GOOGLE_CLIENT_SECRET (secret)
  • GSC_ACCESS_MODE
  • MCP_GSC_STATE_DIR
  • PORT
  • TOKEN_ENCRYPTION_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: rankpulse · What it can do: Google Search Console · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built