FlightSweeper
REMOTE · FLIGHTSWEEPER-WEBMCP.VERCEL.APP · SCANNED SEP 21
Anonymous public tools for FlightSweeper. See the published agent boundary before use.
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 203 tokens (~50/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 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.
remote · flightsweeper-webmcp.vercel.app
claude mcp add --transport http app-vercel-flightsweeper-webmcp-public 'https://flightsweeper-webmcp.vercel.app/mcp'
{
"mcpServers": {
"app-vercel-flightsweeper-webmcp-public": {
"url": "https://flightsweeper-webmcp.vercel.app/mcp"
}
}
} {
"servers": {
"app-vercel-flightsweeper-webmcp-public": {
"type": "http",
"url": "https://flightsweeper-webmcp.vercel.app/mcp"
}
}
} [mcp_servers.app-vercel-flightsweeper-webmcp-public] url = "https://flightsweeper-webmcp.vercel.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-vercel-flightsweeper-webmcp-public": {
"type": "remote",
"url": "https://flightsweeper-webmcp.vercel.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-vercel-flightsweeper-webmcp-public --url 'https://flightsweeper-webmcp.vercel.app/mcp' --transport streamable-http
mcp_servers:
app-vercel-flightsweeper-webmcp-public:
url: "https://flightsweeper-webmcp.vercel.app/mcp" {
"McpServers": {
"app-vercel-flightsweeper-webmcp-public": {
"Transport": "http",
"Url": "https://flightsweeper-webmcp.vercel.app/mcp"
}
}
} assistant mcp add app-vercel-flightsweeper-webmcp-public -t streamable-http -u 'https://flightsweeper-webmcp.vercel.app/mcp'
{
"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.
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.
- 21 Sept 26 +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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 8 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.
- 6 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.
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 21 Sept 2026 · Probed https://flightsweeper-webmcp.vercel.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | f7911168ffa7d0f4135e24792e7a52a8 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of flightsweeper-webmcp.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self' data:; connect-src 'self'; object-src 'none'; base-uri 'none'; frame-ancestors 'none'; form-action 'self' |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
| permissions-policy | tools=(self), camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://flightsweeper-webmcp.vercel.app/mcp | Verified | 200 | |
| http (plaintext) | http://flightsweeper-webmcp.vercel.app/mcp | HTTPS enforced | 308 | https://flightsweeper-webmcp.vercel.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 →
get_challenge_capabilities Get Challenge Capabilities ~46
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| canonicalUrl | string | yes | – |
| mode | string | yes | – |
| name | string | yes | – |
| realTransactions | boolean | yes | – |
| remoteMcpToolCount | integer | yes | – |
| webmcpToolCount | integer | yes | – |
No examples provided.
get_flight_tool_contracts Get Flight Tool Contracts ~48
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| lifecycle | string | yes | – |
| state | string | yes | – |
| tools | array | yes | – |
No examples provided.
get_safety_model Get Safety Model ~48
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| authority | string | yes | – |
| idempotency | string | yes | – |
| policy | string | yes | – |
| privacy | string | yes | – |
| revocation | string | yes | – |
No examples provided.
get_sandbox_inventory Get Sandbox Inventory ~39
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| caveat | string | yes | – |
| containsPersonalData | boolean | yes | – |
| defaultRoute | string | yes | – |
| kind | string | yes | – |
| routeMode | string | yes | – |
| supplierConnectivity | boolean | yes | – |
No examples provided.
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.