# Things To Do API (remote · api.thingstodoapi.com)

Search local events in plain words: shows, pop-ups, markets, classes, with times, venues, prices.

- Trust score: 57/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `api.thingstodoapi.com`: 57/100 (this document), [markdown](https://verifymcp.io/servers/com-thingstodoapi-events/api.md), [page](https://verifymcp.io/servers/com-thingstodoapi-events/api)

## Channel facts

- Endpoint: `https://api.thingstodoapi.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 511 tokens (~170/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Things To Do API MCP server?

Things To Do API is a hosted endpoint at https://api.thingstodoapi.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-thingstodoapi-events 'https://api.thingstodoapi.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-thingstodoapi-events": {
      "url": "https://api.thingstodoapi.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-thingstodoapi-events": {
      "type": "http",
      "url": "https://api.thingstodoapi.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-thingstodoapi-events]
url = "https://api.thingstodoapi.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-thingstodoapi-events": {
      "type": "remote",
      "url": "https://api.thingstodoapi.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-thingstodoapi-events --url 'https://api.thingstodoapi.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-thingstodoapi-events:
    url: "https://api.thingstodoapi.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-thingstodoapi-events": {
      "Transport": "http",
      "Url": "https://api.thingstodoapi.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-thingstodoapi-events -t streamable-http -u 'https://api.thingstodoapi.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-thingstodoapi-events": {
      "type": "http",
      "url": "https://api.thingstodoapi.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-18 (score 57, 0)

- [security] Tool “search_events” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “search_events” reworded the description of “query”

### 2026-10-17 (score 57)

First indexed and scored.

## MCP tools (3)

### `search_events` (~379 tokens)

Search local events

Find 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 words as `query` ("techno this weekend in Oakland", "spooky things to do friday", "farmers market sunday morning"); time and place in the words are understood. Say who it is for in the same words ("comedy this weekend for my parents, they hate crowds", "things to do with my kids saturday"): what suits them comes first. Use `from`/`to`, `place` or `near` when you already know them exactly. Returns events with start times in the local timezone, the venue, a summary, tags, ticket and source links, and why each matched. Covers the San Francisco Bay Area today; a place outside it comes back as not covered, with no events. For more, call again with the `offset` a search returns as next_offset.

Input parameters:

- `categories` (array): Only these categories.
- `from` (string): ISO 8601 start of the window. Overrides any time in the query.
- `limit` (number): How many events, 1 to 50, default 10.
- `near` (object): A point to search around.
- `offset` (number): Skip this many, for the next page: pass the next_offset a search returned.
- `place` (string): A city or neighborhood by name, e.g. "Oakland", "the Mission".
- `query` (string): What to find, in plain words. May include when, where, and who it is for.
- `sort` (string)
- `to` (string): ISO 8601 end of the window.

### `get_event` (~38 tokens)

One event in full

Everything known about one event by its id (from search_events): all its tags, venue, links and times.

Input parameters:

- `id` (string, required)

### `list_coverage` (~29 tokens)

Where events are covered

The metros and cities covered, and the categories. Call it when unsure whether a city is covered.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-thingstodoapi-events/api#diagnostics

## Score history

- 2026-10-18: 57
- 2026-10-17: 57

## Common questions

### What is the Things To Do API MCP server?

Things To Do API is an MCP server listed in the public MCP registry as com.thingstodoapi/events. Search local events in plain words: shows, pop-ups, markets, classes, with times, venues, prices. This page covers its hosted endpoint (https://api.thingstodoapi.com/mcp).

### Is the Things To Do API MCP server safe to use?

Things To Do API scores 57 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Things To Do API MCP server expose?

Things To Do API exposes 3 tools: search_events, get_event, list_coverage. Their descriptions and schemas cost roughly 446 tokens of context every time the server is loaded.

### Does the Things To Do API MCP server require authentication?

No. We connected to Things To Do API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Things To Do API MCP server still maintained?

Things To Do API is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.thingstodoapi.com/mcp
- Website: https://thingstodoapi.com/docs/
- Changelog RSS feed: https://verifymcp.io/servers/com-thingstodoapi-events/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-thingstodoapi-events/api.json
- HTML version of this page: https://verifymcp.io/servers/com-thingstodoapi-events/api