Remote MCP · Endpoint

Hovercode MCP server

No. Hovercode answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://hovercode.com/mcp/

The last check completed an MCP handshake.

Registry name
com.hovercode/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
340 ms
Tools exposed
36 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Create and manage QR codes, short links, landing pages, and forms in your Hovercode workspace.
Listing
From the official MCP registry (active).
Recent checks of Hovercode
CheckedResultHandshake
1 hour agoHandshake completed340 ms
2 days agoHandshake completed8.25 s
4 days agoHandshake completed155 ms
5 days agoHandshake completed154 ms
7 days agoHandshake completed157 ms
8 days agoHandshake completed325 ms
9 days agoHandshake completed151 ms
12 days agoHandshake completed141 ms
13 days agoHandshake completed478 ms
15 days agoHandshake completed160 ms
16 days agoHandshake completed217 ms
17 days agoHandshake completed319 ms
18 days agoHandshake completed347 ms
19 days agoHandshake completed134 ms
20 days agoHandshake completed136 ms
21 days agoHandshake completed350 ms
22 days agoHandshake completed148 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 Hovercode and makes no claim about it beyond what these checks measured.