RecallChecker — Vehicle Safety Recalls vs Fr24api MCP

A side-by-side look at the RecallChecker — Vehicle Safety Recalls and Fr24api MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

RecallChecker — Vehicle Safety Recalls logoRecallChecker — Vehicle Safety RecallsTravel & Transportation · Remote HTTP/SSECheck U.S. NHTSA vehicle safety recall campaigns by make, model, and year. Live official data.52GoodAuth: not declaredFr24api MCP logoFr24api MCPTravel & Transportation · Local subprocess (stdio)MCP server providing access to the Flightradar24 API for real-time and historical flight data56GoodAuth: api key required

Verdict: choose RecallChecker — Vehicle Safety Recalls for travel & transportation work over a hosted endpoint; choose Fr24api MCP for travel & transportation as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

RecallChecker — Vehicle Safety Recalls logoChoose RecallChecker — Vehicle Safety Recalls when

  • You need dedicated capabilities in the Travel & Transportation domain.
  • You prefer a remote HTTP/SSE transport.
  • You want tools like check_vehicle_recalls.
Explore RecallChecker — Vehicle Safety Recalls

Fr24api MCP logoChoose Fr24api MCP when

  • You need dedicated capabilities in the Travel & Transportation domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: FR24_API_KEY.
  • You want tools like get_live_flights_positions_light, get_live_flights_positions_full, get_live_flights_count.
Explore Fr24api MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecRecallChecker — Vehicle Safety Recalls logoRecallChecker — Vehicle Safety RecallsFr24api MCP logoFr24api MCP
CategoryTravel & TransportationTravel & Transportation
Quality signal52/100 · Good56/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredBYOK (pay the provider)
Required env varsNone listedFR24_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars030
Directory activity 4 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools113

Tools & capabilities

RecallChecker — Vehicle Safety Recalls tools 1

  • check_vehicle_recallsCheck U.S. NHTSA safety recall campaigns for a vehicle by make, model, and model year. Returns official NHTSA recall campaigns (component, hazard, remedy, campaign number, official notice link) plus the date the data was fetched. Results are model-year campaign matches, NOT VIN-specific repair status — an empty result means no open recalls were found in NHTSA as of the returned date, which is not a guarantee the vehicle is safe.

Fr24api MCP tools 13

  • get_live_flights_positions_lightGet real-time aircraft positions with basic information.
  • get_live_flights_positions_fullGet real-time aircraft positions with comprehensive flight details.
  • get_live_flights_countGet count of live flights matching criteria.
  • get_historic_flights_positions_fullGet historical flight positions with full details.
  • get_historic_flights_positions_lightGet historical flight positions with basic information.
  • get_historic_flights_countGet count of historical flights.
  • get_flight_summary_fullGet comprehensive flight takeoff/landing information.
  • get_flight_summary_lightGet essential flight takeoff/landing information.
  • get_flight_summary_countGet count of flights in summary query.
  • get_flight_tracksGet detailed positional tracks for a specific flight.
  • get_airline_infoGet airline information by ICAO code.
  • get_airport_info_lightGet basic airport information.
  • +1 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

RecallChecker — Vehicle Safety Recalls

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "recallchecker-vehicle-safety-recalls": {
      "url": "https://mcp.checkrecall.com/mcp"
    }
  }
}

Fr24api MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "fr24api-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@flightradar24/fr24api-mcp"
      ],
      "env": {
        "FR24_API_KEY": "YOUR_FR24_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

RecallChecker — Vehicle Safety Recalls is categorized under Travel & Transportation and uses a remote HTTP/SSE transport. Fr24api MCP belongs to Travel & Transportation and uses a local stdio subprocess. Pick RecallChecker — Vehicle Safety Recalls for travel & transportation work and Fr24api MCP for travel & transportation.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

RecallChecker — Vehicle Safety Recalls has no declared pricing — check the project's own site. Fr24api MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add recallchecker-vehicle-safety-recalls and fr24api-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, RecallChecker — Vehicle Safety Recalls has a quality signal of 52/100 (Good) with 4 views, 0 installs and 0 GitHub stars. Fr24api MCP has 56/100 (Good) with 2 views, 0 installs and 30 GitHub stars.