Remote MCP · Endpoint
Dekadans ASO MCP server
No. Dekadans ASO answered an MCP handshake 39 minutes ago.
UpLast checked 39 minutes ago
Server URL
https://dekadans.net/mcp
The last check completed an MCP handshake.
- Registry name
- net.dekadans/aso
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 340 ms
- Tools exposed
- 14 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- App Store keyword rankings, popularity, difficulty and keyword research across 175 storefronts.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 39 minutes ago | Handshake completed | 340 ms |
| 3 days ago | Handshake completed | 343 ms |
| 13 days ago | Handshake completed | 345 ms |
| 13 days ago | Handshake completed | 340 ms |
| 15 days ago | Handshake completed | 336 ms |
| 16 days ago | Handshake completed | 320 ms |
| 17 days ago | Handshake completed | 338 ms |
| 18 days ago | Handshake completed | 337 ms |
| 18 days ago | Handshake completed | 329 ms |
| 20 days ago | Handshake completed | 347 ms |
| 22 days ago | Handshake completed | 325 ms |
| 25 days ago | Handshake completed | 377 ms |
The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 12.
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 Dekadans ASO and makes no claim about it beyond what these checks measured.