MCP server for querying Devpost.com. Search hackathons, fetch winners, analyze tech stack trends.
Server has 10 tools with consistent naming (verb_noun pattern) and descriptions present for all. However, output schemas are entirely undocumented, no return type specifications visible in code. Parameter descriptions are present but generic; many lack format constraints or validation guidance. Error handling returns text messages but lacks actionable recovery steps or error classification. No tool annotations (readOnlyHint, etc.) despite all tools being read-only. Composition is sound (single responsibility per tool), but chaining support is weak, tools don't consistently return IDs needed for downstream calls.
Analyze sponsor tracks and prizes for a hackathon. Returns track names, sponsors, prize info, and winner counts per track.
Analyze the tech stacks used by winning projects of a hackathon. Returns frequency counts and the most common technologies.
Check if a project idea already exists on Devpost. Searches for similar projects and returns top matches with details including prizes won and tech stack.
Compare two hackathons side by side. Returns participants, prizes, winner counts, top technologies, and shared/unique tech stacks.
Get winning projects from a specific hackathon on Devpost. Provide the hackathon slug (e.g., 'hackillinois-2026').
Get full details of a Devpost project including description, tech stack, team, prizes, demo video, and GitHub link.
No output schemas documented. Tools return JSON text but LLMs cannot infer field names, types, or structure. Agents cannot plan downstream calls or extract specific fields reliably.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). All 10 tools are read-only but this is not declared in the schema, forcing LLMs to infer safety from descriptions alone.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 54 | 2026-07-28+ | v2 |
Analyze a winning project's submission structure as a template. Returns sections, word counts, and formatting patterns.
Search for hackathons on Devpost. Returns name, URL, dates, participant count, prizes, and status.
Search across all Devpost projects. Returns name, tagline, URL, hackathon, tech stack, and likes.
Analyze trending technologies across multiple hackathons. Returns the most common tech stacks, frequency counts, and example projects.
Error messages are generic text ('Error searching hackathons: ...') with no recovery guidance. LLMs cannot determine if errors are retryable, user-fixable, or fatal.
Parameter descriptions lack format constraints. 'hackathon_slug' says 'e.g. hackillinois-2026' but no regex, length limits, or character restrictions stated. LLMs may pass invalid slugs.
No pagination support visible. Tools like search_hackathons and search_projects may return large result sets but lack limit, offset, or cursor parameters. Results could exhaust context window.