MCP server for hackproof #19

Why

Every Claude, Cursor and Raven user should be able to ask HackProof questions. An MCP server over the public data is the cheapest integration with the biggest reach.

What to build

• apps/mcp/ (TypeScript, @modelcontextprotocol/sdk, part of the pnpm workspace). It reads the public API over https.
• Tools: list_hackathons, get_summary, query_projects, get_project, get_contract, hourly, distributions, top_errors, compare_idea(text) (keyword match over project names, descriptions and topics, returning the closest projects with the matched terms) and methodology(). Map them to the existing routes in apps/api/src/hackproof/routes.py and add routes where one is missing.
• An in memory cache with ETag revalidation once the API sends ETags (see the public API issue), a plain TTL until then.
• Every tool response includes when the data was generated, so agents can say how fresh an answer is. The API does not expose this yet: add it to the stats response from the last sync time.
• Publish to npm as hackproof-mcp. The README shows config snippets for Claude Desktop, Cursor and Raven.

Acceptance criteria

• npx hackproof-mcp runs and every tool returns data against a running API.
• Tests with a fixture API for every tool.
• The README has copy paste config for Claude Desktop, Cursor and Raven.

See CONTRIBUTING.md for conventions.