Remote MCP · Endpoint
Sharebench MCP server
No. Sharebench answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp-public.sharebench.ai/
The last check completed an MCP handshake.
- Registry name
- ai.sharebench/registry
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 508 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Sharebench — search & pull AI skills, agents, prompts & playbooks (SKILL.md) into any MCP client
- Website
- https://sharebench.ai/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 508 ms |
| 12 hours ago | Handshake completed | 572 ms |
| 1 day ago | Handshake completed | 482 ms |
| 2 days ago | Handshake completed | 513 ms |
| 4 days ago | Handshake completed | 502 ms |
| 4 days ago | Handshake completed | 480 ms |
| 5 days ago | Handshake completed | 521 ms |
| 7 days ago | Handshake completed | 476 ms |
| 8 days ago | Handshake completed | 8.94 s |
| 11 days ago | Handshake completed | 517 ms |
| 13 days ago | Handshake completed | 490 ms |
| 16 days ago | Handshake completed | 528 ms |
| 18 days ago | Handshake completed | 478 ms |
| 20 days ago | Handshake completed | 729 ms |
| 22 days ago | Handshake completed | 474 ms |
| 24 days ago | Handshake completed | 513 ms |
| 26 days ago | Handshake completed | 464 ms |
| 28 days ago | Handshake completed | 479 ms |
| 29 days ago | Handshake completed | 544 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.
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 Sharebench and makes no claim about it beyond what these checks measured.