_ registry / mcp streamable-http · checked 1h ago

citizen01-bahn-x402

https://bahn.1f916.de

Registry code: ee152cd8e608d62e

api record

Rail re-planning for a traveller already on a delayed train. Workflow: search_stations -> departures -> plan_transfer. The first two are free; plan_transfer costs 1 USDC-cent per call via x402 on Base. Call it unpaid to receive the PaymentRequired object, then retry with the payment payload in params._meta['x402/payment'].

endpoint
https://bahn.1f916.de/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 it live, free and safe measured by this hub
Is citizen01-bahn-x402 live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is citizen01-bahn-x402 free to use?
Yes — the hub reached it with no key and no payment.
What tools does citizen01-bahn-x402 have?
3 tools: plan_transfer, departures, search_stations.
Is citizen01-bahn-x402 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.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
103ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 classified

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.

  • plan_transfer unknown never probed

    PAID (x402 exact/EVM, 1 USDC-cent per call). Re-plan a journey for a traveller already on a delayed train: per-stop transfer buffer, onward connections with arrival times, and one safe recommendation. Call it without payment to receive the PaymentRequired object; retry with the payment payload in params._meta['x402/payment'].

    mcp-tool

    {
      "type": "object",
      "required": [
        "trip_id",
        "to"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "Destination stop_id from search_stations."
        },
        "trip_id": {
          "type": "string",
          "description": "trip_id from departures."
        },
        "min_buffer": {
          "type": "integer",
          "default": 8,
          "minimum": 0,
          "description": "Minimum transfer buffer in minutes."
        },
        "manual_delay": {
          "type": "integer",
          "description": "Known delay in minutes, if the feed has none."
        }
      }
    }
    arguments 27 lines
  • departures unknown 1h ago

    Free. Upcoming departures at a stop_id, with trip_id, line, scheduled/actual time and current delay. Use trip_id as 'trip_id' in plan_transfer for the train the traveller is already on.

    mcp-tool

    {
      "type": "object",
      "required": [
        "station"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 30,
          "minimum": 1
        },
        "station": {
          "type": "string",
          "description": "stop_id from search_stations."
        }
      }
    }
    arguments 18 lines
  • search_stations unknown 1h ago

    Free. Resolve a station or city name to a stop_id. A bare city name resolves to that city's main rail hub only when exactly one candidate exists; the answer then carries a 'resolution' object naming the rule, the chosen station and the rejected alternatives. Use the returned stop_id as 'to' in plan_transfer.

    mcp-tool

    {
      "type": "object",
      "required": [
        "q"
      ],
      "properties": {
        "q": {
          "type": "string",
          "description": "Station or city name, e.g. 'Leipzig Hbf'."
        },
        "limit": {
          "type": "integer",
          "default": 5,
          "maximum": 20,
          "minimum": 1
        }
      }
    }
    arguments 18 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ee152cd8e608d62e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ee152cd8e608d62e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ee152cd8e608d62e/badge.svg)](https://brick.blue/agent/ee152cd8e608d62e?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.

_ how we know
card completeness
70%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.