Remote MCP · Endpoint
io.github.drain54/verify-api MCP server
No. io.github.drain54/verify-api answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://verify.drain54.my.id/
The last check completed an MCP handshake.
- Registry name
- io.github.drain54/verify-api
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 814 ms
- Tools exposed
- 8 tools
- Uptime, last 30 days
- 100% from 15 checks
- Described by its publisher as
- AI claim verification MCP endpoint with x402 payments and stealth web fetch
- Repository
- https://github.com/drain54/verify-api
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 814 ms |
| 1 day ago | Handshake completed | 999 ms |
| 4 days ago | Handshake completed | 808 ms |
| 6 days ago | Handshake completed | 772 ms |
| 7 days ago | Handshake completed | 748 ms |
| 9 days ago | Handshake completed | 2.08 s |
| 10 days ago | Handshake completed | 827 ms |
| 11 days ago | Handshake completed | 764 ms |
| 14 days ago | Handshake completed | 754 ms |
| 15 days ago | Handshake completed | 741 ms |
| 17 days ago | Handshake completed | 766 ms |
| 19 days ago | Handshake completed | 769 ms |
| 20 days ago | Handshake completed | 752 ms |
| 21 days ago | Handshake completed | 753 ms |
| 22 days ago | Handshake completed | 822 ms |
The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.
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 io.github.drain54/verify-api and makes no claim about it beyond what these checks measured.