Remote MCP · Endpoint
One-Page Readiness Check — 10 Signals, Arabic or English MCP server
No. One-Page Readiness Check — 10 Signals, Arabic or English answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://advisorsai.ai/store-readiness-mcp
The last check completed an MCP handshake.
- Registry name
- ai.advisorsai/store-readiness
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 479 ms
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 94.4% from 18 checks
- Described by its publisher as
- Ten machine-readable signals on one public page: the top miss if any, and a receipt we re-verify.
- Website
- https://advisorsai.ai/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 479 ms |
| 1 day ago | Handshake completed | 440 ms |
| 3 days ago | Handshake completed | 430 ms |
| 3 days ago | Handshake completed | 432 ms |
| 4 days ago | Handshake completed | 386 ms |
| 5 days ago | Handshake completed | 519 ms |
| 7 days ago | Failed - the request timed out | — |
| 10 days ago | Handshake completed | 548 ms |
| 12 days ago | Handshake completed | 526 ms |
| 14 days ago | Handshake completed | 521 ms |
| 17 days ago | Handshake completed | 532 ms |
| 19 days ago | Handshake completed | 530 ms |
| 21 days ago | Handshake completed | 443 ms |
| 23 days ago | Handshake completed | 513 ms |
| 25 days ago | Handshake completed | 527 ms |
| 26 days ago | Handshake completed | 492 ms |
| 28 days ago | Handshake completed | 591 ms |
| 29 days ago | Handshake completed | 652 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 27 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 One-Page Readiness Check — 10 Signals, Arabic or English and makes no claim about it beyond what these checks measured.