Analytics

revenuescope.jp

Provides analytics on website performance, including revenue, engagement, keyword performance, and AI traffic.

1 endpoint10 known toolsFirst detected July 25, 2026Last detected July 25, 2026

ENDPOINT 1

https://mcp.revenuescope.jp/api/mcp

No auth detected

MCP server metadata

Name: revenuescope-mcp
Version: 1.9.1

Capabilities

tools.listChanged

Known tools 10

list_sites

List the sites this caller can analyze, in two groups.

Inferred read-only

get_summary

Return the full headline summary for a site and period in ONE call: the 5 KPIs (revenue, sessions, RPS, AOV, CVR) PLUS two engagement KPIs (avg_duration = average dwell time in seconds, bounce_rate = % single-page-exit sessions) each with value AND the period-over-period change vs the previous equal-length window, PLUS a daily revenue/sessions/conversions trend, PLUS ad-spend availability (connected_channels, ad_spend_data_status, ad_spend_channels_in_period) and the Path A/B recommendation.

Inferred read-only

get_breakdown

Consolidated breakdown tool.

Inferred read-only

get_keyword_performance

Return search-query performance from Google Search Console for the given period.

Inferred read-only

get_ai_traffic

Return AI-assistant (ChatGPT/Claude/Perplexity/Gemini/Copilot) traffic for the given period.

Inferred read-only

get_priority_insights

Return the top 3 prioritized, pre-computed DIAGNOSES for the site over the given period — 'what should I act on this week', ranked by revenue impact.

Inferred read-only

suggest_budget_allocation

Return a proposed monthly budget split across paid ad channels (Google Ads / Meta / TikTok Ads / Yahoo!

Inferred read-only

get_page_trend

Return how ONE page's Google Search performance changed over time (FD-040) — the time-axis drill-down for a page surfaced by get_breakdown(dimension='page').

Inferred read-only

get_content_actions

Return a content 'playbook' for the site: every content page classified into ONE of five action buckets over a weekly-style window comparison (current window vs the immediately preceding window of equal length), ranked by search-opportunity × session gain so you can tell the user which page to GROW next and what to do: within the 'striking' bucket rows are ordered by expected_sessions_gain DESC (the band-CTR headroom that is the actionable lever there), while the other buckets keep real landing revenue DESC (largest revenue at stake first).

Inferred read-only

get_competitor_keywords

Return the latest competitor SEO snapshot for the site (FD-041): which keywords each tracked competitor DOMAIN ranks for on Google (Japan/ja), at what position, with monthly search_volume, cpc and etv (estimated monthly traffic — a visit estimate, not a monetary value), plus how each rank moved vs the previous snapshot.

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.revenuescope-mcp]
url = "https://mcp.revenuescope.jp/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "revenuescope-mcp": {
      "type": "http",
      "url": "https://mcp.revenuescope.jp/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: revenuescope-mcp
Remote MCP URL: https://mcp.revenuescope.jp/api/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": {
    "revenuescope-mcp": {
      "url": "https://mcp.revenuescope.jp/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "revenuescope-mcp": {
      "type": "http",
      "url": "https://mcp.revenuescope.jp/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "revenuescope-mcp",
  "transport": "streamable-http",
  "url": "https://mcp.revenuescope.jp/api/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.