Home / MCP registry index / dev.clusterhack/clusterhack

ClusterHack

dev.clusterhack/clusterhack in the official MCP registry. Endpoint https://clusterhack.dev/mcp/.

The registry describes it as: Run hackathons end to end: events, teams, submissions, judging and winners.

We read its 60 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

event_roles list_api_endpoints list_capabilities search server_info whoami event_background_images event_cities event_faq event_get event_info_blocks event_list event_nominations event_presets event_schedule event_share_links event_team_stages event_types event_branding event_free_agents event_my_membership event_my_registration_answers event_registration_form invite_preview team_get team_list team_locations team_matchmaking_teams team_members team_open_roles team_posts team_readiness team_roles team_seeking_members submission_get submission_list submission_list_media submission_page event_leaderboard showcase_browse company_about_us company_employees company_employment_requests company_ex_employees company_get company_list company_roster company_vacancies event_sponsor_text event_sponsor_tiers event_sponsors article_get article_languages article_list article_titles legal_info tag_list tech_list account_ai_access account_how_to_sign_in

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/dev-clusterhack-clusterhack/badge.svg)](https://lazaretto.dev/mcp-registry/dev-clusterhack-clusterhack)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.