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

planetrack

https://planetrack.ai

Registry code: ff530f8f44316aca

api record

Live and historical flight data from PlaneTrack (planetrack.ai), built on its own ADS-B receiver network and FAA schedule data. Use flight_status for a flight in the air now, flight_on_date for 'was my flight late' within the last 7 days, airport_board for departures and arrivals, aircraft_info for a registration or Mode-S hex, aircraft_overhead for what is flying over a place. Those five need no key. The other tools are for developers and use credits on a PlaneTrack API key (free keys: 2,000 credits a month at https://planetrack.ai/pricing.html#api). Always give the user the planetrack.ai…

endpoint
https://planetrack.ai/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 planetrack live?
Yes — it answered the hub's last check (checked 6h ago). It answered 100% of checks over the last 30 days.
Is planetrack free to use?
Yes — the hub reached it with no key and no payment.
What tools does planetrack have?
10 tools: live_aircraft_near, flight_history, flight_reliability, flight_on_date, aircraft_track, overhead_summary, aircraft_overhead, flight_status, ….
Is planetrack 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
634ms

last good check

priced tools
0

of 10 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. 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 10 tools
2 open 8 never probed 2 of 10 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.

  • aircraft_info open 6h ago

    An aircraft by registration (e.g. N12345, G-EUPT) or Mode-S hex (e.g. a1b2c3): type, operator, where it is now if flying, and its flights in the last 7 days. Free, no key.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ident"
  ],
  "properties": {
    "ident": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • airport_board open 6h ago

    Live departures and arrivals board for an airport (ICAO like KJFK or IATA like JFK): flight, other airport, status, time. Free, no key.

    mcp-tool

    {
  "type": "object",
  "required": [
    "airport"
  ],
  "properties": {
    "airport": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • live_aircraft_near unknown never probed

    Aircraft currently airborne within radius_km of a latitude/longitude, nearest first, with callsign, altitude, heading, speed and type. 10 credits.

    mcp-tool

    {
  "type": "object",
  "required": [
    "lat",
    "lon"
  ],
  "properties": {
    "lat": {
      "type": "number"
    },
    "lon": {
      "type": "number"
    },
    "limit": {
      "type": "integer",
      "default": 50,
      "maximum": 200,
      "minimum": 1
    },
    "radius_km": {
      "type": "number",
      "default": 50,
      "maximum": 300,
      "minimum": 1
    }
  }
}
    arguments 27 lines
  • flight_history unknown never probed

    Past legs of a flight number/callsign as flown (e.g. UAL1, BAW117): dates, airports, times, aircraft. 20 credits.

    mcp-tool

    {
  "type": "object",
  "required": [
    "callsign"
  ],
  "properties": {
    "days": {
      "type": "integer",
      "default": 30,
      "maximum": 3650,
      "minimum": 1
    },
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 100,
      "minimum": 1
    },
    "callsign": {
      "type": "string"
    }
  }
}
    arguments 23 lines
  • flight_reliability unknown never probed

    On-time performance for a flight number, a route (e.g. KJFK-KLAX or JFK-LAX) or a departure airport over the last 7 to 90 days (US airspace, FAA SWIM). Give exactly one of flight, route, airport. 20 credits.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "days": {
      "type": "integer",
      "default": 30,
      "maximum": 90,
      "minimum": 7
    },
    "route": {
      "type": "string"
    },
    "flight": {
      "type": "string"
    },
    "airport": {
      "type": "string"
    }
  }
}
    arguments 20 lines
  • flight_on_date unknown never probed

    What happened to a flight on a given day within the last 7 days: departure and arrival airports, scheduled and actual take-off, delay in minutes, status, aircraft. Free, no key. Older dates: point the user to the flight record at the returned link.

    mcp-tool

    {
  "type": "object",
  "required": [
    "callsign",
    "date"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "UTC date, YYYY-MM-DD"
    },
    "callsign": {
      "type": "string",
      "description": "ICAO callsign, e.g. UAL1"
    }
  }
}
    arguments 17 lines
  • aircraft_track unknown never probed

    Positions of one aircraft (Mode-S hex, e.g. a1b2c3) over the last minutes (5 to 1440). 20 credits.

    mcp-tool

    {
  "type": "object",
  "required": [
    "icao24"
  ],
  "properties": {
    "icao24": {
      "type": "string"
    },
    "minutes": {
      "type": "integer",
      "default": 720,
      "maximum": 1440,
      "minimum": 5
    }
  }
}
    arguments 17 lines
  • overhead_summary unknown never probed

    How many aircraft passed within km of a point over the last 1 to 3 days: passes per day, lowest pass, busiest hour (UTC), night passes, types, operators, rarest visitor. 20 credits.

    mcp-tool

    {
  "type": "object",
  "required": [
    "lat",
    "lon"
  ],
  "properties": {
    "km": {
      "type": "number",
      "default": 3,
      "maximum": 10,
      "minimum": 1
    },
    "lat": {
      "type": "number"
    },
    "lon": {
      "type": "number"
    },
    "days": {
      "type": "integer",
      "default": 1,
      "maximum": 3,
      "minimum": 1
    }
  }
}
    arguments 27 lines
  • aircraft_overhead unknown 6h ago

    Aircraft flying right now within radius_km (max 30) of a latitude/longitude, nearest first: callsign, type, altitude, speed. Free, no key.

    mcp-tool

    {
  "type": "object",
  "required": [
    "lat",
    "lon"
  ],
  "properties": {
    "lat": {
      "type": "number"
    },
    "lon": {
      "type": "number"
    },
    "radius_km": {
      "type": "number",
      "default": 15,
      "maximum": 30,
      "minimum": 1
    }
  }
}
    arguments 21 lines
  • flight_status unknown never probed

    Live status of a flight that is in the air now, by callsign or flight number as broadcast (e.g. UAL1, BAW117, DAL2540): route, progress, altitude, speed and estimated arrival. Free, no key.

    mcp-tool

    {
  "type": "object",
  "required": [
    "callsign"
  ],
  "properties": {
    "callsign": {
      "type": "string",
      "description": "ICAO callsign, e.g. UAL1"
    }
  }
}
    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 ff530f8f44316aca.

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

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.