Remote MCP · Endpoint

io.bootify/mcp MCP server

No. io.bootify/mcp answered an MCP handshake 6 days ago.

UpLast checked 6 days ago

Server URL

https://bootify.io/mcp

The last check completed an MCP handshake.

Registry name
io.bootify/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
324 ms
Tools exposed
57 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Build Spring Boot applications, ready for coding agents, including best practices.
Listing
From the official MCP registry (active).
Recent checks of io.bootify/mcp
CheckedResultHandshake
6 days agoHandshake completed324 ms
7 days agoHandshake completed418 ms
7 days agoHandshake completed346 ms
9 days agoHandshake completed323 ms
10 days agoHandshake completed363 ms
11 days agoHandshake completed327 ms
12 days agoHandshake completed323 ms
13 days agoHandshake completed333 ms
15 days agoHandshake completed334 ms
17 days agoHandshake completed364 ms
20 days agoHandshake completed344 ms
22 days agoHandshake completed326 ms
25 days agoHandshake completed343 ms
26 days agoHandshake completed342 ms
29 days agoHandshake completed327 ms
31 days agoHandshake completed322 ms
32 days agoHandshake completed339 ms
34 days agoHandshake completed338 ms
35 days agoHandshake completed320 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with io.bootify/mcp and makes no claim about it beyond what these checks measured.