# app.aplusz/flight-fares (remote · aplusz.app)

Cheapest observed fare, 6-month low and best departure date for a city pair.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `aplusz.app`: 71/100 (this document), [markdown](https://verifymcp.io/servers/app-aplusz-flight-fares/aplusz.md), [page](https://verifymcp.io/servers/app-aplusz-flight-fares/aplusz)

## Channel facts

- Endpoint: `https://aplusz.app/mcp`
- 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-09-28.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 76/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add --transport http app-aplusz-flight-fares 'https://aplusz.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-aplusz-flight-fares": {
      "url": "https://aplusz.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-aplusz-flight-fares": {
      "type": "http",
      "url": "https://aplusz.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-aplusz-flight-fares]
url = "https://aplusz.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-aplusz-flight-fares": {
      "type": "remote",
      "url": "https://aplusz.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-aplusz-flight-fares --url 'https://aplusz.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-aplusz-flight-fares:
    url: "https://aplusz.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-aplusz-flight-fares": {
      "Transport": "http",
      "Url": "https://aplusz.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-aplusz-flight-fares -t streamable-http -u 'https://aplusz.app/mcp'
```

### Other

```json
{
  "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.

## 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-09-28 (score 71, 0)

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

### 2026-09-26 (score 71, +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.

### 2026-09-25 (score 70, 0)

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

### 2026-09-24 (score 70, +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.

### 2026-09-22 (score 69, +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.

### 2026-09-20 (score 68, +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.

### 2026-09-18 (score 67, +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.

### 2026-09-16 (score 66, +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.

## MCP tools (3)

### `find_cheapest_fare` (~206 tokens)

Cheapest fare between two cities

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.

Input parameters:

- `from` (string, required): 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, required): Destination city. Uppercase IATA city code such as BKK. Must differ from from.

### `list_routes_from` (~98 tokens)

Cheapest destinations from one city

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.

Input parameters:

- `from` (string, required): Origin city. Uppercase IATA city code such as LON.
- `limit` (integer): How many destinations to return, 1-200. Default 40.

### `resolve_city` (~68 tokens)

Resolve a city name to its IATA code

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.

Input parameters:

- `query` (string, required): City name or partial name, e.g. "sao paulo".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-aplusz-flight-fares/aplusz#diagnostics

## Score history

- 2026-09-28: 71
- 2026-09-27: 71
- 2026-09-26: 71
- 2026-09-25: 70
- 2026-09-24: 70
- 2026-09-23: 69
- 2026-09-22: 69
- 2026-09-21: 68
- 2026-09-20: 68
- 2026-09-19: 67
- 2026-09-18: 67
- 2026-09-17: 66
- 2026-09-16: 66
- 2026-09-15: 65
- 2026-09-14: 65
- 2026-09-13: 64

## Common questions

### 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 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://aplusz.app/mcp
- Repository: https://github.com/dagrang-repository/aplusz
- Website: https://aplusz.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-aplusz-flight-fares/aplusz.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-aplusz-flight-fares/aplusz.json
- HTML version of this page: https://verifymcp.io/servers/app-aplusz-flight-fares/aplusz