BEACON by Owner Connect MCP server
com.virtualhangar.owners/beaconowners.virtualhangar.comstreamable-httpv1.0.0Scanned
Ask about a private aircraft: approximate charter costs, trip requests and buyer inquiries.
6 tools: 3 do something that can't be undone, 1 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 3
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the BEACON by Owner Connect MCP server can do
The BEACON by Owner Connect MCP server is published by owners.virtualhangar.com, a domain the MCP Registry verified. It has 6 tools. It can do things that cannot be undone, such as sending, paying or publishing (estimate_charter, request_trip and send_buyer_inquiry) and create or change data (1 tool: check_availability), but cannot delete data. 2 tools only read.
4 tools bring in text other people can write (get_aircraft, estimate_charter, request_trip and 1 more); 3 tools can send data out of your system (estimate_charter, request_trip and send_buyer_inquiry).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 14, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Can't be undone 3Claude Code: ask
estimate_charterAn approximate charter cost for one aircraft at the hourly rate its owner published.Reads text others writeCan send data out1 finding
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "estimate_charter" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- title: Approximate charter cost
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
request_tripSends a charter trip request for one aircraft to the booking contact its owner named.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "request_trip" says "request": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it 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.
Annotations the server declares
- title: Request a charter trip
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
send_buyer_inquiryPasses a would-be buyer's message about acquiring one aircraft to the acquisition representative its owner named.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "send_buyer_inquiry" says "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "send_buyer_inquiry" says "send": it sends or publishes something to other people.
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
Description, as the server wrote it 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.
Annotations the server declares
- title: Contact the owner about buying
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
Changes things 1Claude Code: ask
check_availabilityWhether 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check availability
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
get_aircraftWhat public record says about one U.S.Reads text others writeNo findings
Why it is in this group
- The name "get_aircraft" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Aircraft record and owner-approved facts
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
search_aircraftThe aircraft whose owners chose to be listed on Owner Connect, filtered by minimum passenger seats, base airport, aircraft type, charter signal or sales signal.No findings
Why it is in this group
- The name "search_aircraft" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Listed aircraft by seats, base, type or signal
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out3
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:50 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (3 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://owners.virtualhangar.com/mcp/beacon: tools/list returned 6 tools to an anonymous client, including estimate_charter (irreversible), request_trip (irreversible), send_buyer_inquiry (irreversible), check_availability (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnestimate_charter
The server marks "estimate_charter" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:check_availabilityChanges thingsdescriptionannotations
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http beacon https://owners.virtualhangar.com/mcp/beaconclaude mcp add --transport http beacon https://owners.virtualhangar.com/mcp/beaconRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__beacon__get_aircraft",
"mcp__beacon__search_aircraft"
],
"ask": [
"mcp__beacon__estimate_charter",
"mcp__beacon__check_availability",
"mcp__beacon__request_trip",
"mcp__beacon__send_buyer_inquiry"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as beacon. Review it before you use it.
Capability tags behind 4 rules
- mcp__beacon__get_aircraft untrusted-input
- mcp__beacon__estimate_charter untrusted-input, outbound
- mcp__beacon__request_trip untrusted-input, outbound
- mcp__beacon__send_buyer_inquiry untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.virtualhangar.owners/beacon/verify?hash=f123fc701d62292fce6f1f1f305d748c4f9ae51e7f80619ec3e73fbbe8663b00" | jq -e '.changed == false'Pinned hash f123fc701d62, from Nov 14, 2026, 18:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.virtualhangar.owners/beacon/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.virtualhangar.owners/beacon)Source: MCP Registry. Synced Oct 21, 2026, 18:10 UTC.
BEACON by Owner Connect MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the BEACON by Owner Connect MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the BEACON by Owner Connect MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the BEACON by Owner Connect MCP server do things that cannot be undone?
- Yes. 3 tools can send, pay, publish or merge: estimate_charter, request_trip and send_buyer_inquiry.
What tools does the BEACON by Owner Connect MCP server have?
- 6 tools: 3 irreversible, 1 write, 2 read. estimate_charter, request_trip, send_buyer_inquiry, check_availability, get_aircraft and search_aircraft.
Does the BEACON by Owner Connect MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the BEACON by Owner Connect MCP server send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): estimate_charter, request_trip and send_buyer_inquiry.
Has the BEACON by Owner Connect MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 1, 2026. Every change is on this page and in its Atom feed.