RevenueScope: revenue-first analytics for your EC site

Name: RevenueScope: revenue-first analytics for your EC site
Author: toshihiroshishido

MCP serverMCP

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

by toshihiroshishidorepository ↗homepage ↗v1.9.1

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"revenuescope-revenue-first-analytics-for-your-ec","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability111/111 checks ok

when	check	result	http	latency	detail
6 h ago	mcp initialize	ok	200	304 ms	server revenuescope-mcp 5.6.0 · protocol 2025-06-18 · 12 tools
12 h ago	mcp initialize	ok	200	415 ms	server revenuescope-mcp 5.6.0 · protocol 2025-06-18 · 12 tools
18 h ago	mcp initialize	ok	200	316 ms	server revenuescope-mcp 5.6.0 · protocol 2025-06-18 · 12 tools
25 h ago	mcp initialize	ok	200	303 ms	server revenuescope-mcp 5.6.0 · protocol 2025-06-18 · 12 tools
31 h ago	mcp initialize	ok	200	279 ms	server revenuescope-mcp 5.3.0 · protocol 2025-06-18 · 12 tools
2 d ago	mcp initialize	ok	200	309 ms	server revenuescope-mcp 5.3.0 · protocol 2025-06-18 · 12 tools
2 d ago	mcp initialize	ok	200	322 ms	server revenuescope-mcp 5.3.0 · protocol 2025-06-18 · 12 tools
2 d ago	mcp initialize	ok	200	298 ms	server revenuescope-mcp 5.3.0 · protocol 2025-06-18 · 12 tools
2 d ago	mcp initialize	ok	200	297 ms	server revenuescope-mcp 5.3.0 · protocol 2025-06-18 · 12 tools
3 d ago	mcp initialize	ok	200	338 ms	server revenuescope-mcp 5.3.0 · protocol 2025-06-18 · 12 tools

Tools observed via MCP handshake

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 reg
get_metadata — Return RevenueScope metric definitions, measurement boundaries, and the meaning of confirmed, unconfirmed, zero, sample, comparison-unavailable and retrieval-er
get_summary — Return headline KPIs (revenue, orders, sessions, RPS, AOV, CVR), engagement metrics and daily trends for the site's calendar month to date, compared with the pr
get_today — Return today's activity for a site: the site's timezone from 00:00 to now, provisional values. No screen of the RevenueScope app shows this view now. Purchase e
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 compare
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-lengt
get_ai_traffic — Return AI-assistant traffic using dashboard_ai_referred, a separate RPC from the AI channels of dashboard_channels that the search screen shows (for the screen'
get_priority_insights — STOPPED. This tool no longer returns insights: its old rules (ROAS, saturation) do not match the current RevenueScope definitions. It always returns status='sto
suggest_budget_allocation — STOPPED. This tool no longer returns a budget split: the old method weighted every channel by revenue ÷ ad spend, which RevenueScope no longer provides (it retu
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 suppor
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
get_competitor_keywords — Return the latest competitor SEO snapshot for the site which keywords each tracked competitor DOMAIN ranks for on Google (Japan/ja), at what position, with mont

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.toshihiroshishido/revenuescope-mcp

first seen 1 mo ago · fetched 2 d agoopen ↗

Field history (7 recent events)

1 mo ago · declared · summary → "Ask AI about your EC site's revenue by channel, RPS/AOV/CVR, search & AI traffic, budget split."
1 mo ago · declared · description → "Ask AI about your EC site's revenue by channel, RPS/AOV/CVR, search & AI traffic, budget split."
1 mo ago · declared · publisherName → "toshihiroshishido"
1 mo ago · declared · homepageUrl → "https://www.revenuescope.jp"
1 mo ago · declared · repoUrl → "https://github.com/toshihiroshishido/revenuescope-mcp"
1 mo ago · declared · version → "1.9.1"
1 mo ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from