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

airport-facts

https://airport-facts.mnpi.workers.dev

Registry code: 10052a70b757c521

api record

Airport facts from OurAirports (public domain): codes, location, runways, frequencies and official links for 9,900+ open airports. Use find_airports for "which airport serves X" or "what is the code of X airport", lookup_airport for a known code, nearest_airports for coordinates. There is no live flight, delay or parking data: point users to the airport website (home_link) for that.

endpoint
https://airport-facts.mnpi.workers.dev/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 airport-facts live?
Yes — it answered the hub's last check (checked 21h ago). It answered 100% of checks over the last 30 days.
Is airport-facts free to use?
Yes — the hub reached it with no key and no payment.
What tools does airport-facts have?
3 tools: find_airports, nearest_airports, lookup_airport.
Is airport-facts 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
673ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 2 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.

  • find_airports unknown 21h ago

    Which airports serve a city or town, or what is the code of an airport by name? Returns matching airports (scheduled-service and larger first) with IATA/ICAO codes, city, region, country and coordinates. For a town (34,000 towns over 15k people) with no scheduled-service airport of its own, also returns the nearest airports that have scheduled flights, with distances. Use "City, Country" or the country argument to disambiguate (e.g. "Cambridge, NZ" vs "Cambridge, GB").

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "City, town or airport name, e.g. \"Auckland\", \"Cambridge, New Zealand\", \"Heathrow\"."
        },
        "country": {
          "type": "string",
          "description": "Optional. ISO 3166-1 alpha-2 code or English country name."
        }
      }
    }
    arguments 16 lines
  • nearest_airports unknown 21h ago

    The nearest airports to a latitude/longitude, with straight-line distance in km. By default only airports with scheduled airline service (an IATA code or medium/large size, not heliports); set scheduled_only to false to include all open airports in the dataset.

    mcp-tool

    {
      "type": "object",
      "required": [
        "latitude",
        "longitude"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "How many (default 5)."
        },
        "latitude": {
          "type": "number"
        },
        "longitude": {
          "type": "number"
        },
        "scheduled_only": {
          "type": "boolean",
          "description": "Only airports with scheduled service (default true)."
        }
      }
    }
    arguments 25 lines
  • lookup_airport unknown 21h ago

    Facts about one airport from its IATA code (e.g. AKL, LHR, JFK), ICAO code (e.g. NZAA, EGLL) or OurAirports ident: full name, city, region, country, coordinates, elevation, type, whether it has scheduled airline service, runways (length, surface, lighting), radio frequencies, and links to the official website and Wikipedia. 9,900+ open airports worldwide. No live flight status.

    mcp-tool

    {
      "type": "object",
      "required": [
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "description": "IATA (3 letters), ICAO (4 characters) or OurAirports ident."
        }
      }
    }
    arguments 12 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 10052a70b757c521.

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