Remote MCP · Endpoint
WebMCP Demo Store MCP server
No. WebMCP Demo Store answered an MCP handshake 34 minutes ago.
UpLast checked 34 minutes ago
Server URL
https://demowithmcp.converso.work/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.kamatanuj/webmcp-store
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 680 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 14 checks
- Described by its publisher as
- WebMCP demo store: same catalog via MCP tool calls vs DOM scraping. -79% bytes, -42% tokens.
- Repository
- https://github.com/kamatanuj/webmcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 34 minutes ago | Handshake completed | 680 ms |
| 9 days ago | Handshake completed | 683 ms |
| 10 days ago | Handshake completed | 656 ms |
| 11 days ago | Handshake completed | 653 ms |
| 12 days ago | Handshake completed | 684 ms |
| 14 days ago | Handshake completed | 643 ms |
| 14 days ago | Handshake completed | 670 ms |
| 15 days ago | Handshake completed | 651 ms |
| 17 days ago | Handshake completed | 800 ms |
| 19 days ago | Handshake completed | 614 ms |
| 21 days ago | Handshake completed | 660 ms |
| 24 days ago | Handshake completed | 653 ms |
| 26 days ago | Handshake completed | 659 ms |
| 28 days ago | Handshake completed | 676 ms |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.
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 WebMCP Demo Store and makes no claim about it beyond what these checks measured.