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
Listing
From the official MCP registry (active).
Recent checks of io.github.drain54/verify-api
CheckedResultHandshake
1 hour agoHandshake completed814 ms
1 day agoHandshake completed999 ms
4 days agoHandshake completed808 ms
6 days agoHandshake completed772 ms
7 days agoHandshake completed748 ms
9 days agoHandshake completed2.08 s
10 days agoHandshake completed827 ms
11 days agoHandshake completed764 ms
14 days agoHandshake completed754 ms
15 days agoHandshake completed741 ms
17 days agoHandshake completed766 ms
19 days agoHandshake completed769 ms
20 days agoHandshake completed752 ms
21 days agoHandshake completed753 ms
22 days agoHandshake completed822 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.