# C'est Chaud à Paris (remote · cestchaud.city)

Read-only Paris catalogue: events and dates, places, free things, booking links.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `cestchaud.city`: 79/100 (this document), [markdown](https://verifymcp.io/servers/city-cestchaud-paris/cestchaud.md), [page](https://verifymcp.io/servers/city-cestchaud-paris/cestchaud)

## Channel facts

- Endpoint: `https://cestchaud.city/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1243 tokens (~155/item across 8 items; 7 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the C'est Chaud à Paris MCP server?

C'est Chaud à Paris is a hosted endpoint at https://cestchaud.city/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 city-cestchaud-paris 'https://cestchaud.city/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "city-cestchaud-paris": {
      "url": "https://cestchaud.city/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "city-cestchaud-paris": {
      "type": "http",
      "url": "https://cestchaud.city/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.city-cestchaud-paris]
url = "https://cestchaud.city/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "city-cestchaud-paris": {
      "type": "remote",
      "url": "https://cestchaud.city/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add city-cestchaud-paris --url 'https://cestchaud.city/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  city-cestchaud-paris:
    url: "https://cestchaud.city/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "city-cestchaud-paris": {
      "Transport": "http",
      "Url": "https://cestchaud.city/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add city-cestchaud-paris -t streamable-http -u 'https://cestchaud.city/mcp'
```

### Other

```json
{
  "mcpServers": {
    "city-cestchaud-paris": {
      "type": "http",
      "url": "https://cestchaud.city/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-11-04 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 75, +1)

- [functional regression] Schema quality: 1062 → 1243
- [functional] New tool “esim_plans”

### 2026-10-26 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-25 (score 74)

First indexed and scored.

## MCP tools (7)

### `search_events` (~241 tokens)

Search Paris events

Finds dated events in Paris by time window, subject, price, free text or distance from a point. Returns each event with its page URL and, where we hold one, a booking link. Relaxes the window or radius when fewer than three events match, and says so in `relaxed`.

Input parameters:

- `date_from` (string): Paris day, YYYY-MM-DD.
- `date_to` (string): Paris day, YYYY-MM-DD. Inclusive. Defaults to date_from.
- `free` (boolean): Only events with free entry.
- `interests` (array): Filter by subject. Read the `interests` resource for the list.
- `limit` (integer): Defaults to 20.
- `locale` (string): Language for our own prose. Event titles and place names are never translated.
- `near` (object): Restrict to a radius around a point in the Paris area.
- `offset` (integer): For paging.
- `price_max` (number): Budget ceiling in EUR.
- `query` (string): Free text over title, venue and organiser.
- `when` (string): Time window. Mutually exclusive with date_from/date_to.

Output parameters:

- `attribution` (object): Who to credit and under what licence. The ODbL datasets behind most of this data require attribution wherever the data is used, including inside an answer you generate.
- `items` (array): The matching events, in the order we would show them.
- `match_count`: Matches across every page. Null means we could not determine it — never zero.
- `relaxed` (array): Empty when the search ran as asked. Otherwise the steps taken to find anything at all — tell the reader, because the answer is no longer exactly what they asked for.
- `total` (number): How many this response carries.
- `window`: The date window actually searched, after any relaxation.

### `get_event` (~96 tokens)

Get one Paris event

Returns one event by slug: its dates, venue, subject tags, our own description where we have written one, and a booking link where we hold an offer. Use it after search_events, or when you already have an event URL.

Input parameters:

- `locale` (string): Language for our own prose. The event's title is never translated.
- `slug` (string, required): The event's slug — the last path segment of its page URL.

Output parameters:

- `attribution` (object): Who to credit and under what licence. The ODbL datasets behind most of this data require attribution wherever the data is used, including inside an answer you generate.
- `event` (object): The event, with its full date list and venue resolved.

### `search_places` (~246 tokens)

Search Paris places

Finds cafés, parks, museums, pools, libraries and other places in Paris by kind, amenity, whether they are open now, or distance from a point. Each place carries how reliably it stays cool, what it suits, and its page URL.

Input parameters:

- `category` (string): Restrict to one kind of place.
- `free_entry` (boolean): Only places you can enter without paying.
- `good_for` (string): What the visitor wants to do there: work, study, shelter, family, quick_cool.
- `has_air_conditioning` (boolean): Only places with verified AC.
- `limit` (integer): Defaults to 20.
- `locale` (string): Language for our own prose. Place names are never translated.
- `near` (object): Sort by distance from a point in the Paris area instead of by arrondissement.
- `offset` (integer): For paging.
- `open_now` (boolean): Only places open at the time of the call.
- `power_outlets` (boolean): Only places with verified power sockets.
- `query` (string): Free text over name and address.
- `wifi` (boolean): Only places with verified wifi.

Output parameters:

- `attribution` (object): Who to credit and under what licence. The ODbL datasets behind most of this data require attribution wherever the data is used, including inside an answer you generate.
- `items` (array): The matching places, in the order we would show them.
- `match_count` (number): Matches across every page.
- `total` (number): How many this response carries.

### `get_place` (~91 tokens)

Get one Paris place

Returns one place by slug with its address, coordinates, amenities, opening hours and how reliably it stays cool, plus the nearest other places. Use it after search_places, or when you already have a place URL.

Input parameters:

- `locale` (string): Language for our own prose. The place's name is never translated.
- `slug` (string, required): The place's slug — the last path segment of its page URL.

Output parameters:

- `attribution` (object): Who to credit and under what licence. The ODbL datasets behind most of this data require attribution wherever the data is used, including inside an answer you generate.
- `nearby` (array): Other places within walking distance, nearest first — the next stop.
- `place` (object): The place, with its photo credit and opening hours where we hold them.

### `search_all` (~116 tokens)

Search everything in Paris

Searches events, activities, places and guides at once by name or text, for when the kind of thing is not known in advance. Each hit says which kind it is and carries the slug to pass to get_event or get_place.

Input parameters:

- `limit` (integer): Defaults to 20.
- `offset` (integer): For paging.
- `query` (string, required): What to look for. At least two characters — one matches most of the catalogue.
- `type` (string): Restrict to one kind. Omit to search everything.

Output parameters:

- `attribution` (object): Who to credit and under what licence. The ODbL datasets behind most of this data require attribution wherever the data is used, including inside an answer you generate.
- `counts` (object): How many matched per kind — useful for saying 'also 12 places' without a second call.
- `hits` (array): Matches across every kind, best first.
- `total` (number): How many this response carries.

### `moment_now` (~58 tokens)

What is on in Paris right now

Returns the seasonal or cultural moment currently running in Paris — Fashion Week, Christmas, a heatwave — with its hub URL and dates, or the city's seasonal mode when none is running.

Input parameters:

- `locale` (string): Language for titles and taglines.

Output parameters:

- `attribution` (object): Who to credit and under what licence. The ODbL datasets behind most of this data require attribution wherever the data is used, including inside an answer you generate.
- `card`: The next one alongside it, if any.
- `hero`: The moment currently taking over the home page, if any.
- `seasonal_default` (string): The city's mode when no moment is taking over. Always meaningful.

### `esim_plans` (~181 tokens)

France eSIM data plans

Returns prepaid eSIM data plans that work in France, for a given amount of data and trip length. Each plan carries its price with the date that price was checked, and a booking link. Relevant when a reader is travelling to Paris from outside the EU and needs mobile data on arrival.

Input parameters:

- `days` (number): How many days the trip lasts. Snaps to the nearest of 7, 15, 30; omit for 15.
- `gb` (number): Gigabytes wanted. Snaps to the nearest of 1, 3, 5, 10, 20, 50; omit for 10. Use `unlimited` instead for an unmetered plan.
- `locale` (string): Language for the disclosure wording.
- `unlimited` (boolean): Ask for unmetered plans instead of a size.

Output parameters:

- `approximate` (boolean): True when nothing matched the requested combination and these are the nearest plans instead. Say so when relaying them.
- `attribution` (object): Who to credit and under what licence. The ODbL datasets behind most of this data require attribution wherever the data is used, including inside an answer you generate.
- `country` (string): ISO 3166-1 alpha-2. Always FR — this is a Paris guide.
- `items` (array): Matching plans, best match first.
- `requested` (object): What was actually asked of the catalogue, after snapping.
- `total` (number): How many plans are in `items`.
- `unavailable` (boolean): True when the plan source could not be reached, or returned only prices too old to publish. An empty `items` with this false means there genuinely are none.
- `url` (string): The page a reader can open to do this themselves.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/city-cestchaud-paris/cestchaud#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 77
- 2026-10-31: 77
- 2026-10-30: 76
- 2026-10-29: 76
- 2026-10-28: 75
- 2026-10-27: 75
- 2026-10-26: 74
- 2026-10-25: 74

## Common questions

### What is the C'est Chaud à Paris MCP server?

C'est Chaud à Paris is an MCP server listed in the public MCP registry as city.cestchaud/paris. Read-only Paris catalogue: events and dates, places, free things, booking links. This page covers its hosted endpoint (https://cestchaud.city/mcp).

### Is the C'est Chaud à Paris MCP server safe to use?

C'est Chaud à Paris scores 79 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 C'est Chaud à Paris MCP server expose?

C'est Chaud à Paris exposes 7 tools: search_events, get_event, search_places, get_place, search_all, and 2 more. Their descriptions and schemas cost roughly 1,029 tokens of context every time the server is loaded.

### Does the C'est Chaud à Paris MCP server require authentication?

No. We connected to C'est Chaud à Paris without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the C'est Chaud à Paris MCP server still maintained?

C'est Chaud à Paris is still listed as active in the MCP registry. We last reached this channel on 5 November 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://cestchaud.city/mcp
- Website: https://cestchaud.city/for-agents
- Changelog RSS feed: https://verifymcp.io/servers/city-cestchaud-paris/cestchaud.xml
- Changelog JSON feed: https://verifymcp.io/servers/city-cestchaud-paris/cestchaud.json
- HTML version of this page: https://verifymcp.io/servers/city-cestchaud-paris/cestchaud