# FlightSweeper (remote · flightsweeper-webmcp.vercel.app)

Anonymous public tools for FlightSweeper. See the published agent boundary before use.

- Trust score: 86/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `flightsweeper-webmcp.vercel.app`: 86/100 (this document), [markdown](https://verifymcp.io/servers/app-vercel-flightsweeper-webmcp-public/flightsweeper-webmcp.md), [page](https://verifymcp.io/servers/app-vercel-flightsweeper-webmcp-public/flightsweeper-webmcp)

## Channel facts

- Endpoint: `https://flightsweeper-webmcp.vercel.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-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 203 tokens (~50/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 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).
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 FlightSweeper MCP server?

FlightSweeper is a hosted endpoint at https://flightsweeper-webmcp.vercel.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-vercel-flightsweeper-webmcp-public 'https://flightsweeper-webmcp.vercel.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-vercel-flightsweeper-webmcp-public": {
      "url": "https://flightsweeper-webmcp.vercel.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-vercel-flightsweeper-webmcp-public": {
      "type": "http",
      "url": "https://flightsweeper-webmcp.vercel.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-vercel-flightsweeper-webmcp-public]
url = "https://flightsweeper-webmcp.vercel.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-vercel-flightsweeper-webmcp-public": {
      "type": "remote",
      "url": "https://flightsweeper-webmcp.vercel.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-vercel-flightsweeper-webmcp-public --url 'https://flightsweeper-webmcp.vercel.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-vercel-flightsweeper-webmcp-public:
    url: "https://flightsweeper-webmcp.vercel.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-vercel-flightsweeper-webmcp-public": {
      "Transport": "http",
      "Url": "https://flightsweeper-webmcp.vercel.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-vercel-flightsweeper-webmcp-public -t streamable-http -u 'https://flightsweeper-webmcp.vercel.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-vercel-flightsweeper-webmcp-public": {
      "type": "http",
      "url": "https://flightsweeper-webmcp.vercel.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-21 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 80, +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-06 (score 79, +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.

## MCP tools (4)

### `get_challenge_capabilities` (~46 tokens)

Get Challenge Capabilities

Use this when an agent needs to describe the public FlightSweeper WebMCP challenge and its synthetic-only boundary. Do not use it for real travel transactions or private data.

Output parameters:

- `canonicalUrl` (string)
- `mode` (string)
- `name` (string)
- `realTransactions` (boolean)
- `remoteMcpToolCount` (integer)
- `webmcpToolCount` (integer)

### `get_flight_tool_contracts` (~48 tokens)

Get Flight Tool Contracts

Use this when an agent needs to list the browser-local WebMCP tool contracts without executing or mutating a mission. Do not use it for real travel transactions or private data.

Output parameters:

- `lifecycle` (string)
- `state` (string)
- `tools` (array)

### `get_sandbox_inventory` (~39 tokens)

Get Sandbox Inventory

Use this when an agent needs to describe the bounded synthetic inventory used by the challenge. Do not use it for real travel transactions or private data.

Output parameters:

- `caveat` (string)
- `containsPersonalData` (boolean)
- `defaultRoute` (string)
- `kind` (string)
- `routeMode` (string)
- `supplierConnectivity` (boolean)

### `get_safety_model` (~48 tokens)

Get Safety Model

Use this when an agent needs to describe FlightSweeper's application-enforced policy, revocation, and idempotency model. Do not use it for real travel transactions or private data.

Output parameters:

- `authority` (string)
- `idempotency` (string)
- `policy` (string)
- `privacy` (string)
- `revocation` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-vercel-flightsweeper-webmcp-public/flightsweeper-webmcp#diagnostics

## Score history

- 2026-09-21: 86
- 2026-09-20: 85
- 2026-09-19: 85
- 2026-09-18: 84
- 2026-09-17: 84
- 2026-09-16: 83
- 2026-09-15: 83
- 2026-09-14: 82
- 2026-09-13: 82
- 2026-09-12: 81
- 2026-09-11: 81
- 2026-09-10: 80
- 2026-09-09: 80
- 2026-09-08: 80
- 2026-09-07: 79
- 2026-09-06: 79
- 2026-09-05: 78
- 2026-09-04: 78
- 2026-09-03: 77
- 2026-09-02: 77
- 2026-09-01: 76
- 2026-08-31: 76
- 2026-08-30: 75
- 2026-08-29: 75
- 2026-08-28: 74

## Common questions

### What is the FlightSweeper MCP server?

FlightSweeper is an MCP server listed in the public MCP registry as app.vercel.flightsweeper-webmcp/public. Anonymous public tools for FlightSweeper. See the published agent boundary before use. This page covers its hosted endpoint (https://flightsweeper-webmcp.vercel.app/mcp).

### Is the FlightSweeper MCP server safe to use?

FlightSweeper scores 86 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 FlightSweeper MCP server expose?

FlightSweeper exposes 4 tools: get_challenge_capabilities, get_flight_tool_contracts, get_sandbox_inventory, get_safety_model. Their descriptions and schemas cost roughly 181 tokens of context every time the server is loaded.

### Does the FlightSweeper MCP server require authentication?

No. We connected to FlightSweeper without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the FlightSweeper MCP server still maintained?

FlightSweeper is still listed as active in the MCP registry. We last reached this channel on 21 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://flightsweeper-webmcp.vercel.app/mcp
- Repository: https://github.com/raintree-technology/flightsweeper-webmcp
- Changelog RSS feed: https://verifymcp.io/servers/app-vercel-flightsweeper-webmcp-public/flightsweeper-webmcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-vercel-flightsweeper-webmcp-public/flightsweeper-webmcp.json
- HTML version of this page: https://verifymcp.io/servers/app-vercel-flightsweeper-webmcp-public/flightsweeper-webmcp