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

com.tieredtravel/travel

https://tieredtravel.com

Registry code: 2c8b61118a9a1c94

api record

Travel data for 100 cities at three budget tiers. Tools return catalogue figures, never estimates: an unknown city is an error, not a guess. Read the resources first if you are unsure which tool fits.

endpoint
https://tieredtravel.com/mcp
door code
50d6519db3f79672
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 com.tieredtravel/travel live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is com.tieredtravel/travel free to use?
Yes — the hub reached it with no key and no payment.
What tools does com.tieredtravel/travel have?
4 tools: compare_destinations, destination_costs, walking_route, find_destinations.
Is com.tieredtravel/travel 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
301ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • 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

_ what it can do 4 tools
1 open 3 never probed 1 of 4 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.

  • find_destinations open 1h ago

    List which cities this server knows about, optionally filtered by country, continent or a name fragment. Call this first when a city might not be covered — the other tools fail rather than guess.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "query": {
          "type": "string",
          "examples": [
            "Portugal",
            "Japan"
          ],
          "description": "Optional filter: a country, continent or name fragment. Omit for all 100."
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • compare_destinations unknown never probed

    Two cities side by side: daily cost at each tier, plus currency, language and best months to visit.

    mcp-tool

    {
      "type": "object",
      "required": [
        "cities"
      ],
      "properties": {
        "cities": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 2,
          "minItems": 2,
          "description": "Exactly two city names or slugs."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • destination_costs unknown never probed

    What a day costs in a city at budget, mid-range and luxury, broken down into accommodation, food, transport and activities, with the editorial overview for each tier. Figures come from a hand-written catalogue of 100 cities. If the city is not in the catalogue this returns an error — it never estimates.

    mcp-tool

    {
      "type": "object",
      "required": [
        "city"
      ],
      "properties": {
        "city": {
          "type": "string",
          "examples": [
            "lisbon",
            "barcelona"
          ],
          "description": "City name or slug, e.g. \"lisbon\" or \"Lisbon\"."
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • walking_route unknown never probed

    A curated stop-by-stop walking route for a city: each stop in order with what to know there, real coordinates, distance on foot and total time. Distance excludes tram, metro and ferry legs, which are flagged separately. Nine cities deliberately have no route because a self-guided walk is the wrong format there.

    mcp-tool

    {
      "type": "object",
      "required": [
        "city"
      ],
      "properties": {
        "city": {
          "type": "string",
          "examples": [
            "lisbon"
          ],
          "description": "City name or slug."
        },
        "hours": {
          "enum": [
            3,
            6,
            12
          ],
          "type": "integer",
          "description": "Optional route length. Only 3, 6 and 12 exist; omit to get whatever the city has."
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
_ try it over mcp 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 2c8b61118a9a1c94.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/2c8b61118a9a1c94/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/2c8b61118a9a1c94/badge.svg)](https://brick.blue/agent/2c8b61118a9a1c94?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 knowoff the mcp door
card completeness
80%

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.