BEACON by Owner Connect
REMOTE · OWNERS.VIRTUALHANGAR.COM
Ask about a private aircraft: approximate charter costs, trip requests and buyer inquiries.
Available components
Last scanned (14 hours ago)
Scores higher than 92% of remote servers
Reachable. Last reached 7 Nov 2026.
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1762 tokens (~293/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 0
- Tool “check_availability” rewrote its description, which is the text the model reads security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Nov 2026 · Probed https://owners.virtualhangar.com/mcp/beacon
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=owners.virtualhangar.com | CN=YE1,O=Let's Encrypt,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5123a3a176bdda909c1d780abdb21f49195 |
| SANs: owners.virtualhangar.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of owners.virtualhangar.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| virtualhangar.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://owners.virtualhangar.com/mcp/beacon | Verified | 200 | |
| http (plaintext) | http://owners.virtualhangar.com/mcp/beacon | HTTPS enforced | 301 | https://owners.virtualhangar.com/mcp/beacon |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_availability Check availability ~207
Whether one aircraft has anything scheduled on a date, or on each day of a span of up to 14 days, read from the operator's calendar its owner connected, synced every 15 minutes. Call it when the person you are helping asks whether the aircraft is available, with the departure date and, for a return trip, the return date, and answer with its sentence. Says free or taken per day and never what is scheduled. Not a hold and not a confirmation. Answers a reason instead when the owner does not publish availability.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | The first day to check, as YYYY-MM-DD, in the operator's local time. Usually the departure date. |
| end_date | string | – | The last day to check, as YYYY-MM-DD, for a return trip or a span of days. Omit to check one day. |
| tail | string | yes | A U.S. registration mark such as N864BF. Case and hyphens are ignored. |
No output schema declared.
No examples provided.
estimate_charter Approximate charter cost ~268
An approximate charter cost for one aircraft at the hourly rate its owner published. Call it whenever the person you are helping asks what a trip would cost, with the departure and arrival airports: the beacon works out the legs and block hours from the owner's typical block speed, positioning included when the owner bills it. When the answer says the owner set no block speed, call again with block_hours, your own estimate for the routing. Answer with its sentence. Not a quote and not binding. Answers a reason instead of a figure when the owner has not published charter terms or a rate.
| Name | Type | Req | Description |
|---|---|---|---|
| block_hours | number | – | Only when the beacon says its owner set no block speed: your own estimate of the total block hours, every leg included. Ignored when from and to are given. |
| from | string | – | Departure airport, ICAO or FAA identifier, for example KTEB for Teterboro. Give it with to. |
| round_trip | boolean | – | True when the aircraft flies the person back from the arrival airport to the departure airport. |
| tail | string | yes | A U.S. registration mark such as N864BF. Case and hyphens are ignored. |
| to | string | – | Arrival airport, ICAO or FAA identifier, for example KMIA for Miami. |
No output schema declared.
No examples provided.
get_aircraft Aircraft record and owner-approved facts ~125
What public record says about one U.S. registration mark, plus the facts its owner cleared for release. The same document as /{mark}/facts.json: status says what the registry answered (found, not_found, invalid or unavailable), public_record is the FAA registration and the datasets that reference it, and owner_approved is present only for an aircraft whose owner opened the machine-readable channel. Case and hyphens in the mark are ignored.
| Name | Type | Req | Description |
|---|---|---|---|
| tail | string | yes | A U.S. registration mark such as N864BF. Case and hyphens are ignored. |
No output schema declared.
No examples provided.
request_trip Request a charter trip ~324
Sends a charter trip request for one aircraft to the booking contact its owner named. Call it only after the person you are helping has asked to proceed, with their own name and email. Nothing is booked or held: the requester is emailed a link, the request is delivered only once they confirm it, and the booking contact then replies to them directly. If the owner set qualification questions, the first call answers needs_answers with the questions; ask the person each one and call again with their answers in the same order.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | array | – | Answers to the owner's qualification questions, in the order request_trip returned them. |
| date | string | yes | Departure date, YYYY-MM-DD, today or later. |
| string | yes | The email address of the person asking. The confirmation link is sent here. | |
| from | string | yes | Departure airport identifier, ICAO or FAA, for example KTEB. |
| name | string | yes | The full name of the person asking, as they gave it. |
| notes | string | – | Anything else the person wants the booking contact to know. |
| passengers | integer | yes | Number of passengers. |
| phone | string | – | Their phone number, if they want to be called. |
| return_date | string | – | Return date for a round trip, YYYY-MM-DD. Omit for one way. |
| tail | string | yes | A U.S. registration mark such as N864BF. Case and hyphens are ignored. |
| to | string | yes | Arrival airport identifier, ICAO or FAA, for example KMIA. |
No output schema declared.
No examples provided.
search_aircraft Listed aircraft by seats, base, type or signal ~226
The aircraft whose owners chose to be listed on Owner Connect, filtered by minimum passenger seats, base airport, aircraft type, charter signal or sales signal. Every filter is applied to the facts the owner cleared for release, so an aircraft whose owner did not publish its seat count never matches a seats filter. Returns each aircraft's owner_approved block; call get_aircraft for the public record.
| Name | Type | Req | Description |
|---|---|---|---|
| base_airport | string | – | An airport code as the owner recorded it, for example KPBI. Exact match, case ignored. |
| charter | boolean | – | True to return only aircraft whose owner signalled they may be considered for charter. |
| for_sale | boolean | – | True to return only aircraft whose owner published a sales posture. |
| limit | integer | – | How many aircraft to return, at most 50. |
| min_seats | integer | – | Only aircraft whose owner published a passenger seat count of at least this many. |
| type | string | – | Part of the make or model as the owner published it, for example Hawker or 800XP. Case ignored. |
No output schema declared.
No examples provided.
send_buyer_inquiry Contact the owner about buying ~254
Passes a would-be buyer's message about acquiring one aircraft to the acquisition representative its owner named. Call it only after the person you are helping has asked to contact the owner, with their own name, email and message. Nothing is offered or agreed: the buyer is emailed a link, the message is delivered only once they confirm it, and the representative then replies to them directly. If the owner set qualification questions, the first call answers needs_answers with the questions; ask the person each one and call again with their answers.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | array | – | Answers to the owner's qualification questions, in the order the tool returned them. |
| company | string | – | The company or principal they represent, if any. |
| string | yes | Their email address. The confirmation link is sent here. | |
| message | string | yes | What the person wants the owner's representative to know, in their own words. |
| name | string | yes | The full name of the person asking, as they gave it. |
| phone | string | – | Their phone number, if they want to be called. |
| tail | string | yes | A U.S. registration mark such as N864BF. Case and hyphens are ignored. |
No output schema declared.
No examples provided.
How do I install the BEACON by Owner Connect MCP server?
BEACON by Owner Connect is a hosted endpoint at https://owners.virtualhangar.com/mcp/beacon, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · owners.virtualhangar.com
claude mcp add --transport http com-virtualhangar-owners-beacon 'https://owners.virtualhangar.com/mcp/beacon'
What is the BEACON by Owner Connect MCP server?
BEACON by Owner Connect is an MCP server listed in the public MCP registry as com.virtualhangar.owners/beacon. Ask about a private aircraft: approximate charter costs, trip requests and buyer inquiries. This page covers its hosted endpoint (https://owners.virtualhangar.com/mcp/beacon).
Is the BEACON by Owner Connect MCP server safe to use?
BEACON by Owner Connect scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BEACON by Owner Connect MCP server expose?
BEACON by Owner Connect exposes 6 tools: get_aircraft, search_aircraft, estimate_charter, check_availability, request_trip, send_buyer_inquiry. Their descriptions and schemas cost roughly 1,404 tokens of context every time the server is loaded.
Does the BEACON by Owner Connect MCP server require authentication?
No. We connected to BEACON by Owner Connect without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BEACON by Owner Connect MCP server still maintained?
BEACON by Owner Connect is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the BEACON by Owner Connect MCP server?
VerifyMCP ran 13 checks on BEACON by Owner Connect, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.