Unstop MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UNSTOP_MCP_TIMEOUT | No | Optional environment-driven runtime configuration for request timeout. | |
| UNSTOP_MCP_USER_AGENT | No | Optional environment-driven runtime configuration for the custom User-Agent header. | |
| UNSTOP_MCP_MAX_RETRIES | No | Optional environment-driven runtime configuration for max retries. | |
| UNSTOP_MCP_RETRY_DELAY | No | Optional environment-driven runtime configuration for retry delay. | |
| UNSTOP_MCP_DETAIL_DELAY | No | Optional environment-driven runtime configuration for delay between detail fetches. | |
| UNSTOP_MCP_GEOCACHE_PATH | No | Optional environment-driven runtime configuration for the geocode cache file path. | |
| UNSTOP_MCP_DETAIL_WORKERS | No | Optional environment-driven runtime configuration for the number of workers used for fetching details. | |
| UNSTOP_MCP_CACHE_TTL_SECONDS | No | Optional environment-driven runtime configuration for cache time-to-live in seconds. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_hackathonsC | Search Unstop hackathons with filters, sorting, pagination, and optional cache usage. |
| get_hackathon_detailsC | Fetch full details for a single Unstop hackathon by ID. |
| search_hackathons_by_locationC | Find offline Unstop hackathons within a radius of a city, address, or campus. |
| refresh_cacheB | Force an immediate refresh of the cached open hackathon dataset. |
| get_cache_infoB | Inspect cache freshness, TTL, and item counts for the open hackathon snapshot. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| find_relevant_hackathons | Guide an LLM through gathering preferences, calling search tools, and recommending hackathons. |
| compare_hackathons | Guide an LLM to compare multiple hackathons using the detail tool and resource views. |
| plan_hackathon_search | Guide an LLM on which Unstop MCP tools and resources to use for a discovery task. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| cache_info | Read-only cache metadata for the open hackathon snapshot. |
| open_hackathons_snapshot | Read-only snapshot of currently cached open hackathons. |
TDQS
Scored across 5 tools
Most tools have distinct purposes: get_cache_info inspects cache state, get_hackathon_details fetches a single hackathon, refresh_cache updates the cache, and search_hackathons searches with filters. However, search_hackathons and search_hackathons_by_location could cause some confusion as both search hackathons, though the latter is location-specific.
All tool names follow a consistent verb_noun pattern (e.g., get_cache_info, search_hackathons, refresh_cache). The naming is uniform and predictable, making it easy for an agent to understand the action and target.
With 5 tools, the server is well-scoped for managing hackathon data and cache operations. Each tool serves a clear purpose without being overly sparse or bloated, fitting typical MCP server ranges.
The tools cover core operations for hackathon data (search, get details) and cache management (info, refresh), but there are minor gaps such as no explicit tool for creating or updating hackathon data, which might be outside the server's read-only scope. Overall, it supports common workflows effectively.