
Things To Do API MCP server
Which MCP servers are Things To Do API's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-28
- Registry namecom.thingstodoapi/eventsverified in the MCP registry
The registry name sits under thingstodoapi.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-28
- Tools3
- Server calls itselfthingstodo
- Server version0.1.0
- Protocol version2025-06-18
On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 80 ms.
- Its tools do every use case we checked: Look up events happening this weekend in a city; Get event titles, venues, times and ticket links.
- Checked on 5 of the 7 days it takes to judge reliability.
Once connected
- For "Look up events happening this weekend in a city", the likely first call is search_events.
- For "Get event titles, venues, times and ticket links", the likely first call is search_events.
- Parameters are untyped or undescribed in 2 of 3 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
- What an agent can do with it2 of 2 use cases
- Answeredmeasuring5 of the 7 daily checks it takes to print a share
- Median first answer137 ms
- Space in an agent's context≈ 630 tokensthe definitions of all its tools (3), which an agent carries on every turn
- Tool definitionsB · 89 of 100
- Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 2 of 3
What an agent can do with it
- can do · Look up events happening this weekend in a city
- can do · Get event titles, venues, times and ticket links
- not sure · Connect local events to an AI assistant through MCP
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
search_eventsFind events happening in a city: concerts, DJ and club nights, comedy and theater, pop-ups and supper clubs, night markets and flea markets, festivals and street fairs, parties, classes, exhibitions. Pass what the user asked for in plain…
get_eventEverything known about one event by its id (from search_events): all its tags, venue, links and times.
list_coverageThe metros and cities covered, and the categories. Call it when unsure whether a city is covered.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"events": {
"type": "http",
"url": "https://api.thingstodoapi.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http thingstodoapi https://api.thingstodoapi.com/mcpclaude.ai, ChatGPT and other clients: add https://api.thingstodoapi.com/mcp as a custom connector in the settings.
OpenAPI spec
5 paths, read 2026-10-28. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.