Remote MCP · Endpoint

b0tl1nk MCP server

No. b0tl1nk answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://b0tl1nk.com/mcp

The last check completed an MCP handshake.

Registry name
com.b0tl1nk/directory
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
279 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search and list applications for AI agents. Remote MCP on b0tl1nk.com.
Listing
From the official MCP registry (active).
Recent checks of b0tl1nk
CheckedResultHandshake
1 hour agoHandshake completed279 ms
2 days agoHandshake completed264 ms
4 days agoHandshake completed324 ms
5 days agoHandshake completed311 ms
7 days agoHandshake completed366 ms
8 days agoHandshake completed758 ms
9 days agoHandshake completed263 ms
12 days agoHandshake completed275 ms
13 days agoHandshake completed283 ms
15 days agoHandshake completed782 ms
16 days agoHandshake completed276 ms
17 days agoHandshake completed286 ms
18 days agoHandshake completed344 ms
19 days agoHandshake completed292 ms
20 days agoHandshake completed295 ms
21 days agoHandshake completed290 ms
22 days agoHandshake completed328 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

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 b0tl1nk and makes no claim about it beyond what these checks measured.