Is com.hovercode/mcp up? Live MCP status

Yes, it is up. It answered an MCP initialize with no credential and negotiated protocol 2025-06-18.

A stock client connected with no credential and negotiated 2025-06-18. Use it.

Outcomeusable
HTTP status200
Protocol version2025-06-18
Server says it ishovercode 1.0.0
Answered in453 ms
Endpoint checkedhttps://hovercode.com/mcp/
Checked

One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.

Live status every few hours: Wellknown

Email me when this server changes

That was one look. To hear when it stops answering or its tools change, leave an address.

Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.

Monthly census, 6 October 2026

The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).

Agent discovery documents at this origin

A2A agent cardNot published (HTTP 404).
/.well-known/agent-card.json
MCP server card (SEP-2127)Not published (HTTP 404).
https://hovercode.com/mcp/server-card
MCP server card (SEP-1649 location)Published, does not validate: `$schema` is required (and 4 more). SEP-1649 shape; Hovercode MCP 1.0.0; streamable-http.
/.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026
Web Bot Auth key directoryNot published (HTTP 404).
/.well-known/http-message-signatures-directory

Read at https://hovercode.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.

Tool changes between snapshots

In the 2026-10 snapshot it listed 36 tools: build_page, create_folder, create_form, create_page, create_pdf_qr, create_qr_code, create_qr_codes_bulk, create_short_link, delete_folder, delete_page, delete_qr_code, delete_short_link, download_qr, get_analytics, get_form, get_form_responses, get_page, get_qr_activity, get_qr_code, get_short_link, get_short_link_activity, list_block_types, list_folders, list_forms, list_pages, list_qr_codes, list_short_links, list_tags, list_templates, list_workspaces, set_workspace, update_folder, update_form, update_page, update_qr_code, update_short_link.

Its tools changed between 2026-09 and 2026-10:

Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.

The listing

Registry namecom.hovercode/mcp
TitleHovercode
DescriptionCreate and manage QR codes, short links, landing pages, and forms in your Hovercode workspace.
Endpointhttps://hovercode.com/mcp/
Publisher repositoryhttps://github.com/Hovercode-Ltd/hovercode-mcp
Version1.0.1
Listing updated

Also

The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt

Free, no key, no signup. Terms · Privacy