Remote MCP · Endpoint
RevenueScope: revenue-first analytics for your EC site MCP server
Yes, as of 2 hours ago: the hostname does not resolve.
DownLast checked 2 hours 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
- 88.2% from 17 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 |
|---|---|---|
| 2 hours ago | Failed - the hostname does not resolve | — |
| 2 days ago | Failed - the hostname does not resolve | — |
| 4 days ago | Handshake completed | 222 ms |
| 5 days ago | Handshake completed | 352 ms |
| 7 days ago | Handshake completed | 248 ms |
| 8 days ago | Handshake completed | 220 ms |
| 9 days ago | Handshake completed | 264 ms |
| 12 days ago | Handshake completed | 233 ms |
| 13 days ago | Handshake completed | 233 ms |
| 15 days ago | Handshake completed | 224 ms |
| 17 days ago | Handshake completed | 223 ms |
| 18 days ago | Handshake completed | 229 ms |
| 19 days ago | Handshake completed | 1.16 s |
| 20 days ago | Handshake completed | 238 ms |
| 20 days ago | Handshake completed | 257 ms |
| 21 days ago | Handshake completed | 236 ms |
| 23 days ago | Handshake completed | 241 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 17.
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.