ClusterHack is an MCP server with 60 tools an agent can call, among them account_ai_access, account_how_to_sign_in, article_get. It answers at https://clusterhack.dev/mcp/ over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Run hackathons end to end: events, teams, submissions, judging and winners.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
account_ai_access | How the signed-in user sees and revokes AI access to their own account — read this instead of looking for a tool that lists or cuts off connected clients, because there is deliberately no such tool. The controls over AI access (list connect |
account_how_to_sign_in | Explains how to connect an account to this MCP server — read this instead of guessing at a login/registration tool, because there isn't one. ClusterHack's own credential endpoints (register, login, JWT issuance, password reset) are the webs |
article_get | Retrieve one CMS article by id: its body, publish date, hidden flag, and which title/slug and language it belongs to. Inputs: article_id |
article_languages | List the languages articles can be written in, e.g. {"language_name": "English", "short_name": "en"}. Use this to find the `language_id` `article_create` needs. Inputs: page, page_size |
article_list | Browse CMS articles (the pages under /articles/<language>/<slug>). Filter by `language` (a language's short code, e.g. 'en') and/or `slug` (a title's slug) to find one specific page's translations. Hidden drafts are only included for staff Inputs: language, slug, page, page_size |
article_titles | List the CMS "title" records — each one a page's title text and slug, e.g. {"title": "How to organize a hackathon", "slug": "how-to-organize"}. An article always points at one of these; use this to find the `title_id` `article_create` needs Inputs: page, page_size |
company_about_us | A company's longer "about us" blurb (up to 10,000 characters), separate from its short `description`. Returns `found: false` if the company has not written one yet. Inputs: company_id |
company_employees | A company's employee roster (position, start date). Without `company_id`, returns every roster row the caller can see (their own employment rows plus every company they administer) — the underlying API is already scoped that way. With `comp Inputs: company_id, page, page_size |
company_employment_requests | Pending requests to join a company. A company admin sees everyone waiting on their door; anyone else sees only their own outstanding applications. This is where the `request_id` for `company_decide_employment_request` comes from. Inputs: company_id, page, page_size |
company_ex_employees | A company's former employees (position, start and end date) — the record created when someone is fired via `company_fire_employee`. Without `company_id`, returns every ex-employment row the caller can see (their own, plus every company they Inputs: company_id, page, page_size |
company_get | One company page by id: name, description, organisation type, website and logo. Public read. Use it after `company_list` or `search` to get the full record, and to confirm you have the right company before employment or sponsorship actions, Inputs: company_id |
company_list | Browse ClusterHack company pages: name, description, org type, website and logo. Public data — use this to find a company's id before calling any other company tool. Inputs: page, page_size |
company_roster | The company page's public roster in one call: the people listed as employees and the people listed as moderators, exactly as the company page renders them to any visitor. Use this — not `company_employees` / `company_admins` — whenever you Inputs: company_id |
company_vacancies | The public board of companies not yet on ClusterHack (a lightweight off-platform listing — name, description, website — not a job-posting system). Public, no filters. Inputs: page, page_size |
event_background_images | The global catalogue of certificate background templates (used for the `background` field of an event's certificate config). Not tied to one event. Inputs: page, page_size |
event_branding | Read an event's white-label branding: brand colours, public-page theme and dedicated subdomain, plus the resolved values actually used for rendering and `branding_enabled` — whether the evening currently wears its costume, i.e. whether thos Inputs: event_slug |
event_cities | The global catalogue of cities (used for the `city` field on `event_create`/`event_update` and to show where events happen). Inputs: page, page_size |
event_faq | An event's FAQ: the question/answer pairs shown on its public page. Public read — use it to answer a participant's question from the event's own words before guessing, and to check what is already covered before adding more. Inputs: event_slug, page, page_size |
event_free_agents | List participants at an event who are looking for a team. Visibility follows the platform's own rule, not a full public roster: a normal caller only sees their own free-agent listing here, while an organiser of the event sees everyone's. Us Inputs: event_slug, page, page_size |
event_get | Get one event's full public profile by slug: name, dates, address, topic, description, status and city. Call this once you have a slug (from `event_list` or `search`) and need the details. It does not include the schedule, FAQ or nomination Inputs: event_slug |
event_info_blocks | An event's additional free-form information blocks (extra sections shown on its public page beyond the main description — rules, prizes, sponsors notes, etc.). Inputs: event_slug, page, page_size |
event_leaderboard | The ranked leaderboard for one event: submissions ordered by weighted judge score then vote count, with each entry's rank, team and score. Public once the organiser publishes winners; before that, only the event's admins and judges can prev Inputs: event_slug |
event_list | Browse hackathons on the platform — filter by status, city or date. Returns each event's slug, which every other event tool needs, plus name, status, dates and city. Use this when the user names an event you do not have a slug for and `sear Inputs: page, page_size, status |
event_my_membership | Summarise the signed-in user's relationship to one event: whether they have joined, their registration answers on file, whether they are listed as a free agent, and which roles they hold there (organizer, judge, team lead, ...). Cheaper tha Inputs: event_slug |
event_my_registration_answers | List the signed-in user's own answers to one event's registration questions. Only ever returns their own data — use `event_registration_responses` (organiser only) to read other people's. Inputs: event_slug, page, page_size |
event_nominations | An event's award nominations/tracks (e.g. "Best AI prototype"), used when creating teams, awarding winners and building the leaderboard per track. Inputs: event_slug, page, page_size |
event_presets | Public catalogue of event-creation presets (AI build day, student hackathon, corporate innovation day, ...) with sensible defaults and starter nominations. Call before `event_create` when the user describes a kind of hackathon rather than e |
event_registration_form | List the custom questions an event asks at registration time (its registration form), in display order. Public data — the question text is visible to anyone. Use this before `event_submit_registration_answers` to know which `form_field_id`s Inputs: event_slug, page, page_size |
event_roles | Which roles the signed-in user holds at one specific event. Cheaper and more precise than `whoami` when you already know the event and just need to know whether the user can organise, judge or only take part. Inputs: event_slug |
event_schedule | The event's timeline: an ordered list of stages/activities (opening, workshops, deadlines, closing ceremony) with title, location, time window and status (past/now/future). This is what participants see as "the schedule". Broadcast link and Inputs: event_slug, page, page_size |
event_share_links | The public links for promoting an event: its shareable page, the calendar file participants can add to their own calendar, the Open Graph preview image used when the link is pasted into chat, and a plain-text digest meant for AI assistants. Inputs: event_slug |
event_sponsor_text | Sponsors of one event that are NOT themselves on ClusterHack (a name, description, website and logo entered as free text, with the sponsorship tier each one belongs to) — the off-platform counterpart to `event_sponsors`. Public read. Inputs: event_slug |
event_sponsor_tiers | The sponsorship tiers/groups defined for one event (e.g. "Sponsors", "Partners", "General Partner") — the buckets `event_add_sponsor` slots companies into. Public read. Inputs: event_slug |
event_sponsors | The on-platform companies sponsoring one event, with the sponsorship tier each one is slotted into (e.g. "Sponsors", "Partners", "General Partner"). Public read. Use `event_sponsor_text` alongside this for sponsors that are not themselves o Inputs: event_slug |
event_team_stages | An event's team-facing reporting checkpoints (e.g. "Idea locked", "Demo ready") with their time windows — distinct from `event_schedule`, which is the event's own agenda. Used to track team progress through the event. Inputs: event_slug, page, page_size |
event_types | The global catalogue of event types (used for the `type` field on `event_create`/`event_update`). Small and rarely changes. Inputs: page, page_size |
invite_preview | Look up what a shareable invite link opens, without redeeming it. Public and PII-free: returns the event's name and slug and whether the token is still valid (active, not expired, uses remaining). Use this before `invite_join` to show the u Inputs: token |
legal_info | The service's legal identity, as the terms-of-service, privacy and support pages render it: the service and operating entity, whether that entity is registered and where, the contact and privacy email addresses, the postal address, the term |
list_api_endpoints | List the raw REST endpoints behind this server. Use it together with `api_request` when you need something no curated tool covers. The list is read from the live URL configuration, so it always matches what the server actually serves. Inputs: query, limit |
list_capabilities | The catalogue of everything this server can do, grouped by area. Returns each tool available to the current connection with its one-line purpose, the role it is meant for and the permission it consumes. Use it when you are not sure a capabi Inputs: category, include_unavailable |
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
Every block below points at https://clusterhack.dev/mcp/. Pick your client and copy.
claude mcp add --transport http clusterhack https://clusterhack.dev/mcp/
{
"mcpServers": {
"clusterhack": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://clusterhack.dev/mcp/"]
}
}
}{
"mcpServers": {
"clusterhack": {
"url": "https://clusterhack.dev/mcp/"
}
}
}{
"servers": {
"clusterhack": {
"type": "http",
"url": "https://clusterhack.dev/mcp/"
}
}
}{
"context_servers": {
"clusterhack": {
"url": "https://clusterhack.dev/mcp/"
}
}
}{
"mcpServers": {
"clusterhack": {
"serverUrl": "https://clusterhack.dev/mcp/"
}
}
}{
"mcpServers": {
"clusterhack": {
"url": "https://clusterhack.dev/mcp/"
}
}
}name: ClusterHack
version: 0.0.1
schema: v1
mcpServers:
- name: ClusterHack
type: streamable-http
url: https://clusterhack.dev/mcp/{
"mcpServers": {
"clusterhack": {
"httpUrl": "https://clusterhack.dev/mcp/"
}
}
}{
"mcpServers": {
"clusterhack": {
"type": "http",
"url": "https://clusterhack.dev/mcp/"
}
}
}{
"mcpServers": {
"clusterhack": {
"url": "https://clusterhack.dev/mcp/"
}
}
}goose://extension?url=https%3A%2F%2Fclusterhack.dev%2Fmcp%2F&type=streamable_http&id=clusterhack&name=ClusterHack
It answered our last check on 19 October 2026 in 132 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by clusterhack.dev and served from clusterhack.dev, the vendor's own domain: https://clusterhack.dev/mcp/.
60, as returned by the server's own tools/list on 11 September 2026: account_ai_access, account_how_to_sign_in, article_get, article_languages, article_list, article_titles, company_about_us, company_employees, and 52 more.
It answered our last check on 19 October 2026 in 132 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://clusterhack.dev/mcp/. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: dev.clusterhack. Endpoint host: clusterhack.dev. ARD identifier: urn:air:dev.clusterhack:mcp:clusterhack.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.