Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
johto.data FAA Drone Data is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
5
tools declared
remote
at its publisher
—
calls last 7d
What it does
Fresh, clean FAA drone data: Part 107 waivers and FRIA Remote ID sites as rows, with FAA doc links.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http johto-data-faa-drone-data-mcp 'https://mcp.apify.com/?tools=johto.data/faa-drone-data&payment=x402'
# 2 — ask your agent for something these tools do
# get-actor-run, get-dataset-items, get-key-value-store-record and 2 more
johto.data FAA Drone Data costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
JOAll 2 servers
johtodata2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http johto-data-faa-drone-data-mcp 'https://mcp.apify.com/?tools=johto.data/faa-drone-data&payment=x402'Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Get detailed information about a specific Actor run. Returns run result: status, storages (datasets/keyValueStores alias map), stats, summary, nextStep. - summary describes the past (e.g. "SUCCEEDED in 22s. 47 items; 3 fields available."). - nextStep prescribes one primary follow-up action with identifiers interpolated (e.g. "Use get-dataset-items with datasetId=..."). - waitSecs (0–45, default 3
| Parameter | Type | Required | Notes |
|---|---|---|---|
| runId | string | yes | The ID of the Actor run. |
| waitSecs | integer | no | Maximum seconds to wait for the run to reach a terminal state (SUCCEEDED, FAILED, ABORTED, TIMED-OUT). 0 returns immediately with the current status. Cap: 45. Default: 30. |
Get items (rows) from a dataset — the output/results produced by an Actor run. Returns the rows themselves, not dataset metadata, counts, or a schema. When the user provides a datasetId and asks to retrieve results, output, data, or rows, call this tool directly. Default limit is 20. Use clean=true to skip empty items and hidden fields. USAGE: - Use when you need to read data from a dataset (all
| Parameter | Type | Required | Notes |
|---|---|---|---|
| datasetId | string | yes | Dataset ID or username~dataset-name. |
| clean | boolean | no | If true, returns only non-empty items and skips hidden fields (starting with #). Shortcut for skipHidden=true and skipEmpty=true. |
| offset | number | no | Number of items to skip at the start. Default is 0. |
| limit | integer | no | Maximum number of items to return. Default is 20. |
| fields | string | no | Comma-separated list of fields to include in results. Fields in output are sorted as specified. Use dot notation for nested objects (e.g. "metadata.url"); the server auto-flattens parent prefixes. |
| omit | string | no | Comma-separated list of fields to exclude from results. |
| desc | boolean | no | If true, results are returned in reverse order (newest to oldest). |
| flatten | string | no | Comma-separated list of fields to flatten (e.g. flatten="metadata" turns {"metadata":{"url":"x"}} into {"metadata.url":"x"}). Normally derived automatically from dot-notation in fields; specify only |
Get the value stored under a specific key in a key-value store — a single record, not a listing of all keys. Requires the exact key name. The response preserves the original Content-Encoding; most clients handle decompression automatically. USAGE: - Use when you need to retrieve a specific record (JSON, text, or binary) from a store. USAGE EXAMPLES: - user_input: Get record INPUT from store abc1
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyValueStoreId | string | yes | Key-value store ID or username~store-name. |
| recordKey | string | yes | Key of the record to retrieve. |
Abort an Actor run that is currently starting or running. For runs with status SUCCEEDED, FAILED, ABORTING, ABORTED, or TIMED-OUT, this call has no effect. The results will include the updated run details after the abort request. USAGE: - Use when you need to stop a run that is taking too long or misconfigured. USAGE EXAMPLES: - user_input: Abort run y2h7sK3Wc - user_input: Gracefully abort run
| Parameter | Type | Required | Notes |
|---|---|---|---|
| runId | string | yes | The ID of the Actor run to abort. |
| gracefully | boolean | no | If true, the Actor run will abort gracefully with a 30-second timeout. |
This tool calls the Actor "johto.data/faa-drone-data" and retrieves its output results. Actor description: FAA drone data for AI agents: active Part 107 waivers (company, waiver number, waived rules like BVLOS 107.31, over people 107.39, night, altitude, dates) plus FRIA Remote ID flying sites with location. Filter by rule, keyword, state, date. $0.02/record. This tool requires an x402 payment. I
| Parameter | Type | Required | Notes |
|---|---|---|---|
| datasets | array | no | Which official FAA datasets to return. Example values: ["waivers"] |
| issuedAfter | string | no | YYYY-MM-DD. Waivers: effectiveFrom date (FAA's 'Date of Issuance' column, which is when the waiver takes effect). FRIA: start date. Empty = all. |
| regulations | array | no | Waived Part 107 sections to keep, e.g. ["107.31"] (BVLOS), ["107.39"] (over people), ["107.29"] (night), ["107.51(b)"] (altitude). Empty = all. Example values: ["107.31"] |
| keywords | array | no | Match company/person (waivers) or site/organization/city (FRIA). |
| states | array | no | Two-letter states for FRIA sites. Empty = all. |
| activeOnly | boolean | no | Skip expired waivers/sites. Waivers that are not yet in effect (status 'upcoming') are kept. Example values: true |
| maxItems | integer | no | Maximum records; each is one charged result ($0.002). Default 10 keeps an empty-input call a cheap sample; raise it for the full list. Example values: 25 |
| onlyNew | boolean | no | Remember results across runs (per account) and return only items not seen before. Ideal for scheduled runs: you pay only for new records. |
| webhookUrl | string | no | Optional. POSTs the new items as JSON with a 'text'/'content' summary (Slack, Discord, Zapier, Make, n8n compatible). |
| waitSecs | integer | no | Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow nextStep to poll |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install johto.data FAA Drone Data or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.2 · scanned 23 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digesta31192001c536529b20e5c5a66c2e9bdefb36348942e3af241c71221d1990ccd
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get-actor-run | no tags | |
| get-dataset-items | no tags | |
| get-key-value-store-record | no tags | |
| abort-actor-run | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| johto-dot-data--faa-drone-data | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digesta31192001c536529
Scanned2026-10-23
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.2.
1.0.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish johto.data FAA Drone Data can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.