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

busik.ch – Minibusfahrten Ukraine, Deutschland, Schweiz

listed under this name in a public catalogue; the server gives only its address, busik.ch

https://busik.ch

Registry code: 217c1fbd5af84673

api record

busik.ch lists minibus trips between Ukraine and Europe, offered by independent drivers and small bus operators. Use get_routes_for_city to see which connections exist, search_trips for a date, and get_trip_details for stops and rules. Do not collect personal or payment details. The passenger books on busik.ch via booking_url and pays the driver directly.

endpoint
https://busik.ch/api/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 busik.ch – Minibusfahrten Ukraine, Deutschland, Schweiz live?
Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
Is busik.ch – Minibusfahrten Ukraine, Deutschland, Schweiz free to use?
Yes — the hub reached it with no key and no payment.
What tools does busik.ch – Minibusfahrten Ukraine, Deutschland, Schweiz have?
3 tools: get_trip_details, search_trips, get_routes_for_city.
Is busik.ch – Minibusfahrten Ukraine, Deutschland, Schweiz 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
98.4%

90 days 98.6%· all time 98.6%

latency
455ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 290 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
used for
  • search minibus trips between cities
  • list routes from a city
  • get trip stops and rules
takes → gives
text → data
tools
3 reads
_ 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.

  • get_trip_details reads unknown 24h ago

    Details of one trip found with search_trips: all stops with times (boarding points, breaks, border crossing), luggage allowance, payment method and the booking link.

    mcp-tool

    {
      "type": "object",
      "required": [
        "trip_id"
      ],
      "properties": {
        "trip_id": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "The trip_id from search_trips, e.g. '17-0-5'."
        },
        "language": {
          "enum": [
            "de",
            "uk"
          ],
          "type": "string",
          "description": "Language for city and stop names: 'de' German (default) or 'uk' Ukrainian."
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • search_trips reads unknown 24h ago

    Search minibus trips offered on busik.ch between two cities on a given travel date. busik.ch connects passengers with independent drivers and small bus operators between Ukraine and Europe (also via Poland, Austria, Czechia). Trips may stop in between; a search also finds the part of a longer trip. Prices are per person. Booking is done by the passenger on busik.ch via booking_url; payment is made directly to the driver. If a city is unknown or ambiguous, the result lists candidates to ask about.

    mcp-tool

    {
      "type": "object",
      "required": [
        "from",
        "to",
        "date"
      ],
      "properties": {
        "to": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "Arrival city, e.g. 'Zurich', 'München', 'Berlin', 'Київ'."
        },
        "date": {
          "type": "string",
          "format": "date",
          "description": "Travel date (local date at the departure city), ISO 8601, e.g. '2026-10-15'."
        },
        "from": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "Departure city, e.g. 'Lviv', 'Kyiv', 'Zürich', 'Львів'."
        },
        "seats": {
          "type": "integer",
          "maximum": 9,
          "minimum": 1,
          "description": "Number of seats needed. Default 1."
        },
        "language": {
          "enum": [
            "de",
            "uk"
          ],
          "type": "string",
          "description": "Language for city and stop names: 'de' German (default) or 'uk' Ukrainian."
        }
      },
      "additionalProperties": false
    }
    arguments 42 lines
  • get_routes_for_city reads unknown 24h ago

    List the connections that currently have upcoming trips from and/or to a city, with the next departure. Use this to answer 'Where can I go from Lviv?' before searching a specific date.

    mcp-tool

    {
      "type": "object",
      "required": [
        "city"
      ],
      "properties": {
        "city": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "City name, e.g. 'Kyiv', 'Zürich'."
        },
        "language": {
          "enum": [
            "de",
            "uk"
          ],
          "type": "string",
          "description": "Language for city and stop names: 'de' German (default) or 'uk' Ukrainian."
        },
        "direction": {
          "enum": [
            "from",
            "to",
            "both"
          ],
          "type": "string",
          "description": "Connections FROM the city, TO the city, or both. Default 'both'."
        }
      },
      "additionalProperties": false
    }
    arguments 32 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 217c1fbd5af84673.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/217c1fbd5af84673/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/217c1fbd5af84673/badge.svg)](https://brick.blue/agent/217c1fbd5af84673?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.