io.github.abhibavishi/rankparse-mcp
REMOTE · MCP.RANKPARSE.COM · SCANNED SEP 20
SEO MCP server — backlinks, domain authority, tech stack, and 18+ tools via Common Crawl.
Available components
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 7936 tokens (~108/item across 73 items; 73 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 77% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 73 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.abhibavishi/rankparse-mcp server?
io.github.abhibavishi/rankparse-mcp is a hosted endpoint at https://mcp.rankparse.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.rankparse.com
claude mcp add --transport http abhibavishi-rankparse-mcp 'https://mcp.rankparse.com/mcp'
{
"mcpServers": {
"abhibavishi-rankparse-mcp": {
"url": "https://mcp.rankparse.com/mcp"
}
}
} {
"servers": {
"abhibavishi-rankparse-mcp": {
"type": "http",
"url": "https://mcp.rankparse.com/mcp"
}
}
} [mcp_servers.abhibavishi-rankparse-mcp] url = "https://mcp.rankparse.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"abhibavishi-rankparse-mcp": {
"type": "remote",
"url": "https://mcp.rankparse.com/mcp",
"enabled": true
}
}
} openclaw mcp add abhibavishi-rankparse-mcp --url 'https://mcp.rankparse.com/mcp' --transport streamable-http
mcp_servers:
abhibavishi-rankparse-mcp:
url: "https://mcp.rankparse.com/mcp" {
"McpServers": {
"abhibavishi-rankparse-mcp": {
"Transport": "http",
"Url": "https://mcp.rankparse.com/mcp"
}
}
} assistant mcp add abhibavishi-rankparse-mcp -t streamable-http -u 'https://mcp.rankparse.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Sept 26 0
- Schema quality: 7136 → 7936 ▼ functional
- New tool “get_rank_alert_settings” functional
- New tool “list_rank_change_alerts” functional
- New tool “provision_indexnow_key” functional
- New tool “submit_indexnow_urls” functional
- New tool “update_rank_alert_settings” functional
- “get_keyword_rank_history” added an optional parameter “dimension” cosmetic
- 9 Sept 26 0
- Tool “get_schema_markup” rewrote its description, which is the text the model reads security
- 6 Sept 26 0
- Schema quality: pass → fail ▼ functional
- New tool “get_keyword_rank_history” functional
- New tool “get_keyword_rankings” functional
- New tool “list_rank_tracking_sites” functional
- New tool “list_tracked_keywords” functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Aug 26 82
- Tool “zeekeo_list_campaigns” rewrote its description, which is the text the model reads security
- Tool “zeekeo_send_message” rewrote its description, which is the text the model reads security
- Schema quality: 5604 → 6377 ▼ functional
- New tool “zeekeo_activate_campaign” functional
- New tool “zeekeo_create_campaign” functional
- New tool “zeekeo_create_template” functional
- 21 Aug 26 0
- New tool “zeekeo_list_campaigns” functional
- New tool “zeekeo_send_message” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.rankparse.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rankparse.com | CN=WE1,O=Google Trust Services,C=US | 21 Aug 2026 | 19 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 96fc8688c5ed8f931300de47a94dccef |
| SANs: rankparse.com, mcp.rankparse.com, *.mcp.rankparse.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.rankparse.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| rankparse.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.rankparse.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.rankparse.com/mcp | HTTPS enforced | 301 | https://mcp.rankparse.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
batch_lookup ~26
Get backlinks for up to 50 domains at once
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | – |
No output schema declared.
No examples provided.
check_credits ~14
Check remaining credit balance
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_anchor_text ~31
Get anchor text distribution for a domain
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
get_backlinks ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| from_domain | string | – | – |
| limit | number | – | – |
| link_type | string | – | – |
| score | boolean | – | – |
| sort | string | – | – |
No output schema declared.
No examples provided.
get_competitor_gap ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| limit | number | – | – |
| vs | string | yes | – |
No output schema declared.
No examples provided.
get_crawl_history ~37
Get first/last seen dates and total snapshot count for a domain (source: Wayback Machine)
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
get_domain_authority ~24
Get authority score for a domain
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
get_domain_overlap ~31
Find domains linking to all queried domains
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
get_domain_rank ~25
Get inbound edge count and linking domain stats
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
get_google_ads_accounts ~94
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_google_ads_keyword_ideas ~280
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.
| Name | Type | Req | Description |
|---|---|---|---|
| geo_target_constants | array | – | Location resource names, default ["geoTargetConstants/2840"] (United States). Max 10. |
| include_adult_keywords | boolean | – | Include adult keywords in results (default false) |
| keyword_plan_network | string | – | Search network to estimate against (default GOOGLE_SEARCH) |
| keywords | array | – | Seed keywords to expand from, e.g. ["seo tools", "backlink checker"]. Max 20; provide these and/or url. |
| language | string | – | Language resource name, default "languageConstants/1000" (English) |
| limit | number | – | Max ideas to return (default Google decides, max 1000) |
| url | string | – | A page or site URL to derive keyword ideas from, e.g. "https://example.com/pricing" |
No output schema declared.
No examples provided.
get_google_ads_keyword_metrics ~236
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.
| Name | Type | Req | Description |
|---|---|---|---|
| geo_target_constants | array | – | Location resource names, default ["geoTargetConstants/2840"] (United States). Max 10. |
| keyword_plan_network | string | – | Search network to estimate against (default GOOGLE_SEARCH) |
| keywords | array | yes | The exact keywords to look up, e.g. ["seo api", "rank tracker"]. Max 200 per call; extras are dropped and reported via the "truncated" flag. |
| language | string | – | Language resource name, default "languageConstants/1000" (English) |
No output schema declared.
No examples provided.
get_gsc_country_breakdown ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| rowLimit | number | – | Max rows (default 25, max 1000) |
| site | string | yes | Property URL e.g. "https://example.com" |
| startDate | string | yes | Start date YYYY-MM-DD |
No output schema declared.
No examples provided.
get_gsc_date_trends ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| site | string | yes | Property URL e.g. "https://example.com" |
| startDate | string | yes | Start date YYYY-MM-DD |
No output schema declared.
No examples provided.
get_gsc_device_breakdown ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| site | string | yes | Property URL e.g. "https://example.com" |
| startDate | string | yes | Start date YYYY-MM-DD |
No output schema declared.
No examples provided.
get_gsc_low_ctr_pages ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | 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 | yes | Property URL e.g. "https://example.com" |
| startDate | string | yes | Start date YYYY-MM-DD |
No output schema declared.
No examples provided.
get_gsc_low_ctr_queries ~192
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | 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 | yes | Property URL e.g. "https://example.com" |
| startDate | string | yes | Start date YYYY-MM-DD |
No output schema declared.
No examples provided.
get_gsc_opportunity_queries ~176
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | 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 | yes | Property URL e.g. "https://example.com" |
| startDate | string | yes | Start date YYYY-MM-DD |
No output schema declared.
No examples provided.
get_gsc_page_queries ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| page | string | yes | Full page URL e.g. "https://example.com/blog/post" |
| rowLimit | number | – | Max rows (default 25, max 1000) |
| site | string | yes | Property URL e.g. "https://example.com" |
| startDate | string | yes | Start date YYYY-MM-DD |
No output schema declared.
No examples provided.
get_gsc_page_segment ~163
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| rowLimit | number | – | Max rows (default 25, max 1000) |
| site | string | yes | Property URL e.g. "https://example.com" |
| startDate | string | yes | Start date YYYY-MM-DD |
| urlPattern | string | yes | URL substring to filter by e.g. "/blog/" or "/products/" |
No output schema declared.
No examples provided.
get_gsc_page_trend ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| page | string | yes | Full page URL e.g. "https://example.com/blog/post" |
| site | string | yes | Property URL e.g. "https://example.com" |
| startDate | string | yes | Start date YYYY-MM-DD |
No output schema declared.
No examples provided.
get_gsc_properties ~47
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_gsc_query_page_pairs ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| rowLimit | number | – | Max rows (default 100, max 1000) |
| site | string | yes | Property URL e.g. "https://example.com" |
| startDate | string | yes | Start date YYYY-MM-DD |
No output schema declared.
No examples provided.
get_gsc_query_pages ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| query | string | yes | Search query to look up e.g. "best seo tools" |
| rowLimit | number | – | Max rows (default 25, max 1000) |
| site | string | yes | Property URL e.g. "https://example.com" |
| startDate | string | yes | Start date YYYY-MM-DD |
No output schema declared.
No examples provided.
get_gsc_query_trend ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| query | string | yes | Search query to track e.g. "best seo tools" |
| site | string | yes | Property URL e.g. "https://example.com" |
| startDate | string | yes | Start date YYYY-MM-DD |
No output schema declared.
No examples provided.
get_gsc_search_appearance ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| site | string | yes | Property URL e.g. "https://example.com" |
| startDate | string | yes | Start date YYYY-MM-DD |
No output schema declared.
No examples provided.
get_gsc_sitemaps ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | Property URL e.g. "https://example.com" |
No output schema declared.
No examples provided.
get_gsc_top_pages ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| rowLimit | number | – | Max rows (default 25, max 1000) |
| site | string | yes | Property URL e.g. "https://example.com" |
| startDate | string | yes | Start date YYYY-MM-DD |
No output schema declared.
No examples provided.
get_gsc_top_queries ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| rowLimit | number | – | Max rows (default 25, max 1000) |
| site | string | yes | Property URL e.g. "https://example.com" or "sc-domain:example.com" |
| startDate | string | yes | Start date YYYY-MM-DD |
No output schema declared.
No examples provided.
get_gsc_url_inspection ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | Property URL e.g. "https://example.com" |
| url | string | yes | Full URL to inspect e.g. "https://example.com/blog/post" |
No output schema declared.
No examples provided.
get_internal_links ~35
Get internal link structure for a domain (v1 stub)
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
get_keyword_rank_history ~331
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dimension | string | – | Breakdown of the daily rows. Default "total" is one row per day; "device" is one row per day per device (desktop/mobile/tablet) with a device field on each row. Device rows exist only where the provi… |
| end_date | string | yes | End of the range, inclusive, as YYYY-MM-DD |
| engine | string | yes | Search engine to get history for (required -- history is always single-engine) |
| keyword_id | string | yes | Tracked keyword ID, from list_tracked_keywords |
| site_id | string | yes | Logical RankParse website ID, from list_rank_tracking_sites |
| start_date | string | yes | Start of the range, inclusive, as YYYY-MM-DD |
No output schema declared.
No examples provided.
get_keyword_rankings ~369
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.
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | Search engine to report on. Defaults to "all" (every engine enabled for this account) -- the primary use case is comparing engines side by side, so leave this unset unless you need one engine only. |
| keyword_id | string | – | Restrict to one tracked keyword ID, from list_tracked_keywords. Omit to get all keywords for the site. |
| limit | integer | – | Max keywords to return (default 100, max 100) |
| offset | integer | – | Pagination offset (default 0) |
| period_days | integer | – | Length of the current/previous comparison window in days (default 28, max 90) |
| site_id | string | yes | Logical RankParse website ID, from list_rank_tracking_sites |
No output schema declared.
No examples provided.
get_link_audit ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
get_link_intersect ~35
Find domains linking to A but not B
| Name | Type | Req | Description |
|---|---|---|---|
| domain_a | string | yes | – |
| domain_b | string | yes | – |
No output schema declared.
No examples provided.
get_link_velocity ~30
Get rate of new/lost links over time (v1 stub)
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
get_lost_links ~28
Get links lost since previous crawl (v1 stub)
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
get_new_links ~27
Get links gained since previous crawl (v1 stub)
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
get_outbound_links ~33
Get domains that a domain links out to
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
get_page_performance ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| strategy | string | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
get_page_seo ~64
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
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
get_platform_domains ~185
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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") |
No output schema declared.
No examples provided.
get_platform_trends ~43
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)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_rank_alert_settings ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| site_id | string | yes | Logical RankParse website ID, from list_rank_tracking_sites |
No output schema declared.
No examples provided.
get_referring_domains ~39
Get unique domains linking to a domain
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| limit | number | – | – |
| score | boolean | – | – |
No output schema declared.
No examples provided.
get_schema_markup ~47
Extract schema.org JSON-LD structured data from a URL: every entity found (including ones nested in @graph), their types, and any malformed blocks
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
get_similar_domains ~42
Find domains with similar link profiles, useful for competitor discovery. May return partial results when the query fan-out hits time budget.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
get_site_explorer ~35
Full SEO overview for a domain (backlinks, authority, top pages, anchor text)
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
get_site_health ~58
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
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
get_sitemap ~43
Discover and parse a domain's sitemap. Returns URLs with lastmod, changefreq, and priority
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
What is the io.github.abhibavishi/rankparse-mcp server?
io.github.abhibavishi/rankparse-mcp is listed in the public MCP registry as io.github.abhibavishi/rankparse-mcp. SEO MCP server, backlinks, domain authority, tech stack, and 18+ tools via Common Crawl. This page covers its hosted endpoint (https://mcp.rankparse.com/mcp).
Is the io.github.abhibavishi/rankparse-mcp server safe to use?
io.github.abhibavishi/rankparse-mcp scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.abhibavishi/rankparse-mcp server expose?
io.github.abhibavishi/rankparse-mcp exposes 73 tools: get_backlinks, get_referring_domains, get_outbound_links, get_domain_authority, get_domain_rank, and 68 more. Their descriptions and schemas cost roughly 7,936 tokens of context every time the server is loaded.
Does the io.github.abhibavishi/rankparse-mcp server require authentication?
No. We connected to io.github.abhibavishi/rankparse-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.abhibavishi/rankparse-mcp server still maintained?
io.github.abhibavishi/rankparse-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.