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

dev.workers.quietworklabs.faa-x402/faa-airport-status

https://faa-x402.quietworklabs.workers.dev

Registry code: 123fa0badaf39176

api record

Live US airport disruption data parsed from the FAA NAS Status feed: ground stops, ground delay programs, arrival/departure delays and closures. Use airport_status for one airport (IATA like JFK or ICAO like KJFK) and us_airport_disruptions for every current disruption ranked by severity (5 ground stop/closure, 3-4 ground delay program or long delays, 2 delays). Data is cached up to 60s. Not for operational flight planning.

endpoint
https://faa-x402.quietworklabs.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 dev.workers.quietworklabs.faa-x402/faa-airport-status live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is dev.workers.quietworklabs.faa-x402/faa-airport-status free to use?
Yes — the hub reached it with no key and no payment.
What tools does dev.workers.quietworklabs.faa-x402/faa-airport-status have?
2 tools: airport_status, us_airport_disruptions.
Is dev.workers.quietworklabs.faa-x402/faa-airport-status 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
157ms

last good check

priced tools
0

of 2 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, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 4 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
1

distinct

settlements
1

last 2026-10-18

received on chain
0.001 USDC

counted from three payers (thin, concentrated, shared-payto)

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

  • us_airport_disruptions open 2h ago

    Every current FAA disruption in US airspace (ground stops, ground delay programs, delays, closures) ranked by severity. Price: $0.003 USDC per call via x402 (Base); the first 5 calls per day per client are free.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "minSeverity": {
      "type": "integer",
      "maximum": 5,
      "minimum": 1,
      "description": "Only events with severity >= this. Default 2."
    }
  }
}
    arguments 11 lines
  • airport_status unknown 2h ago

    Current FAA status for one US airport: normal, advisory or disrupted, max severity (0-5) and each active event (ground stop, ground delay program with average/max delay, arrival/departure delays, closure). Price: $0.002 USDC per call via x402 (Base); the first 5 calls per day per client are free.

    mcp-tool

    {
  "type": "object",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "US airport IATA (EWR) or ICAO (KEWR) code"
    }
  }
}
    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 123fa0badaf39176.

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

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.