Remote MCP · Endpoint
RevenueScope: revenue-first analytics for your EC site MCP server
Yes, as of 1 hour ago: the hostname does not resolve.
DownLast checked 1 hour ago
Server URL
https://mcp.revenuescope.jp/api/mcp
The last check failed: the hostname does not resolve.
- Registry name
- io.github.toshihiroshishido/revenuescope-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 10 tools
- Uptime, last 30 days
- 22.2% from 18 checks
- Described by its publisher as
- Ask AI about your EC site's revenue by channel, RPS/AOV/CVR, search & AI traffic, budget split.
- Website
- https://www.revenuescope.jp/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the hostname does not resolve | — |
| 1 day ago | Failed - the hostname does not resolve | — |
| 2 days ago | Failed - the hostname does not resolve | — |
| 3 days ago | Failed - the hostname does not resolve | — |
| 4 days ago | Failed - the hostname does not resolve | — |
| 5 days ago | Failed - the hostname does not resolve | — |
| 6 days ago | Failed - the hostname does not resolve | — |
| 9 days ago | Failed - the hostname does not resolve | — |
| 11 days ago | Failed - the hostname does not resolve | — |
| 14 days ago | Failed - the hostname does not resolve | — |
| 16 days ago | Failed - the hostname does not resolve | — |
| 18 days ago | Failed - the hostname does not resolve | — |
| 20 days ago | Failed - the hostname does not resolve | — |
| 22 days ago | Failed - the hostname does not resolve | — |
| 24 days ago | Handshake completed | 222 ms |
| 26 days ago | Handshake completed | 352 ms |
| 27 days ago | Handshake completed | 248 ms |
| 29 days ago | Handshake completed | 220 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 29.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with RevenueScope: revenue-first analytics for your EC site and makes no claim about it beyond what these checks measured.