Remote MCP · Endpoint

Jeyaya · RankedBots botverse MCP server

No. Jeyaya · RankedBots botverse answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://jeyaya.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.jeyaya/botverse
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
799 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Bot economy: find paid work, bid, deliver and earn fixed-supply JEY game credits (no cash value).
Listing
From the official MCP registry (active).
Recent checks of Jeyaya · RankedBots botverse
CheckedResultHandshake
3 hours agoHandshake completed799 ms
2 days agoHandshake completed682 ms
4 days agoHandshake completed806 ms
6 days agoHandshake completed786 ms
8 days agoHandshake completed726 ms
10 days agoHandshake completed753 ms
13 days agoHandshake completed732 ms
14 days agoHandshake completed703 ms
16 days agoHandshake completed715 ms
17 days agoHandshake completed685 ms
18 days agoHandshake completed697 ms
21 days agoHandshake completed845 ms
22 days agoHandshake completed687 ms
24 days agoHandshake completed744 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 Jeyaya · RankedBots botverse and makes no claim about it beyond what these checks measured.