io.github.youthtrouble/keep-dawdling
Registry code: 8c74272864ac0ee4
Cache-only National Rail answers. Preserve citation_url, attribution, all freshness and coverage qualifications. Plans, routed, at-platform, usual and last-known values are not reported platforms or permission to board. Unlisted does not mean no later trains. Check the station board and announcements.
- endpoint
- https://keep.dawdl.ing/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is io.github.youthtrouble/keep-dawdling live?
- Yes — it answered the hub's last check (checked 10h ago). It answered 100% of checks over the last 30 days.
- Is io.github.youthtrouble/keep-dawdling free to use?
- Not measured yet.
- What tools does io.github.youthtrouble/keep-dawdling have?
- 4 tools: list_stations, get_departures, next_train, platform_for.
- Is io.github.youthtrouble/keep-dawdling safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 4 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_stations unknown never probed
List the 16 supported UK stations and canonical URLs.
{ "type": "object", "required": [], "properties": {}, "additionalProperties": false }arguments 6 linesget_departures unknown never probed
Read up to 20 eligible departures from a cached board. Cold caches are unavailable; preserve freshness, coverage and attribution.
{ "type": "object", "required": [ "station" ], "properties": { "station": { "type": "string", "maxLength": 80, "minLength": 1, "description": "Supported station CRS, slug or catalogue name. Call list_stations for the finite catalogue." } }, "additionalProperties": false }arguments 15 linesnext_train unknown never probed
Next listed eligible cached train from one catalogue station to another, terminating or calling there. No journey planning or completeness guarantee.
{ "type": "object", "required": [ "from", "to" ], "properties": { "to": { "type": "string", "maxLength": 80, "minLength": 1, "description": "Supported station CRS, slug or catalogue name. Call list_stations for the finite catalogue." }, "from": { "type": "string", "maxLength": 80, "minLength": 1, "description": "Supported station CRS, slug or catalogue name. Call list_stations for the finite catalogue." } }, "additionalProperties": false }arguments 22 linesplatform_for unknown never probed
Qualified platform sentence for an exact cached service_id at a station. Plans and history are never reports.
{ "type": "object", "required": [ "station", "service_id" ], "properties": { "station": { "type": "string", "maxLength": 80, "minLength": 1, "description": "Supported station CRS, slug or catalogue name. Call list_stations for the finite catalogue." }, "service_id": { "type": "string", "maxLength": 256, "minLength": 1 } }, "additionalProperties": false }arguments 21 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id8c74272864ac0ee4.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/8c74272864ac0ee4/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/8c74272864ac0ee4?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.