mcpbeat Sign in

RevenueScope: revenue-first analytics for your EC site MCP Server

by toshihiroshishido Your server? Claim it
not responding

RevenueScope: revenue-first analytics for your EC site is listed as active in the registry but did not answer our last check. It exposes 12 tools.

Ask AI about your EC site's revenue by channel, RPS/AOV/CVR, search & AI traffic, budget split.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 91 days of history · worst day 0%
91 days agonow
0.0%
Uptime 24h
0 of 92 checks
12
Tools
read from the server
78 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 56

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 16 August 2026. No other catalogue keeps this.

9 Oct 3 tool descriptions were rewritten get_breakdown, get_summary, suggest_budget_allocation
9 Oct a tool changed version
29 Sep 8 tool descriptions were rewritten get_ai_traffic, get_breakdown, get_content_actions and 5 more
29 Sep 8 tools changed the parameters they ask for get_ai_traffic, get_breakdown, get_content_actions and 5 more
28 Sep 7 tool descriptions were rewritten8 times that day get_ai_traffic, get_breakdown, get_content_actions and 4 more
28 Sep 4 tools changed the parameters they ask for get_ai_traffic, get_breakdown, get_priority_insights and 1 more
28 Sep 2 tools appeared get_metadata, get_today
26 Sep 2 tool descriptions were rewritten get_breakdown, get_summary
26 Sep 2 tools changed the parameters they ask for get_breakdown, get_summary
6 Sep a tool description was rewritten get_breakdown
and 18 more, back to 16 August 2026

RevenueScope: revenue-first analytics for your EC site does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add revenuescope-mcp --transport http https://mcp.revenuescope.jp/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.revenuescope.jp/api/mcp
~/.codex/config.toml
[mcp_servers.revenuescope-mcp]
url = "https://mcp.revenuescope.jp/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "revenuescope-mcp": {
      "url": "https://mcp.revenuescope.jp/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "revenuescope-mcp": {
      "type": "http",
      "url": "https://mcp.revenuescope.jp/api/mcp"
    }
  }
}

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

breakdown
get_breakdown
`get_breakdown` compares channel, entry_page, visitor_history, page and session_attribute rows. By default it uses the site's calendar month to date and compares with the prior month through the same calendar day (clamped to the prior month's last day). Pass start_date and end_date together for another inclusive calendar range in the site's analysis timezone; optionally pass compare_start_date and compare_end_date. Without explicit comparison dates it uses the immediately preceding equal-length range. Each row reports available prior values and deltas. Channel attribution_model supports last_touch, first_touch, linear and time_decay. Candidate ad revenue is not paid attribution. ad_spend_candidates returns ROAS (candidate revenue / ad spend) only for ad-only platforms (Google Ads, Yahoo! Ads, Microsoft Ads, Criteo, RTB House, MicroAd); others such as Meta include organic traffic and get roas_status=includes_organic. Monthly ad spend is prorated by overlapping days. No overall ROAS. Unattributed purchase revenue is a separate row. Some dimensions do not support country/device filters; unsupported axes are identified in notes. site_id is optional when OAuth-authenticated.
competitor
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. READ-ONLY — this tool never runs a research (that costs money and is triggered separately from the dashboard, the competitor-research Edge Function); it only reads what was already fetched. The response is summary-first (token-aware): each domain carries a constant-size `summary` (total_keywords, total_etv, volume_bands and rank_bands histograms, and vs_previous new/lost/improved/declined/same counts) that always reflects the FULL keyword set, while `keywords` returns only the top rows ranked by `sort` (etv default | volume | rank; default limit 10 per domain, max 100) with a `truncated` block (shown/matching_total/lost_total). rank is a POSITION: smaller is better, so a NEGATIVE rank_delta means the competitor's ranking IMPROVED (change ∈ new/improved/declined/same/unknown). Keywords the competitor ranked for before but lost are disclosed in `lost_keywords` (top 10 by previous etv), never dropped silently. Pass `domain` to focus one competitor, `min_volume` to drop low-volume keywords. When the site has NO completed research yet the response is { researched:false } with a `guidance` string explaining a research must be triggered from the dashboard first — this tool cannot start one. site_id is OPTIONAL when OAuth-authenticated. This is the external competitor lens (third-party SERP data); for YOUR OWN search performance use get_keyword_performance, and for your content playbook use get_content_actions.
content
get_content_actions
Return content action buckets and page evidence. By default the window length is N=7 days and GSC data is delayed by 3 days. To choose a window, pass start_date and end_date together: end_date must be today's date in Japan time, and N is end_date minus start_date (2-365 days; e.g. September 21 through September 28 sets N=7), so the pair describes a length ending today rather than the GSC source dates. The response separates `window` (actual JST GSC dates, inclusive) from `session_window` (sessions, revenue and AI metrics over N×24 hours ending at database statement time). `session_window` gives the relative start/end and duration; exact timestamps are unavailable because the RPC does not return its `now()` value. Search classifications, thresholds, bucket_summary, row prioritization, caveats and limits are included in the response. site_id is optional when OAuth-authenticated. Google Search only; data lags 1-2 days.
keyword
get_keyword_performance
Return Google Search Console query metrics. Pass start_date and end_date together (inclusive JST GSC dates); comparison is the immediately preceding equal-length range. Omitting both keeps the dashboard's rolling now-minus-30-days window. Each current and previous window uses a separate dashboard_keywords RPC call, capped at 200 queries by clicks. `period` and `previous_period` show the actual JST date ranges; `date_basis` / `timezone` identify the GSC calendar. `source_windows` exposes the exact p_from/p_to timestamps used for both RPC calls, whether the GSC date bounds are inclusive, and any JST date shared by the two windows. The rolling default has one shared boundary date; explicit date ranges have none. band='all' returns up to limit rows (default 100) with clicks, impressions, CTR, average position, top page and estimated revenue (search-organic RPS × Google clicks); query-matched changes and `truncated` disclose omitted/source-limited rows. A query absent from the previous top 200 may appear new. Explicit dates include both JST GSC dates, while session RPS uses [start, end) and excludes the final microsecond. band='striking' (default limit 10) ranks only candidates among the current top 200; it is not the best opportunity across all queries. Values may differ from the former keyword_breakdown_aggregate because date boundaries, source limit and returned query set differ. Google-search only; data lags 1-2 days. site_id is optional when OAuth-authenticated.
metadata
get_metadata
Return RevenueScope metric definitions, measurement boundaries, and the meaning of confirmed, unconfirmed, zero, sample, comparison-unavailable and retrieval-error states. This is generic metadata; use a site-scoped analytics tool for values. A missing purchase history does not prove purchase tracking is unconfigured.
page
get_page_trend
Return how ONE page's Google Search performance changed over time. Pass start_date and end_date together as inclusive JST dates; comparison dates are not supported. Omitting both preserves the current now-minus-30-days rolling window, which may touch 31 JST dates because GSC filters by date inclusively. Explicit dates are converted to JST day boundaries for GSC rows. `granularity` defaults to day for windows up to about 35 days and week for longer windows; pass it to override. Buckets without GSC rows are omitted. Google-search only; data lags 1-2 days. site_id is optional when OAuth-authenticated. For cross-page snapshots use get_breakdown(dimension='page'); for query trends use get_keyword_performance.
priority
get_priority_insights
STOPPED. This tool no longer returns insights: its old rules (ROAS, saturation) do not match the renewed RevenueScope dashboard. It always returns status='stopped' with the reason and the tools to use instead (get_summary for period KPIs, get_breakdown for channel / entry-page / visitor-history changes). Do not present anything from this tool as a recommendation.
sites
list_sites
List the sites this signed-in account can analyze, in two groups. Each site includes its timezone and today's date in that timezone. Requires OAuth; no site registration is needed. Prefer my_sites; if site_id is omitted, analytics tools use the primary site. When my_sites is empty, analytics tools use the first curated demo site and identify it as sample data.
suggest
suggest_budget_allocation
STOPPED. This tool no longer returns a budget split: the old method weighted every channel by revenue ÷ ad spend, which the renewed RevenueScope dashboard does not provide (it returns ROAS for ad-only platforms only). It always returns status='stopped' with the reason, the alternative (get_breakdown lists each channel's ad spend next to candidate paid-session revenue, with ROAS for ad-only platforms only) and the resume plan (a new method after paid-traffic classification). Do not present anything from this tool as a recommendation.
summary
get_summary
Return headline KPIs (revenue, sessions, RPS, AOV, CVR), engagement metrics and daily trends for the site's calendar month to date, compared with the prior month through the same calendar day (clamped to that month's last day). Pass start_date and end_date together for another inclusive calendar range in the site's analysis timezone; optionally pass compare_start_date and compare_end_date. If comparison dates are omitted, the preceding equal-length range is used. Revenue-dependent metrics are null unless purchase measurement is confirmed; null means unverified, not zero. Required retrieval failures return isError=true and must not be read as zero. No overall ROAS is returned (kpis.roas is always null); per-platform ROAS for ad-only platforms is in get_breakdown ad_spend_candidates. Optional country (ISO2) and device filters scope session-derived metrics. site_id is optional when OAuth-authenticated.
today
get_today
Return today's activity for a site, matching the RevenueScope 今日の状況 screen. Today is the site's timezone from 00:00 to now; values are provisional. Purchase events are observed events, not confirmed orders; unverified revenue and unavailable sections are not zero. Sample-site values do not match the screen's fixed sample data. No event-level or visitor-level rows are returned. For comparison with yesterday at the same time, use get_summary with start_date and end_date both set to today's site-local date. site_id is optional when OAuth-authenticated.
traffic
get_ai_traffic
Return AI-assistant traffic using dashboard_ai_referred. By default, mode='referred' uses the site's calendar month to date and compares with the prior month through the same calendar day (clamped to the prior month's last day). Pass start_date and end_date together for another inclusive calendar range in the site's analysis timezone; optionally pass compare_start_date and compare_end_date. If comparison dates are omitted, the immediately preceding equal-length range is used. mode='gaps' is STOPPED and returns only its stopped notice. site_id is optional when OAuth-authenticated. Scope is clicked citations only.

Endpoints

URLTransportStateLatencyChecked
https://mcp.revenuescope.jp/api/mcp streamable-http answering 78 ms 1 min ago

Alternatives to RevenueScope: revenue-first analytics for your EC site

same job, measured the same way
XPmetric
by xpmetric

Ask your AI about your site's traffic, channels, revenue, goals and funnels (XPmetric analytics).

50 installs/wk local only
Web Analytics
by b77

Ask about your website traffic in chat.

answering
Analytics
by zenovay

Real-time web analytics for AI agents: query traffic, funnels, revenue, and manage your sites.

answering
Clamp Analytics
by clamp

Clamp Analytics MCP server: traffic, revenue, funnels, cohorts, errors, and search, for AI agents.

answering
Yourtraffic
by kozmos-tech

Open-source, privacy-first web analytics for tracking your sites' traffic.

47 installs/wk local only
L
LopeBase
by lopebase

SEO, Search Console, analytics, revenue, and uptime for every site you run, from LopeBase.

495 installs/wk answering
StepMetrics Web Analytics
by stepmetrics

Ask about your website traffic, funnels, SEO and AI agent costs. Sign in with OAuth, no key paste.

answering
Vitrus analytics
by vitrus

Read-only analytics for all your apps: users, AI traffic, revenue, with the SQL behind every number.

answering

RevenueScope: revenue-first analytics for your EC site — questions

Answers built from our own checks of this server.

What can RevenueScope: revenue-first analytics for your EC site do?
It exposes 12 tools, read directly from the server on our last check. Among them: get_ai_traffic, get_breakdown, get_competitor_keywords, get_content_actions, get_keyword_performance, get_metadata and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is RevenueScope: revenue-first analytics for your EC site working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 78 ms. The bar chart above shows every period we have measured.
Is RevenueScope: revenue-first analytics for your EC site still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists RevenueScope: revenue-first analytics for your EC site as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect RevenueScope: revenue-first analytics for your EC site?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does RevenueScope: revenue-first analytics for your EC site need an API key?
No. RevenueScope: revenue-first analytics for your EC site completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.