mcpbeat Sign in

Rankparse MCP Server

by abhibavishi Your server? Claim it
answering

Rankparse MCP is answering right now. Last checked 13 min ago. It exposes 73 tools.

SEO MCP server — backlinks, domain authority, tech stack, and 18+ tools via Common Crawl.

Uptime history 47 days of history
47 days agonow
100.0%
Uptime 24h
91 of 91 checks
73
Tools
read from the server
852 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 60

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 12 August 2026. No other catalogue keeps this.

16 Sep 5 tools appeared get_rank_alert_settings, list_rank_change_alerts, provision_indexnow_key and 2 more
16 Sep a tool changed the parameters it asks for get_keyword_rank_history
8 Sep a tool description was rewritten get_schema_markup
5 Sep 4 tools appeared get_keyword_rank_history, get_keyword_rankings, list_rank_tracking_sites and 1 more
21 Aug 3 tools appeared zeekeo_activate_campaign, zeekeo_create_campaign, zeekeo_create_template
21 Aug 2 tool descriptions were rewritten zeekeo_list_campaigns, zeekeo_send_message
20 Aug 2 tools appeared zeekeo_list_campaigns, zeekeo_send_message
14 Aug 24 tool descriptions were rewritten27 times that day get_competitor_gap, get_google_ads_accounts, get_google_ads_keyword_ideas and 21 more
14 Aug 5 tools appeared outreach_configure_sending, outreach_pause_campaign, outreach_resume_campaign and 2 more
14 Aug 2 tools changed the parameters they ask for outreach_add_contacts, outreach_create_campaign
and 11 more, back to 12 August 2026

Nothing serious here today

Today is the operative word: we check Rankparse MCP 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 13 min ago.

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

Available tools 73

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

gsc
get_gsc_country_breakdown
Get search traffic broken down by country. Useful for understanding geographic audience and international SEO performance. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_date_trends
Get daily search performance trends (clicks, impressions, CTR, position) over a date range. Useful for spotting ranking changes, traffic drops, or algorithm update impact. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_device_breakdown
Get search traffic broken down by device type (desktop, mobile, tablet). Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_low_ctr_pages
Find pages with high impressions but low CTR: pages that Google is showing frequently but users aren't clicking. Good starting point for title/description rewrites. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_low_ctr_queries
Find search queries with high impressions but low CTR. These are ranking but not getting clicked, usually because the title or meta description is weak or misleading. Fixing these is typically higher ROI than chasing new rankings. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_opportunity_queries
Find queries where the site ranks on positions 8–20 (page 1 bottom / page 2), the "quick win" zone where small improvements can meaningfully increase clicks. Returns queries sorted by clicks descending (GSC API default). Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_page_queries
Get search queries driving traffic to a specific page. Useful for understanding what a page ranks for. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_page_segment
Analyze search performance for a URL segment, e.g. all blog posts ("/blog/"), all product pages ("/products/"), or all docs ("/docs/"). Returns the top pages within that segment by clicks. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_page_trend
Get daily click/impression/CTR/position trend for a specific page. Use this to see how a single page's search performance has changed over time, useful for measuring the impact of a content update or spotting a ranking drop. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_properties
List all Google Search Console properties (sites) connected to this account. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_query_page_pairs
Get query+page combinations: which exact queries are landing on which pages. Essential for detecting keyword cannibalization (multiple pages competing for the same query) and understanding the search funnel. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_query_pages
Get all pages that rank for a specific search query. Useful for identifying which pages compete for the same keyword. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_query_trend
Get daily click/impression/CTR/position trend for a specific search query. Use this to track how a particular keyword's ranking and traffic evolves over time. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_search_appearance
Break down traffic by how the site appears in Google Search: organic web results, rich results, AMP, image search, video, news, etc. Shows which search features are driving impressions and clicks. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_sitemaps
List all submitted sitemaps for a property, including submission date, last download time, URL counts, and any errors or warnings. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_top_pages
Get the top pages on a site by clicks from Google Search, with impressions, CTR, and average position. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_top_queries
Get the top search queries driving traffic to a site, ordered by clicks. Shows clicks, impressions, CTR, and average position for each query. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
get_gsc_url_inspection
Inspect a specific URL's indexing status in Google Search. Returns whether the page is indexed, coverage state, last crawl time, mobile usability, and rich results status. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it.
outreach
outreach_add_contacts
Add contacts with per-contact email copy to a campaign (max 100 per call, 500 per campaign, one contact per domain). Works on a draft campaign AND on an already-launched one, which is how you top a live campaign up with fresh prospects. Each contact needs a researched, real email address (never guess addresses) plus a personalized subject and plain-text body (subject ≤500 chars, body ≤10,000). Write like a human: plain punctuation, and NEVER use em-dashes in subjects or bodies. Subjects must be 2-5 words that read like a note from a colleague and reference their content (e.g. "your AI tools guide"): never sales words like exclusive, lifetime, revenue, or deal. Internationalized (non-ASCII) domains must be given in punycode (xn--) form. Returns how many were added and which were skipped (invalid email, duplicate domain/email, copy too long, campaign full, already_contacted = this person was emailed in an earlier campaign). Contacts added to a launched campaign sit inert until you call outreach_launch_campaign again.
outreach_configure_sending
Update the Gmail sending schedule: max_sends_per_day (1-100, applies account-wide across all campaigns) and/or auto_send_enabled (false stops ALL sending, true resumes it). Confirm with the user before changing these; they control real email volume.
outreach_create_campaign
Create a draft link-building outreach campaign (sends via the user's connected Gmail). Outreach flow: 1) interview the user (their site, goal, competitors), 2) build a prospect list with get_competitor_gap / get_referring_domains / get_domain_authority, 3) research one real contact email per prospect domain, 4) write a short personalized subject+body per contact, 5) outreach_create_campaign, 6) outreach_add_contacts, 7) show the user the emails and get their OK, 8) outreach_launch_campaign. Requires the user to have Gmail connected at rankparse.com/dashboard/integrations. To CONTINUE an existing campaign rather than start a new one, begin at outreach_suggest_prospects instead of step 1 — campaigns are topped up, not replaced.
outreach_get_campaign
Get a campaign's status and delivery counts (awaiting launch, queued, sending, sent, skipped). Use to answer "how is my campaign doing?".
outreach_launch_campaign
LAUNCH a campaign: REAL EMAILS will be sent from the user's Gmail account, paced under their daily send cap by an hourly background sweep. Only call this after the user has seen the drafted emails and explicitly approved sending. Contacts already emailed in any previous campaign are automatically suppressed. Safe to call again on an already-launched campaign to queue newly added contacts: it arms only contacts not yet queued, and never re-sends anything. Returns queued/suppressed counts for THIS call and the estimated days to complete.
outreach_list_campaigns
List this account's outreach campaigns with status and contact counts.
outreach_pause_campaign
Pause one campaign: its queued emails stop sending but stay queued, so resuming continues exactly where it left off. Other campaigns keep sending.
outreach_resume_campaign
Resume a paused campaign; its queued emails become eligible for the next hourly send sweep again.
outreach_sending_status
Get the Gmail sending pipeline status: connected account, auto-send on/off, daily cap, how many sent today, remaining budget today, total queued across campaigns, and estimated days to drain the queue.
outreach_suggest_prospects
START HERE when adding more websites to an existing campaign. Returns the campaign's own context (domain, goal), how much room it has left, its send queue, and — critically — exclude_domains: every prospect domain this account has already used in ANY campaign. You MUST filter your discovery results against exclude_domains. get_competitor_gap is cached and unpaginated, so calling it again returns the identical top-N: request a limit several times larger than recommended_batch_size, drop everything already in exclude_domains, and keep what is left. Widen the pool with get_similar_domains, get_link_intersect, or get_platform_domains when the competitor gap is exhausted. Then research one real contact per surviving domain, call outreach_add_contacts, and finish with outreach_launch_campaign to queue them. Note exclude_domains_truncated: when true the list is capped and you should prefer clearly-unseen domains.
zeekeo
zeekeo_activate_campaign
Activates a paused Zeekeo campaign so it starts running (sends real LinkedIn connection invites per the campaign's configured limit/delay). Zeekeo campaigns are created paused by default — call this after zeekeo_create_campaign to actually start sending. This resumes REAL LinkedIn automation — confirm with the user before calling. Requires the user to have connected their own Zeekeo Launchpad account. Direct them to rankparse.com/dashboard/integrations to connect it.
zeekeo_create_campaign
Creates a Zeekeo LinkedIn campaign: sends a connection invite using invite_template_id, and optionally — if followup_template_id is given — waits for the invite to be accepted, then sends a follow-up message using that template. Create templates first with zeekeo_create_template. Provide exactly one of filter_url (a LinkedIn search results URL) or profile_urls (specific profiles) as the target. This starts REAL LinkedIn automation once the campaign has profiles in it — confirm with the user before calling. Requires the user to have connected their own Zeekeo Launchpad account. Direct them to rankparse.com/dashboard/integrations to connect it.
zeekeo_create_template
Creates a reusable Zeekeo message template. Call this BEFORE zeekeo_create_campaign — a campaign references templates by the template_id this returns, not inline text. type must be 'linkedin_invite' for a connection-request template, or one of linkedin_message/linkedin_inmail/email_message for a follow-up/reply template. Requires the user to have connected their own Zeekeo Launchpad account. Direct them to rankparse.com/dashboard/integrations to connect it.
zeekeo_list_campaigns
List the user's Zeekeo Launchpad campaigns (LinkedIn automation). Use this to find a campaign_id for zeekeo_send_message, or call zeekeo_create_campaign to make a new one. Requires the user to have connected their own Zeekeo Launchpad account. Direct them to rankparse.com/dashboard/integrations to connect it.
zeekeo_send_message
Sends a REAL LinkedIn message, InMail, or email through Zeekeo Launchpad to a profile in one of the user's existing Zeekeo campaigns. Only call this after showing the user the drafted message and getting explicit approval. Resolves linkedin_url into that campaign first, so the profile must be reachable from it (use zeekeo_list_campaigns to pick campaign_id). Requires the user to have connected their own Zeekeo Launchpad account. Direct them to rankparse.com/dashboard/integrations to connect it.
rank
get_rank_alert_settings
Get the rank-change alert configuration for one RankParse website: whether daily alert digests are enabled (they are opt-in and default off), the moved_up/moved_down position threshold, and the optional digest email override.
list_rank_change_alerts
List recent rank-change alert events for one RankParse website: significant stored-ranking moves (entered/left top 3 or top 10, moved up/down past the configured threshold, new/lost rankings) detected by the daily digest pass. Reads recorded events, never runs a live check; a keyword with no events simply had no significant moves. Events exist only while alerts are enabled for the site (see get_rank_alert_settings) and only for engines whose data was actually available -- provider-limited or pending engines generate nothing rather than false "lost ranking" alerts.
list_rank_tracking_sites
List websites configured for stored Google, Bing, and Yandex keyword tracking, including provider freshness and sync state. This reads RankParse snapshots; it does not run a live SERP check.
update_rank_alert_settings
Update rank-change alert settings for one RankParse website: enable/disable the daily digest (opt-in, default off), set the moved_up/moved_down position threshold (1-50, default 5), or set/clear an email override for that site's digest lines (null reverts to the account email). Only the fields you pass change. Confirm with the user before enabling -- this turns on a real daily email.
domain
get_domain_authority
Get authority score for a domain
get_domain_overlap
Find domains linking to all queried domains
get_domain_rank
Get inbound edge count and linking domain stats
google
get_google_ads_accounts
List the Google Ads accounts the connected Google user can access, as 10-digit customer IDs. Use this to help a user pick which account to select when they have more than one. Requires Google Ads to be connected and an Ads account selected. Direct the user to rankparse.com/dashboard/integrations. Returns search volume and competition data, NOT keyword rankings; use the Google Search Console tools for ranking and position data.
get_google_ads_keyword_ideas
Discover NEW keyword ideas from seed terms and/or a URL, with average monthly search volume, competition level, and top-of-page bid ranges. Use this for keyword research and content planning: "what should I target?". Supply seed keywords, a URL, or both. Requires Google Ads to be connected and an Ads account selected. Direct the user to rankparse.com/dashboard/integrations. Returns search volume and competition data, NOT keyword rankings; use the Google Search Console tools for ranking and position data.
get_google_ads_keyword_metrics
Get average monthly search volume, competition level, and top-of-page bid ranges for a SPECIFIC list of keywords, with no expansion into related terms. Use this when the user already has keywords in mind and wants them sized: "how much traffic are these worth?". For discovering new keywords instead, use get_google_ads_keyword_ideas. Requires Google Ads to be connected and an Ads account selected. Direct the user to rankparse.com/dashboard/integrations. Returns search volume and competition data, NOT keyword rankings; use the Google Search Console tools for ranking and position data.
link
get_link_audit
Audit a domain's backlink profile: health score, risk flags, link quality breakdown, anchor text profile, top and risky backlinks, and outbound link summary. Scores are derived from a sample of the 250 most recent backlinks, not the full profile.
get_link_intersect
Find domains linking to A but not B
get_link_velocity
Get rate of new/lost links over time (v1 stub)
keyword
get_keyword_rank_history
Get the stored day-by-day ranking history for one keyword on one search engine over a date range. Reads RankParse snapshots synced on a schedule; it is not a live SERP check. History is inherently single-engine, so engine is required (use get_keyword_rankings first to compare across engines). Days with no synced data are simply absent from rows rather than filled with a zero or placeholder value -- do not treat a missing date as "not ranking". Bing and Yandex are opt-in and lower-frequency than Google; their responses may report availability as provider_limited, meaning that provider did not return enough data for that day rather than the keyword ranking nowhere.
get_keyword_rankings
Get stored ranking summaries (current vs previous period) for a website's tracked keywords across Google, Bing, and Yandex. Reads RankParse snapshots synced on a schedule; it is not a live SERP check. Positions are provider-reported averages over each engine's own returned period and are NOT comparable as one blended rank across engines -- compare per engine, not by averaging across them. A missing engine in a keyword's response means that engine is not connected/attached for this site (check enabled_engines in the response), not a zero or bottom rank. Bing and Yandex are opt-in and many accounts do not have them connected, so their absence is normal, not an error. Each present engine also carries an availability field; a null current/previous position with availability other than "available" (e.g. provider_limited, which Bing/Yandex may report, or pending_first_sync, stale, sync_failed) means a data quality/sync issue for that engine, not evidence the keyword ranks nowhere.
page
get_page_performance
Google PageSpeed Insights report for a URL: Lighthouse performance/accessibility/SEO scores and Core Web Vitals (LCP, CLS, INP, FCP, TTFB), with lab and field (CrUX) data. Defaults to mobile; pass strategy=desktop for the desktop profile. Subject to a per-user daily cap (50/day) and a service-wide daily cap; successful responses are cached for 24h.
get_page_seo
Full real-time SEO audit for a URL: title/description with length checks, canonical, robots meta, OG tags, Twitter cards, JSON-LD, hreflang, headings, images missing alt, link counts, word count
platform
get_platform_domains
Get all domains running a specific platform or technology (e.g. WordPress, Shopify, Wix, Squarespace, Framer). Returns domains with DA scores. Billed at 1 credit per result returned.
get_platform_trends
Get a ranked list of all detectable platforms and technologies with their domain counts, useful for comparing platform adoption (e.g. how many sites run WordPress vs Shopify)
site
get_site_explorer
Full SEO overview for a domain (backlinks, authority, top pages, anchor text)
get_site_health
Real-time site health check: HTTPS enforcement, HSTS, www redirect behavior, key URL availability and response times, security headers (CSP, X-Frame-Options, HSTS), robots.txt analysis
anchor
get_anchor_text
Get anchor text distribution for a domain
backlinks
get_backlinks
Get backlinks for a domain. Default sort=importance returns aggregated referrer rows; sort=recent returns URL-level freshest links. Optional filters: from_domain, link_type, score.
batch
batch_lookup
Get backlinks for up to 50 domains at once
competitor
get_competitor_gap
Find domains linking to a competitor but not to you: ranked link-building prospects. Under time budget the response may come back with partial=true and scored=false, meaning the results are the raw gap set without domain-authority ranking; retrying the same request usually returns a fully scored answer.
crawl
get_crawl_history
Get first/last seen dates and total snapshot count for a domain (source: Wayback Machine)
credits
check_credits
Check remaining credit balance
internal
get_internal_links
Get internal link structure for a domain (v1 stub)
lost
get_lost_links
Get links lost since previous crawl (v1 stub)
new
get_new_links
Get links gained since previous crawl (v1 stub)
outbound
get_outbound_links
Get domains that a domain links out to
provision
provision_indexnow_key
Get (or create) the IndexNow key for a host. Idempotent per host: repeated calls return the same key. Free (0 credits). Returns the key, its required key_location (https://<host>/<key>.txt), and verified (whether the hosted key file has already been confirmed). The USER must host a UTF-8 text file containing exactly the key at key_location before submit_indexnow_urls will work — tell them the location and the key, then submit.
referring
get_referring_domains
Get unique domains linking to a domain
schema
get_schema_markup
Extract schema.org JSON-LD structured data from a URL: every entity found (including ones nested in @graph), their types, and any malformed blocks
similar
get_similar_domains
Find domains with similar link profiles, useful for competitor discovery. May return partial results when the query fan-out hits time budget.
sitemap
get_sitemap
Discover and parse a domain's sitemap. Returns URLs with lastmod, changefreq, and priority
submit
submit_indexnow_urls
Submit changed/new/deleted URLs to IndexNow so search engines (Bing, Yandex, Seznam, Naver, ...) recrawl them promptly. All URLs must share one host, max 1000 per call. Requires the host's IndexNow key file to be live: call provision_indexnow_key first and make sure the user hosted the key file at its key_location (indexnow_key_not_verified means the file is missing or wrong). Costs 1 credit, refunded automatically when the submission fails.
tech
get_tech_stack
Real-time technology detection for a domain: frameworks, CMS, analytics, CDN, hosting, e-commerce, payments, and more (50+ technologies)
top
get_top_pages
Get most-linked pages for a domain
tracked
list_tracked_keywords
List the tracked keyword IDs and text for one RankParse website. Call list_rank_tracking_sites first to obtain site_id.

Endpoints

URLTransportStateLatencyChecked
https://mcp.rankparse.com/mcp streamable-http answering 844 ms 13 min ago

Alternatives to Rankparse MCP

same job, measured the same way
SEO Backlinks
by mouhabmzibra-rgb

Backlinks, Domain Rating & expired-domain drops via seo-backlinks.net (Common Crawl)

41 installs/wk local only
CrawlConsole
by crawlconsole

Backlink Analysis MCP for AI Agents: authority, referring domains, and competitor link gaps.

37 installs/wk answering
Kitbag MCP
by syedtaj7

Zero-config MCP server bundling 50+ utility tools: converters, OCR, scraping, and formatters.

45 installs/wk local only
Crawlgraph
by pipeworx-io

CrawlGraph MCP — backlink intelligence on the public Common Crawl webgraph

42 tools answering
Rampify
by rampify

SEO MCP server: crawl your site, find AI-visibility gaps, and ship the fix from your coding agent.

answering
Crawlgraph MCP
by pucilpet

Backlink lookups and competitor gap analysis on Common Crawl's open web graph (4.4B links).

local only
Geekflare
by geekflare

Geekflare MCP server for scraping, search, screenshots, broken links, DNS lookup, and network tools.

62 installs/wk 18 tools answering
HasData
by hasdata

All HasData scraping tools in one MCP server: Google, TikTok, Instagram, maps, e-commerce and more.

answering

Rankparse MCP — questions

Answers built from our own checks of this server.

What can Rankparse MCP do?
It exposes 73 tools, read directly from the server on our last check. Among them: batch_lookup, check_credits, get_anchor_text, get_backlinks, get_competitor_gap, get_crawl_history and 67 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Rankparse MCP mostly used for?
Its tools cluster around gsc, outreach and zeekeo. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Rankparse MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 852 ms. The bar chart above shows every period we have measured.
How do I connect Rankparse MCP?
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.
Does Rankparse MCP need an API key?
No. Rankparse MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 73 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Rankparse MCP?
It answers our handshake in 852 ms on average, which is faster than 12% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.