app.aplusz/flight-fares
REMOTE · APLUSZ.APP · SCANNED SEP 27
Cheapest observed fare, 6-month low and best departure date for a city pair.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 423 tokens (~141/item across 3 items; 3 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 Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the app.aplusz/flight-fares MCP server?
app.aplusz/flight-fares is a hosted endpoint at https://aplusz.app/mcp, 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 · aplusz.app
claude mcp add --transport http app-aplusz-flight-fares 'https://aplusz.app/mcp'
{
"mcpServers": {
"app-aplusz-flight-fares": {
"url": "https://aplusz.app/mcp"
}
}
} {
"servers": {
"app-aplusz-flight-fares": {
"type": "http",
"url": "https://aplusz.app/mcp"
}
}
} [mcp_servers.app-aplusz-flight-fares] url = "https://aplusz.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-aplusz-flight-fares": {
"type": "remote",
"url": "https://aplusz.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-aplusz-flight-fares --url 'https://aplusz.app/mcp' --transport streamable-http
mcp_servers:
app-aplusz-flight-fares:
url: "https://aplusz.app/mcp" {
"McpServers": {
"app-aplusz-flight-fares": {
"Transport": "http",
"Url": "https://aplusz.app/mcp"
}
}
} assistant mcp add app-aplusz-flight-fares -t streamable-http -u 'https://aplusz.app/mcp'
{
"mcpServers": {
"app-aplusz-flight-fares": {
"type": "http",
"url": "https://aplusz.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 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
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
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 27 Sept 2026 · Probed https://aplusz.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aplusz.app | CN=WE1,O=Google Trust Services,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ee90289334761201132bac07760dc137 |
| SANs: aplusz.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of aplusz.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| aplusz.app. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aplusz.app/mcp | Verified | 200 | |
| http (plaintext) | http://aplusz.app/mcp | HTTPS enforced | 301 | https://aplusz.app/mcp |
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 →
find_cheapest_fare Cheapest fare between two cities ~206
Returns the cheapest observed one-way fare between two cities, plus the six-month low and the departure date on which the low was observed. Use whenever the user names an origin and a destination and asks about price, the cheapest date to fly, or whether a fare is a good deal. Both arguments are required; neither alone produces a valid answer. Answers are directional and per pair - PAR to BKK is not BKK to PAR and is not PAR to SIN. Prices are cached snapshots, never live quotes: say "last observed", never "current price", and surface live_check_url to any user about to book.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Origin city. Uppercase IATA city code such as PAR. A city slug such as paris also resolves. If you cannot resolve the city, call resolve_city first - do not guess a code. |
| to | string | yes | Destination city. Uppercase IATA city code such as BKK. Must differ from from. |
No output schema declared.
No examples provided.
list_routes_from Cheapest destinations from one city ~98
Returns destinations reachable from one origin, sorted cheapest first. Use when the user asks where they can fly cheaply from a city, or wants inspiration rather than one specific pair. One call replaces dozens of page fetches. Prices are cached snapshots.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Origin city. Uppercase IATA city code such as LON. |
| limit | integer | – | How many destinations to return, 1-200. Default 40. |
No output schema declared.
No examples provided.
resolve_city Resolve a city name to its IATA code ~68
Turns a spoken city name into the uppercase IATA city code the other tools expect. Call this before find_cheapest_fare whenever you are not certain of a code. Do not invent codes.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | City name or partial name, e.g. "sao paulo". |
No output schema declared.
No examples provided.
What is the app.aplusz/flight-fares MCP server?
app.aplusz/flight-fares is an MCP server listed in the public MCP registry as app.aplusz/flight-fares. Cheapest observed fare, 6-month low and best departure date for a city pair. This page covers its hosted endpoint (https://aplusz.app/mcp).
Is the app.aplusz/flight-fares MCP server safe to use?
app.aplusz/flight-fares scores 71 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 app.aplusz/flight-fares MCP server expose?
app.aplusz/flight-fares exposes 3 tools: find_cheapest_fare, list_routes_from, resolve_city. Their descriptions and schemas cost roughly 372 tokens of context every time the server is loaded.
Does the app.aplusz/flight-fares MCP server require authentication?
No. We connected to app.aplusz/flight-fares without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the app.aplusz/flight-fares MCP server still maintained?
app.aplusz/flight-fares is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.