Remote MCP · Endpoint
opointo MCP server
No. opointo answered an MCP handshake 2 days ago.
UpLast checked 2 days ago
Server URL
https://opointo.com/api/mcp
The last check completed an MCP handshake.
- Registry name
- com.opointo/opointo
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 1.53 s
- Tools exposed
- 11 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Design a React Native app in a browser and emit it as a real Expo project you own, iOS and Android.
- Website
- https://opointo.com/
- Repository
- https://github.com/opointoHQ/opointo-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 days ago | Handshake completed | 1.53 s |
| 3 days ago | Handshake completed | 2.29 s |
| 3 days ago | Handshake completed | 1.09 s |
| 5 days ago | Handshake completed | 1.42 s |
| 6 days ago | Handshake completed | 872 ms |
| 7 days ago | Handshake completed | 1.75 s |
| 8 days ago | Handshake completed | 998 ms |
| 9 days ago | Handshake completed | 1.86 s |
| 11 days ago | Handshake completed | 1.34 s |
| 13 days ago | Handshake completed | 939 ms |
| 16 days ago | Handshake completed | 1.69 s |
| 18 days ago | Handshake completed | 1.05 s |
| 21 days ago | Handshake completed | 1.07 s |
| 22 days ago | Handshake completed | 828 ms |
| 25 days ago | Handshake completed | 983 ms |
| 27 days ago | Handshake completed | 1.28 s |
| 29 days ago | Handshake completed | 1.31 s |
| 30 days ago | Handshake completed | 673 ms |
| 31 days ago | Handshake completed | 792 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 27 responding of 27.
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 opointo and makes no claim about it beyond what these checks measured.