List your agent

ClusterHack

MCP server● Hosted · onlinev1.0.0

Run hackathons end to end: events, teams, submissions, judging and winners

Reviews

No review yet. Used ClusterHack? Be the first to help others choose.

What it does

ClusterHack is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.0.0
PriceNot in the registry
First seen26 Sept 2026
Last checked1d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)

Hosted endpoint

  • https://clusterhack.dev/mcp/ streamable-http

In Claude Code: claude mcp add --transport http clusterhack https://clusterhack.dev/mcp/

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "clusterhack": {
      "url": "https://clusterhack.dev/mcp/"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 1d ago

ONLINE ClusterHack answered an MCP connection on 16 Nov 2026 and introduced itself as clusterhack 1.0.0 (MCP protocol 2025-06-18).

60 tools offered to AI assistants

  • 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.
  • 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.
  • 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
  • search · Search across the platform: events, teams, projects, people and articles. One call when you do not yet know the identifier of the thing the user means ("the AI hackathon in Berlin", "Sasha's team"). Returns the matching objects with the slu
  • server_info · What this MCP server is, which version it speaks, and how to connect. Useful for diagnostics and for telling the user where to manage or revoke the connection.
  • whoami · Who is signed in, what roles they hold, and where. Call this first in any new conversation. It returns the account, the OAuth permissions this connection was granted, and — crucially — the list of events, teams and companies the user belong
  • 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.
  • event_cities · The global catalogue of cities (used for the `city` field on `event_create`/`event_update` and to show where events happen).
  • 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.
  • 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
  • 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.).
  • 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
Show 48 more
  • 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.
  • 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_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
  • 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.
  • 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.
  • event_types · The global catalogue of event types (used for the `type` field on `event_create`/`event_update`). Small and rarely changes.
  • 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
  • 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
  • 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
  • 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.
  • 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
  • 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
  • team_get · Get one team's full detail: name, description, project info, readiness, accessibility flags, and which event and nomination it belongs to. Only visible if the signed-in user belongs to the team, created it, or administers its event.
  • team_list · List teams — scoped to what the signed-in account can see: teams they belong to, created, or administer via being an admin of the team's event. This is never a full public directory of every team on the platform. Filter by `event_slug` to s
  • team_locations · Read the physical location details linked to a team's additional-info profile (street, city, state, zip), if one has been set. There is currently no self-service way to create a new location through this API — location rows are set up separ
  • team_matchmaking_teams · AI-ranked list of teams one free (teamless) participant could join, within the same event. Callable by the free-agent listing's own owner, or an admin of the event. Use `event_free_agents` or `event_join_as_free_agent` to get a `free_member
  • team_members · List a team's current members with their role and caption. Use the row `id` (a membership id, not a user id) with `team_assign_role` or `team_remove_member`.
  • team_open_roles · List the positions teams are looking to fill ("we need a designer"). Visibility is limited to what the signed-in account can already see: their own team's open roles, or — if they organise the event — every team's. It is not a public cross-
  • team_posts · List a team's public updates ("twits") — the short build-log posts a team publishes as it works, in the order the server returns them. Use it to catch up on what a team has been doing, or to check what has already been posted before writing
  • team_readiness · Check whether a team has marked itself ready to present, plus whether it is banned or currently accessible for judging.
  • team_roles · List the roles a team has defined (e.g. "Frontend", "Designer"), which members can be assigned via `team_assign_role`.
  • team_seeking_members · Browse the teams of one event that are advertising open positions — the public "who is recruiting" list behind the find-a-team page, readable by anyone, including someone who has not joined the event yet. This is the tool for a person looki
  • submission_get · Retrieve one project submission by id: title, links, description, status, approval status, vote count and attached media. Anonymous and unrelated callers only see it once the team has submitted (status "submitted"); drafts are visible only
  • submission_list · Browse project submissions, filterable by event, team or status. Anonymous and unrelated callers only ever see submitted (public) projects; a signed-in caller additionally sees their own team's drafts and every submission at events they adm
  • submission_list_media · List the screenshots/gallery images attached to a submission. Visibility mirrors the parent submission: public once submitted, otherwise limited to the team, event admins and judges.
  • submission_page · Read a project's public page: the submission itself, every judge's written feedback (signed with the judge's name only where that judge consented to being named, empty otherwise), and — once the organiser has published the winners — its pla
  • 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
  • showcase_browse · Browse the public, cross-event showcase: shipped/submitted projects ranked for display, with title, tagline, team name, vote count and a cover image. Optionally narrow to one event. This is the public gallery — use `event_leaderboard` inste
  • 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.
  • 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
  • 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.
  • 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
  • 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,
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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
  • article_get · Retrieve one CMS article by id: its body, publish date, hidden flag, and which title/slug and language it belongs to.
  • 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.
  • 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
  • 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
  • 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
  • tag_list · List tags used to categorize content across the platform (articles, projects and more share the same tag vocabulary).
  • tech_list · List technologies (tech-stack tags) that projects and teams can be labelled with, e.g. "React", "PostgreSQL".
  • 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

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://clusterhack.dev/mcp/DECLAREDSRC-001 Official MCP Registry1d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry1d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry1d ago
Websitehttps://clusterhack.dev/mcp-featuresDECLAREDSRC-001 Official MCP Registry1d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry1d ago
Version1.0.0DECLAREDSRC-001 Official MCP Registry1d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry1d ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run ClusterHack? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor ClusterHackLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of ClusterHack?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/clusterhack?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/clusterhack/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about ClusterHack

How do I connect ClusterHack?

Use the hosted endpoint https://clusterhack.dev/mcp/ in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does ClusterHack offer?

When Electra Index connected on 16 Nov 2026, it listed 60 tools: event_roles, list_api_endpoints, list_capabilities, search, server_info, whoami, event_background_images, event_cities and more. The full list is in "Live check" above.

Is ClusterHack online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.