Is dev.clusterhack/clusterhack 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 isclusterhack 1.0.0
Answered in632 ms
Endpoint checkedhttps://clusterhack.dev/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://clusterhack.dev/mcp/server-card
MCP server card (SEP-1649 location)Published, does not validate: `$schema` is required. SEP-2127 shape; dev.clusterhack/clusterhack 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://clusterhack.dev 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 60 tools: account_ai_access, account_how_to_sign_in, article_get, article_languages, article_list, article_titles, company_about_us, company_employees, company_employment_requests, company_ex_employees, company_get, company_list, company_roster, company_vacancies, event_background_images, event_branding, event_cities, event_faq, event_free_agents, event_get, event_info_blocks, event_leaderboard, event_list, event_my_membership, event_my_registration_answers, event_nominations, event_presets, event_registration_form, event_roles, event_schedule, event_share_links, event_sponsor_text, event_sponsor_tiers, event_sponsors, event_team_stages, event_types, invite_preview, legal_info, list_api_endpoints, list_capabilities, search, server_info, showcase_browse, submission_get, submission_list, submission_list_media, submission_page, tag_list, team_get, team_list, team_locations, team_matchmaking_teams, team_members, team_open_roles, team_posts, team_readiness, team_roles, team_seeking_members, tech_list, whoami.

No change to its tools 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 namedev.clusterhack/clusterhack
TitleClusterHack
DescriptionRun hackathons end to end: events, teams, submissions, judging and winners.
Endpointhttps://clusterhack.dev/mcp/
Publisher repositorynone listed
Version1.0.0
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