# Keep Dawdling (remote · keep.dawdl.ing)

Cached UK train departures and qualified platforms, powered by National Rail Enquiries.

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

## Components

- remote · `keep.dawdl.ing`: 70/100 (this document), [markdown](https://verifymcp.io/servers/youthtrouble-keep-dawdling/keep.md), [page](https://verifymcp.io/servers/youthtrouble-keep-dawdling/keep)

## Channel facts

- Endpoint: `https://keep.dawdl.ing/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-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 286 tokens (~71/item across 4 items; 4 tools + 0 resources), lean.
  - 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**: 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Keep Dawdling MCP server?

Keep Dawdling is a hosted endpoint at https://keep.dawdl.ing/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 youthtrouble-keep-dawdling 'https://keep.dawdl.ing/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "youthtrouble-keep-dawdling": {
      "url": "https://keep.dawdl.ing/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "youthtrouble-keep-dawdling": {
      "type": "http",
      "url": "https://keep.dawdl.ing/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.youthtrouble-keep-dawdling]
url = "https://keep.dawdl.ing/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "youthtrouble-keep-dawdling": {
      "type": "remote",
      "url": "https://keep.dawdl.ing/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add youthtrouble-keep-dawdling --url 'https://keep.dawdl.ing/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  youthtrouble-keep-dawdling:
    url: "https://keep.dawdl.ing/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "youthtrouble-keep-dawdling": {
      "Transport": "http",
      "Url": "https://keep.dawdl.ing/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add youthtrouble-keep-dawdling -t streamable-http -u 'https://keep.dawdl.ing/mcp'
```

### Other

```json
{
  "mcpServers": {
    "youthtrouble-keep-dawdling": {
      "type": "http",
      "url": "https://keep.dawdl.ing/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-21 (score 70, +1)

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

### 2026-11-20 (score 69, 0)

- [security] Tool “get_departures” rewrote its description, which is the text the model reads
- [security] Tool “next_train” rewrote its description, which is the text the model reads

### 2026-11-19 (score 69, +1)

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

### 2026-11-16 (score 68, +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-11-14 (score 67, +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-11-12 (score 66, +1)

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

### 2026-11-11 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-10 (score 65)

First indexed and scored.

## MCP tools (4)

### `list_stations` (~20 tokens)

List the 16 supported UK stations and canonical URLs.

### `get_departures` (~63 tokens)

Read up to 20 eligible departures from a cached board, each with where it stops. Cold caches are unavailable; preserve freshness, coverage and attribution.

Input parameters:

- `station` (string, required): Supported station CRS, slug or catalogue name. Call list_stations for the finite catalogue.

### `next_train` (~85 tokens)

Next listed eligible cached train from one catalogue station to another, terminating or calling there, with where it stops. No journey planning or completeness guarantee.

Input parameters:

- `from` (string, required): Supported station CRS, slug or catalogue name. Call list_stations for the finite catalogue.
- `to` (string, required): Supported station CRS, slug or catalogue name. Call list_stations for the finite catalogue.

### `platform_for` (~60 tokens)

Qualified platform sentence for an exact cached service_id at a station. Plans and history are never reports.

Input parameters:

- `service_id` (string, required)
- `station` (string, required): Supported station CRS, slug or catalogue name. Call list_stations for the finite catalogue.

## Diagnostics

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

## Score history

- 2026-11-21: 70
- 2026-11-20: 69
- 2026-11-19: 69
- 2026-11-18: 68
- 2026-11-17: 68
- 2026-11-16: 68
- 2026-11-15: 67
- 2026-11-14: 67
- 2026-11-13: 66
- 2026-11-12: 66
- 2026-11-11: 65
- 2026-11-10: 65

## Common questions

### What is the Keep Dawdling MCP server?

Keep Dawdling is an MCP server listed in the public MCP registry as io.github.youthtrouble/keep-dawdling. Cached UK train departures and qualified platforms, powered by National Rail Enquiries. This page covers its hosted endpoint (https://keep.dawdl.ing/mcp).

### Is the Keep Dawdling MCP server safe to use?

Keep Dawdling scores 70 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 Keep Dawdling MCP server expose?

Keep Dawdling exposes 4 tools: list_stations, get_departures, next_train, platform_for. Their descriptions and schemas cost roughly 228 tokens of context every time the server is loaded.

### Does the Keep Dawdling MCP server require authentication?

No. We connected to Keep Dawdling without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Keep Dawdling MCP server still maintained?

Keep Dawdling is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Keep Dawdling MCP server?

VerifyMCP ran 12 checks on Keep Dawdling, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Keep Dawdling: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://keep.dawdl.ing/mcp
- Website: https://keep.dawdl.ing/developers
- Changelog RSS feed: https://verifymcp.io/servers/youthtrouble-keep-dawdling/keep.xml
- Changelog JSON feed: https://verifymcp.io/servers/youthtrouble-keep-dawdling/keep/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/youthtrouble-keep-dawdling/keep.json
- HTML version of this page: https://verifymcp.io/servers/youthtrouble-keep-dawdling/keep
