# BEACON by Owner Connect (remote · owners.virtualhangar.com)

Ask about a private aircraft: approximate charter costs, trip requests and buyer inquiries.

- Trust score: 86/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-07

## Components

- remote · `owners.virtualhangar.com`: 86/100 (this document), [markdown](https://verifymcp.io/servers/com-virtualhangar-owners-beacon/mcp-beacon.md), [page](https://verifymcp.io/servers/com-virtualhangar-owners-beacon/mcp-beacon)

## Channel facts

- Endpoint: `https://owners.virtualhangar.com/mcp/beacon`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-07.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-virtualhangar-owners-beacon 'https://owners.virtualhangar.com/mcp/beacon'
```

### Cursor

```json
{
  "mcpServers": {
    "com-virtualhangar-owners-beacon": {
      "url": "https://owners.virtualhangar.com/mcp/beacon"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-virtualhangar-owners-beacon": {
      "type": "http",
      "url": "https://owners.virtualhangar.com/mcp/beacon"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-virtualhangar-owners-beacon]
url = "https://owners.virtualhangar.com/mcp/beacon"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-virtualhangar-owners-beacon": {
      "type": "remote",
      "url": "https://owners.virtualhangar.com/mcp/beacon",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-virtualhangar-owners-beacon --url 'https://owners.virtualhangar.com/mcp/beacon' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-virtualhangar-owners-beacon:
    url: "https://owners.virtualhangar.com/mcp/beacon"
```

### Netclaw

```json
{
  "McpServers": {
    "com-virtualhangar-owners-beacon": {
      "Transport": "http",
      "Url": "https://owners.virtualhangar.com/mcp/beacon"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-virtualhangar-owners-beacon -t streamable-http -u 'https://owners.virtualhangar.com/mcp/beacon'
```

### Other

```json
{
  "mcpServers": {
    "com-virtualhangar-owners-beacon": {
      "type": "http",
      "url": "https://owners.virtualhangar.com/mcp/beacon"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 86, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 86, +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.

### 2026-11-03 (score 85, +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.

### 2026-11-01 (score 84, +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.

### 2026-10-30 (score 83, +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.

### 2026-10-27 (score 82, +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.

### 2026-10-25 (score 81, +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.

### 2026-10-24 (score 80, 0)

- [security] Tool “check_availability” rewrote its description, which is the text the model reads

## MCP tools (6)

### `get_aircraft` (~125 tokens)

Aircraft record and owner-approved facts

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.

Input parameters:

- `tail` (string, required): A U.S. registration mark such as N864BF. Case and hyphens are ignored.

### `search_aircraft` (~226 tokens)

Listed aircraft by seats, base, type or signal

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.

Input parameters:

- `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.

### `estimate_charter` (~268 tokens)

Approximate charter cost

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.

Input parameters:

- `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, required): 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.

### `check_availability` (~207 tokens)

Check availability

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.

Input parameters:

- `date` (string, required): 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, required): A U.S. registration mark such as N864BF. Case and hyphens are ignored.

### `request_trip` (~324 tokens)

Request a charter trip

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.

Input parameters:

- `answers` (array): Answers to the owner's qualification questions, in the order request_trip returned them.
- `date` (string, required): Departure date, YYYY-MM-DD, today or later.
- `email` (string, required): The email address of the person asking. The confirmation link is sent here.
- `from` (string, required): Departure airport identifier, ICAO or FAA, for example KTEB.
- `name` (string, required): 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, required): 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, required): A U.S. registration mark such as N864BF. Case and hyphens are ignored.
- `to` (string, required): Arrival airport identifier, ICAO or FAA, for example KMIA.

### `send_buyer_inquiry` (~254 tokens)

Contact the owner about buying

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.

Input parameters:

- `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.
- `email` (string, required): Their email address. The confirmation link is sent here.
- `message` (string, required): What the person wants the owner's representative to know, in their own words.
- `name` (string, required): The full name of the person asking, as they gave it.
- `phone` (string): Their phone number, if they want to be called.
- `tail` (string, required): A U.S. registration mark such as N864BF. Case and hyphens are ignored.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-virtualhangar-owners-beacon/mcp-beacon#diagnostics

## Score history

- 2026-11-07: 86
- 2026-11-06: 86
- 2026-11-05: 86
- 2026-11-04: 85
- 2026-11-03: 85
- 2026-11-02: 84
- 2026-11-01: 84
- 2026-10-31: 83
- 2026-10-30: 83
- 2026-10-29: 82
- 2026-10-28: 82
- 2026-10-27: 82
- 2026-10-26: 81
- 2026-10-25: 81
- 2026-10-24: 80
- 2026-10-23: 80
- 2026-10-22: 79
- 2026-10-21: 79
- 2026-10-20: 78
- 2026-10-19: 78
- 2026-10-18: 78
- 2026-10-17: 77
- 2026-10-16: 77
- 2026-10-15: 76
- 2026-10-14: 76
- 2026-10-13: 75
- 2026-10-12: 75
- 2026-10-10: 74
- 2026-10-08: 73

## Common questions

### 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.

## Links

- Remote endpoint: https://owners.virtualhangar.com/mcp/beacon
- Website: https://owners.virtualhangar.com/connect-your-ai
- Changelog RSS feed: https://verifymcp.io/servers/com-virtualhangar-owners-beacon/mcp-beacon.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-virtualhangar-owners-beacon/mcp-beacon/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-virtualhangar-owners-beacon/mcp-beacon.json
- HTML version of this page: https://verifymcp.io/servers/com-virtualhangar-owners-beacon/mcp-beacon