Databases
qatarevtol.com
Provides a reference database for entities like aircraft, operators, vertiports, and routes, with search, lookup, and change tracking.
ENDPOINT 1
https://qatarevtol.com/mcp
MCP server metadata
- Name
- qatarevtol.com
- Version
- 1.0.0
Primary-source eVTOL reference. Every record carries last_verified and its sources; attribution (CC BY 4.0) is the only condition of use.
Known tools 3
get_entityFetch one entity from the reference by slug: current status, claim, coordinates, last_verified date and full primary-source list.
Inferred read-onlysearch_entitiesSearch entities by free text (name, claim), optionally filtered by entity_type (aircraft, operator, vertiport, route, regulator, answer) and/or status.
Inferred read-onlylist_changesThe fact-change log: every entity addition and status transition in the reference, dated, newest first.
Inferred read-onlyCONNECT 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.qatarevtol-com]
url = "https://qatarevtol.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"qatarevtol-com": {
"type": "http",
"url": "https://qatarevtol.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: qatarevtol-com
Remote MCP URL: https://qatarevtol.com/mcp
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": {
"qatarevtol-com": {
"url": "https://qatarevtol.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"qatarevtol-com": {
"type": "http",
"url": "https://qatarevtol.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "qatarevtol-com",
"transport": "streamable-http",
"url": "https://qatarevtol.com/mcp"
}
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.