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

app.aplusz/flight-fares

https://aplusz.app

Registry code: 8ce17eaa4cab58ef

api record

Cheapest observed flight fares between cities. Prices are cached snapshots, never live quotes - present them as last observed and link the user to live_check_url before they book. Full brief: https://aplusz.app/llms-full.txt

endpoint
https://aplusz.app/mcp
door code
e3613f235668a1c4
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 app.aplusz/flight-fares live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is app.aplusz/flight-fares free to use?
Yes — the hub reached it with no key and no payment.
What tools does app.aplusz/flight-fares have?
3 tools: find_cheapest_fare, list_routes_from, resolve_city.
Is app.aplusz/flight-fares 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
99.7%

90 days 99.2%· all time 99.2%

latency
131ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1412 checks · signed record
  • degraded → live
  • live → degraded· fetch failed
  • degraded → live
  • live → degraded· endpoint unreachable (timeout after 20000ms); card still served
  • degraded → live
_ what it is for
used for
  • find the cheapest observed flight fare between cities
  • list destinations from an origin by price
  • resolve a city name to an airport code
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.

  • find_cheapest_fare reads unknown 2h ago

    Returns the cheapest observed one-way fare between two cities, plus the six-month low and the departure date on which the low was observed. Use whenever the user names an origin and a destination and asks about price, the cheapest date to fly, or whether a fare is a good deal. Both arguments are required; neither alone produces a valid answer. Answers are directional and per pair - PAR to BKK is not BKK to PAR and is not PAR to SIN. Prices are cached snapshots, never live quotes: say "last observed", never "current price", and surface live_check_url to any user about to book.

    mcp-tool

    {
      "type": "object",
      "required": [
        "from",
        "to"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "Destination city. Uppercase IATA city code such as BKK. Must differ from from."
        },
        "from": {
          "type": "string",
          "description": "Origin city. Uppercase IATA city code such as PAR. A city slug such as paris also resolves. If you cannot resolve the city, call resolve_city first - do not guess a code."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • list_routes_from reads unknown 2h ago

    Returns destinations reachable from one origin, sorted cheapest first. Use when the user asks where they can fly cheaply from a city, or wants inspiration rather than one specific pair. One call replaces dozens of page fetches. Prices are cached snapshots.

    mcp-tool

    {
      "type": "object",
      "required": [
        "from"
      ],
      "properties": {
        "from": {
          "type": "string",
          "description": "Origin city. Uppercase IATA city code such as LON."
        },
        "limit": {
          "type": "integer",
          "maximum": 200,
          "minimum": 1,
          "description": "How many destinations to return, 1-200. Default 40."
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • resolve_city reads unknown never probed

    Turns a spoken city name into the uppercase IATA city code the other tools expect. Call this before find_cheapest_fare whenever you are not certain of a code. Do not invent codes.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "City name or partial name, e.g. \"sao paulo\"."
        }
      },
      "additionalProperties": false
    }
    arguments 13 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 8ce17eaa4cab58ef.

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

_ also on aplusz.app 7 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.