Skip to content
MCPSTAMP
MCP server report

johto.data FAA Drone Data MCP server

com.johtodata/faa-drone-data

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 86 of 100 (grade B), higher than 58.3% of the 33,003 registry servers that responded over HTTPS that day. Ready for MCP Registry. Not ready for Claude, ChatGPT and Gemini.

Measured facts

Score
86B
Sign-in
OAuth
Tools listed
Behind sign-in
Protocol version
2025-11-25
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by Resource metadata "resource" equals the server URL and tools/list returns tools.
ChatGPT app directory Not ready Blocked by tools/list returns tools.
Gemini Connected Apps Not ready Blocked by tools/list returns tools.
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

3 checks to fix

  1. Fails

    tools/list returns tools

    tools_list

    Blocks Claude, ChatGPT and Gemini.

    Measured tools/list returned 0 tools

    Expose at least one tool in tools/list (store reviewers test tools).

  2. Fails

    Resource metadata "resource" equals the server URL

    auth_resource

    Blocks Claude.

    Measured resource https://mcp.apify.com is not the server URL https://mcp.apify.com/?tools=johto.data/faa-drone-data&payment=x402

    Serve metadata whose "resource" is exactly https://mcp.apify.com/?tools=johto.data/faa-drone-data&payment=x402 (Claude requires an exact match, path included), e.g. at /.well-known/oauth-protected-resource.

  3. Warning

    initialize latency

    latency

    Measured 3197 ms

    Bring initialize under 1.5 s: avoid cold starts and upstream calls in the handshake.

17 checks passed, 7 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, JSON-RPC error for unknown method, GET answers SSE or 405, serverInfo name and version, Server instructions, tools capability declared, Sign-in method the store supports (OAuth or none), Protected resource metadata (RFC 9728), Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised.

Not run. 401 carries WWW-Authenticate resource_metadata. These need an OAuth sign-in flow the check could not reach.

Not run. inputSchema is an object schema, Tool names are valid and portable, readOnlyHint or destructiveHint on every tool, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT), Human-readable title on every tool, Tool descriptions. The tools sit behind sign-in, and the check runs without credentials.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for johto.data FAA Drone Data

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fmcp.apify.com%2F%3Ftools%3Djohto.data%2Ffaa-drone-data%26payment%3Dx402)](https://www.mcpstamp.com/r/com-johtodata-faa-drone-data/)

HTML

<a href="https://www.mcpstamp.com/r/com-johtodata-faa-drone-data/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fmcp.apify.com%2F%3Ftools%3Djohto.data%2Ffaa-drone-data%26payment%3Dx402" alt="McpStamp score" height="20"></a>
Registry entry

About this server

Fresh, clean FAA drone data: Part 107 waivers and FRIA Remote ID sites as rows, with FAA doc links.
Registry name
com.johtodata/faa-drone-data
Remote URL
https://mcp.apify.com/?tools=johto.data/faa-drone-data&payment=x402
Version
1.0.2
Source
github.com/johtodata/johto-data-api
Website
johtodata.com/docs/faa-drone-data/
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade B servers

All grade B servers · All server reports · State of MCP readiness, November 2026