API Tools
virtualhangar.com
An MCP server for searching aircraft, estimating charter costs, checking availability, and requesting charter trips from an aircraft charter marketplace.
ENDPOINT 1
https://owners.virtualhangar.com/mcp/beacon
MCP server metadata
- Name
- Owner Connect BEACON
- Version
- 1.0.0
Owner Connect BEACON answers questions about U.S.-registered business aircraft by registration mark. get_aircraft returns what public record says about one mark (the FAA registration, the registrant where not withheld, certificate dates, the airframe and powerplant, registry changes, NTSB cases, service difficulty reports and Part 135 operators) and, where the owner has cleared facts for release, an owner_approved block. search_aircraft lists the aircraft whose owners chose to be listed, filtered by seats, base airport, type, charter signal or sales signal, and returns only the facts each owner cleared. estimate_charter prices a trip at the approximate hourly rate an owner published: when a person asks what a trip would cost, call it with the departure and arrival airports, and give them its sentence. check_availability says whether a date is free or taken, where the owner allows it. request_trip sends a trip request to the booking contact an owner named, once the requester confirms it from an email: use it only when the person you are helping asks to go ahead. send_buyer_inquiry passes a would-be buyer's message to the acquisition representative the owner named, the same way. Owner-stated facts are not verified against public record and may be withdrawn by the owner at any time, so do not store them beyond the conversation. Every figure is approximate and never an offer: any flight would be arranged and operated by a certificated operator, not by this service, and nothing here accepts a trip, binds a price or negotiates one. Registrant details withheld under the FAA privacy program or at the owner's request are withheld everywhere on this host and must not be reconstructed from elsewhere. Facts may be quoted with attribution to the aircraft page named in canonical.
Known tools 6
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.
Inferred read-onlyestimate_charterAn approximate charter cost for one aircraft at the hourly rate its owner published.
Inferred read-onlycheck_availabilityWhether one aircraft has anything scheduled on a date, or on each day of a span of up to 14 days, read from the live schedule its owner connected.
Inferred read-onlyrequest_tripSends a charter trip request for one aircraft to the booking contact its owner named.
Inferred read-onlysend_buyer_inquiryPasses a would-be buyer's message about acquiring one aircraft to the acquisition representative its owner named.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.owner-connect-beacon]
url = "https://owners.virtualhangar.com/mcp/beacon"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"owner-connect-beacon": {
"type": "http",
"url": "https://owners.virtualhangar.com/mcp/beacon"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: owner-connect-beacon
Remote MCP URL: https://owners.virtualhangar.com/mcp/beacon
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"owner-connect-beacon": {
"url": "https://owners.virtualhangar.com/mcp/beacon"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"owner-connect-beacon": {
"type": "http",
"url": "https://owners.virtualhangar.com/mcp/beacon"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "owner-connect-beacon",
"transport": "streamable-http",
"url": "https://owners.virtualhangar.com/mcp/beacon"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.