← Registry

Analytics

ranksage.com

Provides SEO analytics and insights from RankSage, including traffic, keyword movement, AI visibility scores, and content/competitor gap analysis.

2 endpoints32 known toolsFirst detected September 9, 2026Last detected September 9, 2026

ENDPOINT 1

https://www.ranksage.com/.well-known/mcp

No auth detected

MCP server metadata

Name
ranksage
Version
1.2.0
Capabilities
tools.listChanged
Server instructions

RankSage exposes read-only SEO, AEO and AI-visibility data for an authenticated account. You are connected anonymously: tools are listed for discovery, but every call requires a Bearer credential — an OAuth access token with the `mcp` scope (discovery via /.well-known/oauth-authorization-server on this origin, PKCE + dynamic client registration) or a RankSage personal access token.

Known tools 16

check_connection

Confirm the RankSage MCP credential is valid and learn its expiry, scopes and the per-call time budget.

Inferred read-only
get_digest

Returns the RankSage digest for the authenticated account: per-website traffic, keyword movement, AI visibility scores and alerts for the requested period.

Inferred read-only
get_visibility_summary

Returns AI share-of-voice for the authenticated account plus a per-engine breakdown of mention rate, citation rate, grounded rate and 95% confidence bands.

Inferred read-only
get_gap_counts

Returns aggregate content and competitor gap counts for the authenticated account, broken down by lens, status, severity and type.

Inferred read-only
list_gaps

Lists content or competitor gaps for the authenticated account, highest impact first.

Inferred read-only
list_action_queue

Returns the ranked RankSage action queue for the authenticated account — the prioritised list of recommended next actions across all data sources.

Inferred read-only
get_traffic_summary

Returns blended traffic for the authenticated account across all connected analytics sources (GA4, first-party, Vercel, PostHog, Amplitude, Mixpanel) for a date window.

Inferred read-only
get_ai_performance

Returns the AI Performance rollup for the authenticated account: AI Traffic Value (a quality-weighted composite, NOT a session count), confirmed AI referral sessions (measured in GA4), the estimated total AI influence with its low–high range and confidence percentage (modelled, not measured), and the AI agents detected on the site by the RankSage tracking script.

Inferred read-only
get_visibility_detail

Returns one detail view of the authenticated account’s AI visibility surface: `prompts` (the prompt library with per-prompt mention confidence bands), `runs` (run history — one row per visibility run), `serp` (latest SERP feature capture per tracked keyword), `carousel` (AIO carousel inclusion), `volatility` (per-keyword citation stability) or `citation_delta` (persisted competitor citation profiles).

Inferred read-only
get_search_analytics

Returns one classic-search view for the authenticated account: `top_pages` (GA4 page performance vs the prior window), `keywords` (tracked keyword ranks PLUS Google Search Console query rows — clicks, impressions, CTR, position), `domain_authority` (DataForSEO backlink profile for the account’s own registered domain), `site_audit` (recent audit runs) or `pagespeed` (window-averaged Lighthouse performance scores).

Inferred read-only
get_content_report

Returns one of the RankSage Content analysis views for the authenticated account.

Inferred read-only
get_content_production

Returns the RankSage content production pipeline for the authenticated account.

Inferred read-only
get_competitor_report

Competitive intelligence for the authenticated account.

Inferred read-only
get_community_report

Community and off-site brand presence for the authenticated account.

Inferred read-only
get_behavior_report

First-party visitor and crawler behaviour for the authenticated account.

Inferred read-only
get_site_readiness

Machine-readability readiness for the authenticated account's OWN site.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.ranksage]
url = "https://www.ranksage.com/.well-known/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "ranksage": {
      "type": "http",
      "url": "https://www.ranksage.com/.well-known/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: ranksage
Remote MCP URL: https://www.ranksage.com/.well-known/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "ranksage": {
      "url": "https://www.ranksage.com/.well-known/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "ranksage": {
      "type": "http",
      "url": "https://www.ranksage.com/.well-known/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "ranksage",
  "transport": "streamable-http",
  "url": "https://www.ranksage.com/.well-known/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://api.ranksage.com/api/v1/mcp

No auth detected

MCP server metadata

Name
ranksage
Version
1.2.0
Capabilities
tools.listChanged
Server instructions

RankSage exposes read-only SEO, AEO and AI-visibility data for an authenticated account. You are connected anonymously: tools are listed for discovery, but every call requires a Bearer credential — an OAuth access token with the `mcp` scope (discovery via /.well-known/oauth-authorization-server on this origin, PKCE + dynamic client registration) or a RankSage personal access token.

Known tools 16

check_connection

Confirm the RankSage MCP credential is valid and learn its expiry, scopes and the per-call time budget.

Inferred read-only
get_digest

Returns the RankSage digest for the authenticated account: per-website traffic, keyword movement, AI visibility scores and alerts for the requested period.

Inferred read-only
get_visibility_summary

Returns AI share-of-voice for the authenticated account plus a per-engine breakdown of mention rate, citation rate, grounded rate and 95% confidence bands.

Inferred read-only
get_gap_counts

Returns aggregate content and competitor gap counts for the authenticated account, broken down by lens, status, severity and type.

Inferred read-only
list_gaps

Lists content or competitor gaps for the authenticated account, highest impact first.

Inferred read-only
list_action_queue

Returns the ranked RankSage action queue for the authenticated account — the prioritised list of recommended next actions across all data sources.

Inferred read-only
get_traffic_summary

Returns blended traffic for the authenticated account across all connected analytics sources (GA4, first-party, Vercel, PostHog, Amplitude, Mixpanel) for a date window.

Inferred read-only
get_ai_performance

Returns the AI Performance rollup for the authenticated account: AI Traffic Value (a quality-weighted composite, NOT a session count), confirmed AI referral sessions (measured in GA4), the estimated total AI influence with its low–high range and confidence percentage (modelled, not measured), and the AI agents detected on the site by the RankSage tracking script.

Inferred read-only
get_visibility_detail

Returns one detail view of the authenticated account’s AI visibility surface: `prompts` (the prompt library with per-prompt mention confidence bands), `runs` (run history — one row per visibility run), `serp` (latest SERP feature capture per tracked keyword), `carousel` (AIO carousel inclusion), `volatility` (per-keyword citation stability) or `citation_delta` (persisted competitor citation profiles).

Inferred read-only
get_search_analytics

Returns one classic-search view for the authenticated account: `top_pages` (GA4 page performance vs the prior window), `keywords` (tracked keyword ranks PLUS Google Search Console query rows — clicks, impressions, CTR, position), `domain_authority` (DataForSEO backlink profile for the account’s own registered domain), `site_audit` (recent audit runs) or `pagespeed` (window-averaged Lighthouse performance scores).

Inferred read-only
get_content_report

Returns one of the RankSage Content analysis views for the authenticated account.

Inferred read-only
get_content_production

Returns the RankSage content production pipeline for the authenticated account.

Inferred read-only
get_competitor_report

Competitive intelligence for the authenticated account.

Inferred read-only
get_community_report

Community and off-site brand presence for the authenticated account.

Inferred read-only
get_behavior_report

First-party visitor and crawler behaviour for the authenticated account.

Inferred read-only
get_site_readiness

Machine-readability readiness for the authenticated account's OWN site.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.ranksage]
url = "https://api.ranksage.com/api/v1/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "ranksage": {
      "type": "http",
      "url": "https://api.ranksage.com/api/v1/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: ranksage
Remote MCP URL: https://api.ranksage.com/api/v1/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "ranksage": {
      "url": "https://api.ranksage.com/api/v1/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "ranksage": {
      "type": "http",
      "url": "https://api.ranksage.com/api/v1/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "ranksage",
  "transport": "streamable-http",
  "url": "https://api.ranksage.com/api/v1/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.