io.github.abhibavishi/rankparse-mcp
REMOTE · MCP.RANKPARSE.COM
SEO MCP server — backlinks, domain authority, tech stack, and 18+ tools via Common Crawl.
Available components
Last scanned (3 hours ago)
Scores higher than 28% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Security95
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 5 Nov 26 −46
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: partial → pass ▲ security
- First check of Authorization: pass security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 29 Oct 26 −1
- Tool “get_ai_visibility” rewrote its description, which is the text the model reads security
- Tool “recheck_ai_visibility” rewrote its description, which is the text the model reads security
- Schema quality: 10553 → 11730 ▼ functional
- New tool “get_indexing_status” functional
- New tool “list_site_issues” functional
- “get_gsc_top_queries” added an optional parameter “searchType” cosmetic
- “get_gsc_country_breakdown” added an optional parameter “searchType” cosmetic
- “get_gsc_date_trends” added an optional parameter “searchType” cosmetic
- “get_gsc_device_breakdown” added an optional parameter “searchType” cosmetic
- “get_gsc_low_ctr_pages” added an optional parameter “searchType” cosmetic
- “get_gsc_low_ctr_queries” added an optional parameter “searchType” cosmetic
- “get_gsc_opportunity_queries” added an optional parameter “searchType” cosmetic
- “get_gsc_page_queries” added an optional parameter “searchType” cosmetic
- “get_gsc_page_segment” added an optional parameter “searchType” cosmetic
- “get_gsc_page_trend” added an optional parameter “searchType” cosmetic
- “get_gsc_query_page_pairs” added an optional parameter “searchType” cosmetic
- “get_gsc_query_pages” added an optional parameter “searchType” cosmetic
- “get_gsc_query_trend” added an optional parameter “searchType” cosmetic
- “get_gsc_search_appearance” added an optional parameter “searchType” cosmetic
- “get_gsc_top_pages” added an optional parameter “searchType” cosmetic
- 26 Oct 26 +2
- DNSSEC: fail → pass ▲ security
- New tool “get_ai_visibility” functional
- New tool “recheck_ai_visibility” functional
- 23 Oct 26 0
- Tool “outreach_add_contacts” rewrote its description, which is the text the model reads security
- Tool “outreach_create_campaign” rewrote its description, which is the text the model reads security
- New tool “outreach_update_contacts” functional
- 22 Oct 26 −1
- Tool “outreach_configure_sending” rewrote its description, which is the text the model reads security
- Tool “outreach_sending_status” rewrote its description, which is the text the model reads security
- “outreach_configure_sending” added an optional parameter “mailbox_id” cosmetic
- “outreach_sending_status” added an optional parameter “mailbox_id” cosmetic
- “outreach_configure_sending” reworded the description of “auto_send_enabled” cosmetic
- “outreach_configure_sending” reworded the description of “max_sends_per_day” cosmetic
- 21 Oct 26 0
- Tool “outreach_create_campaign” rewrote its description, which is the text the model reads security
- Tool “outreach_launch_campaign” rewrote its description, which is the text the model reads security
- Tool “propose_outreach_send” rewrote its description, which is the text the model reads security
- 3 Oct 26 84
- Tool “get_domain_authority” rewrote its description, which is the text the model reads security
- Tool “get_gsc_country_breakdown” rewrote its description, which is the text the model reads security
- Tool “get_gsc_date_trends” rewrote its description, which is the text the model reads security
- Tool “get_gsc_device_breakdown” rewrote its description, which is the text the model reads security
- Tool “get_gsc_low_ctr_pages” rewrote its description, which is the text the model reads security
- Tool “get_gsc_low_ctr_queries” rewrote its description, which is the text the model reads security
- Tool “get_gsc_opportunity_queries” rewrote its description, which is the text the model reads security
- Tool “get_gsc_page_queries” rewrote its description, which is the text the model reads security
- Tool “get_gsc_page_segment” rewrote its description, which is the text the model reads security
- Tool “get_gsc_page_trend” rewrote its description, which is the text the model reads security
- Tool “get_gsc_properties” rewrote its description, which is the text the model reads security
- Tool “get_gsc_query_page_pairs” rewrote its description, which is the text the model reads security
- Tool “get_gsc_query_pages” rewrote its description, which is the text the model reads security
- Tool “get_gsc_query_trend” rewrote its description, which is the text the model reads security
- Tool “get_gsc_search_appearance” rewrote its description, which is the text the model reads security
- Tool “get_gsc_sitemaps” rewrote its description, which is the text the model reads security
- Tool “get_gsc_top_pages” rewrote its description, which is the text the model reads security
- Tool “get_gsc_top_queries” rewrote its description, which is the text the model reads security
- Tool “get_gsc_url_inspection” rewrote its description, which is the text the model reads security
- Tool “outreach_configure_sending” rewrote its description, which is the text the model reads security
- Tool “outreach_create_campaign” rewrote its description, which is the text the model reads security
- Tool “outreach_launch_campaign” rewrote its description, which is the text the model reads security
- Tool “outreach_list_campaigns” rewrote its description, which is the text the model reads security
- Schema quality: 7956 → 9512 ▼ functional
- New tool “complete_agent_task” functional
- New tool “get_agent_tasks” functional
- New tool “list_proposals” functional
- New tool “list_websites” functional
- New tool “log_activity” functional
- New tool “propose_indexnow_submit” functional
- New tool “propose_outreach_send” functional
- “outreach_create_campaign” added an optional parameter “site_id” cosmetic
- “outreach_list_campaigns” added an optional parameter “site_id” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 5 Nov 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 | 19 Oct 2026 | 17 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b7c251857f7150da135329fb45233387 |
| 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 secure
Validation of mcp.rankparse.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| rankparse.com. | present | 2371 | 13 | Verified |
| mcp.rankparse.com. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.rankparse.com/.well-known/oauth-protected-resource/mcp", scope="seo:read account:read workspace:read workspace:write offline_access"
Bearer resource_metadata="https://mcp.rankparse.com/.well-known/oauth-protected-resource/mcp", scope="seo:read account:read workspace:read workspace:write offline_access"| Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://mcp.rankparse.com/.well-known/oauth-protected-resource/mcp", scope="seo:read account:read workspace:read workspace:write offline_access" |
Protected resource metadata
| Document | https://mcp.rankparse.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.rankparse.com/mcp |
| Authorisation server | https://connect.rankparse.com |
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 | Auth required | 401 | |
| 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.
complete_agent_task ~58
Mark a queued task done with a plain-text summary (max 2000 characters) of what you found and what you did. The user sees it in RankParse.
| Name | Type | Req | Description |
|---|---|---|---|
| summary | string | yes | – |
| task_id | string | yes | – |
No output schema declared.
No examples provided.
get_agent_tasks ~74
Get tasks the user queued for you in RankParse. At the start of any RankParse session, call get_agent_tasks to see work the user queued for you. Work on a task, then call complete_agent_task with a short plain-text summary.
| Name | Type | Req | Description |
|---|---|---|---|
| site_id | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
get_ai_visibility ~370
Get the stored AI visibility (agent readiness / AEO) scan for one RankParse website: whether AI search and answer agents (OAI-SearchBot, ChatGPT-User, PerplexityBot, Claude-SearchBot and others) may crawl it, whether AI training crawlers are blocked, robots.txt, sitemap, llms.txt, Markdown content negotiation (Accept: text/markdown) and JSON-LD structured data, plus optional agent protocol features (Link header, Content Signals in robots.txt, Web Bot Auth, API catalog, OAuth discovery and protected resource metadata, MCP server card, agent skills index, A2A agent card, auth.md, DNS-AID agent index), classic site health checks (category "site_health": HTTPS redirect, HSTS, home page noindex, canonical on another host, missing title or meta description), and a score per area (the overall score is AI visibility only; site health has its own area score). Reads the daily background scan; it is not a live fetch (use recheck_ai_visibility to queue one). status "unknown" means the check could not tell (timeout, server error), not that it failed. Checks with optional: true (severity "info") are left out of the score and are never problems on their own: most websites need no MCP server card or API catalog, and blocking training crawlers is often a deliberate choice, so never present them as failures without saying so. Only websites verified through Google Search Console or Bing Webmaster Tools, in workspaces on a paid plan (Pro, Agency, Lifetime), are scanned; others answer eligible: false with reason not_verified or plan_required. 0 credits.
| Name | Type | Req | Description |
|---|---|---|---|
| site_id | string | yes | Logical RankParse website ID, from list_rank_tracking_sites or list_websites |
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 ~68
Get authority score for a domain. If the response has partial=true the lookup timed out or was incomplete: a null score means the authority is unknown (not zero) and the credit was refunded, so retry rather than treating the domain as having no authority.
| 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 ~165
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. When several Google accounts are connected, the property is read through the account that can see it.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| rowLimit | number | – | Max rows (default 25, max 1000) |
| searchType | string | – | Search type (default web). Google does not offer every dimension for discover and googleNews (query is not available there). |
| 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 ~162
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. When several Google accounts are connected, the property is read through the account that can see it.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| searchType | string | – | Search type (default web). Google does not offer every dimension for discover and googleNews (query is not available there). |
| 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 ~143
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. When several Google accounts are connected, the property is read through the account that can see it.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| searchType | string | – | Search type (default web). Google does not offer every dimension for discover and googleNews (query is not available there). |
| 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 ~230
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. When several Google accounts are connected, the property is read through the account that can see 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) |
| searchType | string | – | Search type (default web). Google does not offer every dimension for discover and googleNews (query is not available there). |
| 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 ~242
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. When several Google accounts are connected, the property is read through the account that can see 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) |
| searchType | string | – | Search type (default web). Google does not offer every dimension for discover and googleNews (query is not available there). |
| 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 ~226
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. When several Google accounts are connected, the property is read through the account that can see 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) |
| searchType | string | – | Search type (default web). Google does not offer every dimension for discover and googleNews (query is not available there). |
| 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 ~185
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. When several Google accounts are connected, the property is read through the account that can see 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) |
| searchType | string | – | Search type (default web). Google does not offer every dimension for discover and googleNews (query is not available there). |
| 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 ~213
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. When several Google accounts are connected, the property is read through the account that can see it.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| rowLimit | number | – | Max rows (default 25, max 1000) |
| searchType | string | – | Search type (default web). Google does not offer every dimension for discover and googleNews (query is not available there). |
| 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 ~194
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. When several Google accounts are connected, the property is read through the account that can see 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" |
| searchType | string | – | Search type (default web). Google does not offer every dimension for discover and googleNews (query is not available there). |
| 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 ~66
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. When several Google accounts are connected, the properties visible to any of them are listed once each.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_gsc_query_page_pairs ~184
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. When several Google accounts are connected, the property is read through the account that can see it.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| rowLimit | number | – | Max rows (default 100, max 1000) |
| searchType | string | – | Search type (default web). Google does not offer every dimension for discover and googleNews (query is not available there). |
| 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 ~187
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. When several Google accounts are connected, the property is read through the account that can see 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) |
| searchType | string | – | Search type (default web). Google does not offer every dimension for discover and googleNews (query is not available there). |
| 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 ~178
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. When several Google accounts are connected, the property is read through the account that can see 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" |
| searchType | string | – | Search type (default web). Google does not offer every dimension for discover and googleNews (query is not available there). |
| 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 ~168
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. When several Google accounts are connected, the property is read through the account that can see it.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| searchType | string | – | Search type (default web). Google does not offer every dimension for discover and googleNews (query is not available there). |
| 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 ~98
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. When several Google accounts are connected, the property is read through the account that can see 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 ~168
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. When several Google accounts are connected, the property is read through the account that can see it.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| rowLimit | number | – | Max rows (default 25, max 1000) |
| searchType | string | – | Search type (default web). Google does not offer every dimension for discover and googleNews (query is not available there). |
| 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 ~183
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. When several Google accounts are connected, the property is read through the account that can see it.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date YYYY-MM-DD |
| rowLimit | number | – | Max rows (default 25, max 1000) |
| searchType | string | – | Search type (default web). Google does not offer every dimension for discover and googleNews (query is not available there). |
| 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 ~125
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. When several Google accounts are connected, the property is read through the account that can see 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_indexing_status ~265
Get the Google index status of the pages tracked on a website's Indexing page in RankParse: for each page, the last stored Google URL Inspection result (verdict PASS, PARTIAL, FAIL or NEUTRAL, coverage_state such as "Crawled - currently not indexed", robots.txt state, indexing state, page fetch state, last crawl time, Google-selected canonical, any inspection error) and when it was last submitted to IndexNow, plus a summary count of indexed, not indexed and unchecked pages. Pages are re-inspected by a background job about once a day; google_inspection_available false means no verified Google property covers the website, so pages are never inspected. Not-indexed pages come first. Use get_gsc_url_inspection for a live inspection of one URL. 0 credits.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max pages (default 100, max 500) |
| offset | integer | – | Pages to skip, for paging |
| site_id | string | yes | Logical RankParse website ID, from list_websites or list_rank_tracking_sites |
| status | string | – | Filter: not_indexed (inspected, verdict not PASS), unchecked (no verdict yet), indexed (PASS), error (last inspection failed). Default all. |
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 ~87
Get the rank-change alert configuration for one RankParse website: whether weekly alert digests are enabled (they are opt-in and default off), the moved_up/moved_down position threshold, and the optional digest email override. Delivery is Sunday at 18:00 UTC when meaningful changes exist.
| 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.
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'
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 38 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 85 tools: get_backlinks, get_referring_domains, get_outbound_links, get_domain_authority, get_domain_rank, and 80 more. Their descriptions and schemas cost roughly 11,730 tokens of context every time the server is loaded.
Does the io.github.abhibavishi/rankparse-mcp server require authentication?
Yes. io.github.abhibavishi/rankparse-mcp asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.