# io.github.abhibavishi/rankparse-mcp (remote · mcp.rankparse.com)

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

- Trust score: 71/100 (medium)
- Change this week: +16
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.rankparse.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/abhibavishi-rankparse-mcp/mcp.md), [page](https://verifymcp.io/servers/abhibavishi-rankparse-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.rankparse.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 3658 tokens (~79/item across 46 items; 46 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 64% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http abhibavishi-rankparse-mcp https://mcp.rankparse.com/mcp
```

### Codex

```toml
[mcp_servers.abhibavishi-rankparse-mcp]
url = "https://mcp.rankparse.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "abhibavishi-rankparse-mcp": {
      "type": "remote",
      "url": "https://mcp.rankparse.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add abhibavishi-rankparse-mcp --url https://mcp.rankparse.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  abhibavishi-rankparse-mcp:
    url: "https://mcp.rankparse.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "abhibavishi-rankparse-mcp": {
      "type": "http",
      "url": "https://mcp.rankparse.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 71, +9)

- [functional improvement] Schema quality: unverified → good

### 2026-07-31 (score 62, +5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 57, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 56, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 55, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 54)

First indexed and scored.

## MCP tools (46)

### `get_backlinks` (~89 tokens)

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.

Input parameters:

- `domain` (string, required)
- `from_domain` (string)
- `limit` (number)
- `link_type` (string)
- `score` (boolean)
- `sort` (string)

### `get_referring_domains` (~39 tokens)

Get unique domains linking to a domain

Input parameters:

- `domain` (string, required)
- `limit` (number)
- `score` (boolean)

### `get_outbound_links` (~33 tokens)

Get domains that a domain links out to

Input parameters:

- `domain` (string, required)
- `limit` (number)

### `get_domain_authority` (~24 tokens)

Get authority score for a domain

Input parameters:

- `domain` (string, required)

### `get_domain_rank` (~25 tokens)

Get inbound edge count and linking domain stats

Input parameters:

- `domain` (string, required)

### `get_anchor_text` (~31 tokens)

Get anchor text distribution for a domain

Input parameters:

- `domain` (string, required)
- `limit` (number)

### `get_top_pages` (~31 tokens)

Get most-linked pages for a domain

Input parameters:

- `domain` (string, required)
- `limit` (number)

### `get_domain_overlap` (~31 tokens)

Find domains linking to all queried domains

Input parameters:

- `domains` (array, required)
- `limit` (number)

### `get_link_intersect` (~35 tokens)

Find domains linking to A but not B

Input parameters:

- `domain_a` (string, required)
- `domain_b` (string, required)

### `get_similar_domains` (~42 tokens)

Find domains with similar link profiles — useful for competitor discovery. May return partial results when the query fan-out hits time budget.

Input parameters:

- `domain` (string, required)

### `get_competitor_gap` (~89 tokens)

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.

Input parameters:

- `domain` (string, required)
- `limit` (number)
- `vs` (string, required)

### `get_link_audit` (~67 tokens)

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.

Input parameters:

- `domain` (string, required)

### `get_sitemap` (~43 tokens)

Discover and parse a domain's sitemap — returns URLs with lastmod, changefreq, and priority

Input parameters:

- `domain` (string, required)
- `limit` (number)

### `get_crawl_history` (~37 tokens)

Get first/last seen dates and total snapshot count for a domain (source: Wayback Machine)

Input parameters:

- `domain` (string, required)

### `get_page_seo` (~64 tokens)

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

Input parameters:

- `url` (string, required)

### `get_page_performance` (~111 tokens)

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.

Input parameters:

- `strategy` (string)
- `url` (string, required)

### `get_tech_stack` (~47 tokens)

Real-time technology detection for a domain — frameworks, CMS, analytics, CDN, hosting, e-commerce, payments, and more (50+ technologies)

Input parameters:

- `domain` (string, required)

### `get_site_health` (~58 tokens)

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

Input parameters:

- `domain` (string, required)

### `get_schema_markup` (~28 tokens)

Get schema.org markup for a URL (v1 stub)

Input parameters:

- `url` (string, required)

### `get_internal_links` (~35 tokens)

Get internal link structure for a domain (v1 stub)

Input parameters:

- `domain` (string, required)
- `limit` (number)

### `get_link_velocity` (~30 tokens)

Get rate of new/lost links over time (v1 stub)

Input parameters:

- `domain` (string, required)

### `get_new_links` (~27 tokens)

Get links gained since previous crawl (v1 stub)

Input parameters:

- `domain` (string, required)

### `get_lost_links` (~28 tokens)

Get links lost since previous crawl (v1 stub)

Input parameters:

- `domain` (string, required)

### `get_site_explorer` (~35 tokens)

Full SEO overview for a domain (backlinks, authority, top pages, anchor text)

Input parameters:

- `domain` (string, required)

### `batch_lookup` (~26 tokens)

Get backlinks for up to 50 domains at once

Input parameters:

- `domains` (array, required)

### `check_credits` (~14 tokens)

Check remaining credit balance

### `get_platform_domains` (~185 tokens)

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.

Input parameters:

- `limit` (number): Max results to return (default 100, max 1000)
- `max_da` (number): Maximum domain authority score (0–100)
- `min_da` (number): Minimum domain authority score (0–100)
- `platform` (string, required): Platform name or slug (e.g. "wordpress", "shopify", "wix", "squarespace", "framer")
- `sort` (string): Sort order: da_desc (default), da_asc, domain_asc
- `tld` (string): Filter by top-level domain (e.g. "com", "io", "co.uk")

### `get_platform_trends` (~43 tokens)

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)

### `get_gsc_properties` (~47 tokens)

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_top_queries` (~133 tokens)

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.

Input parameters:

- `endDate` (string, required): End date YYYY-MM-DD
- `rowLimit` (number): Max rows (default 25, max 1000)
- `site` (string, required): Property URL e.g. "https://example.com" or "sc-domain:example.com"
- `startDate` (string, required): Start date YYYY-MM-DD

### `get_gsc_top_pages` (~118 tokens)

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.

Input parameters:

- `endDate` (string, required): End date YYYY-MM-DD
- `rowLimit` (number): Max rows (default 25, max 1000)
- `site` (string, required): Property URL e.g. "https://example.com"
- `startDate` (string, required): Start date YYYY-MM-DD

### `get_gsc_page_queries` (~135 tokens)

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.

Input parameters:

- `endDate` (string, required): End date YYYY-MM-DD
- `page` (string, required): Full page URL e.g. "https://example.com/blog/post"
- `rowLimit` (number): Max rows (default 25, max 1000)
- `site` (string, required): Property URL e.g. "https://example.com"
- `startDate` (string, required): Start date YYYY-MM-DD

### `get_gsc_query_pages` (~137 tokens)

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.

Input parameters:

- `endDate` (string, required): End date YYYY-MM-DD
- `query` (string, required): Search query to look up e.g. "best seo tools"
- `rowLimit` (number): Max rows (default 25, max 1000)
- `site` (string, required): Property URL e.g. "https://example.com"
- `startDate` (string, required): Start date YYYY-MM-DD

### `get_gsc_date_trends` (~112 tokens)

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.

Input parameters:

- `endDate` (string, required): End date YYYY-MM-DD
- `site` (string, required): Property URL e.g. "https://example.com"
- `startDate` (string, required): Start date YYYY-MM-DD

### `get_gsc_country_breakdown` (~115 tokens)

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.

Input parameters:

- `endDate` (string, required): End date YYYY-MM-DD
- `rowLimit` (number): Max rows (default 25, max 1000)
- `site` (string, required): Property URL e.g. "https://example.com"
- `startDate` (string, required): Start date YYYY-MM-DD

### `get_gsc_device_breakdown` (~93 tokens)

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.

Input parameters:

- `endDate` (string, required): End date YYYY-MM-DD
- `site` (string, required): Property URL e.g. "https://example.com"
- `startDate` (string, required): Start date YYYY-MM-DD

### `get_gsc_sitemaps` (~79 tokens)

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.

Input parameters:

- `site` (string, required): Property URL e.g. "https://example.com"

### `get_gsc_url_inspection` (~106 tokens)

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.

Input parameters:

- `site` (string, required): Property URL e.g. "https://example.com"
- `url` (string, required): Full URL to inspect e.g. "https://example.com/blog/post"

### `get_gsc_query_page_pairs` (~134 tokens)

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.

Input parameters:

- `endDate` (string, required): End date YYYY-MM-DD
- `rowLimit` (number): Max rows (default 100, max 1000)
- `site` (string, required): Property URL e.g. "https://example.com"
- `startDate` (string, required): Start date YYYY-MM-DD

### `get_gsc_page_trend` (~144 tokens)

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.

Input parameters:

- `endDate` (string, required): End date YYYY-MM-DD
- `page` (string, required): Full page URL e.g. "https://example.com/blog/post"
- `site` (string, required): Property URL e.g. "https://example.com"
- `startDate` (string, required): Start date YYYY-MM-DD

### `get_gsc_query_trend` (~128 tokens)

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.

Input parameters:

- `endDate` (string, required): End date YYYY-MM-DD
- `query` (string, required): Search query to track e.g. "best seo tools"
- `site` (string, required): Property URL e.g. "https://example.com"
- `startDate` (string, required): Start date YYYY-MM-DD

### `get_gsc_opportunity_queries` (~177 tokens)

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.

Input parameters:

- `endDate` (string, required): End date YYYY-MM-DD
- `maxPosition` (number): Maximum average position (default 20)
- `minPosition` (number): Minimum average position (default 8)
- `rowLimit` (number): Max rows (default 50, max 1000)
- `site` (string, required): Property URL e.g. "https://example.com"
- `startDate` (string, required): Start date YYYY-MM-DD

### `get_gsc_low_ctr_queries` (~192 tokens)

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.

Input parameters:

- `endDate` (string, required): End date YYYY-MM-DD
- `maxCtr` (number): Only include queries with CTR at or below this value 0–1 (default 0.05 = 5%)
- `minImpressions` (number): Only include queries with at least this many impressions (default 100)
- `rowLimit` (number): Max rows (default 50, max 1000)
- `site` (string, required): Property URL e.g. "https://example.com"
- `startDate` (string, required): Start date YYYY-MM-DD

### `get_gsc_low_ctr_pages` (~180 tokens)

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.

Input parameters:

- `endDate` (string, required): End date YYYY-MM-DD
- `maxCtr` (number): Only include pages with CTR at or below this value 0–1 (default 0.05 = 5%)
- `minImpressions` (number): Only include pages with at least this many impressions (default 500)
- `rowLimit` (number): Max rows (default 25, max 1000)
- `site` (string, required): Property URL e.g. "https://example.com"
- `startDate` (string, required): Start date YYYY-MM-DD

### `get_gsc_page_segment` (~163 tokens)

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.

Input parameters:

- `endDate` (string, required): End date YYYY-MM-DD
- `rowLimit` (number): Max rows (default 25, max 1000)
- `site` (string, required): Property URL e.g. "https://example.com"
- `startDate` (string, required): Start date YYYY-MM-DD
- `urlPattern` (string, required): URL substring to filter by e.g. "/blog/" or "/products/"

### `get_gsc_search_appearance` (~118 tokens)

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.

Input parameters:

- `endDate` (string, required): End date YYYY-MM-DD
- `site` (string, required): Property URL e.g. "https://example.com"
- `startDate` (string, required): Start date YYYY-MM-DD

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/abhibavishi-rankparse-mcp/mcp#diagnostics

## Score history

- 2026-08-03: 71
- 2026-08-02: 71
- 2026-08-01: 62
- 2026-07-31: 62
- 2026-07-30: 57
- 2026-07-29: 56
- 2026-07-28: 55
- 2026-07-27: 55
- 2026-07-26: 54

## Links

- Remote endpoint: https://mcp.rankparse.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/abhibavishi-rankparse-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/abhibavishi-rankparse-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/abhibavishi-rankparse-mcp/mcp