C-

npm:airtreks-mcp

Item: npm:airtreks-mcp
Rating: 70
Author: wmcp.sh

https://www.npmjs.com/package/airtreks-mcp

70/100 · MCP Trust Grade · checked 2h ago · MCP 1.0.1

What it offers — 7 tools · Developer Tools

plan_route

The primary entry point for any multi-city trip. Give it your cities — it automatically evaluates Star Alliance RTW, oneworld RTW, AND custom mixed-ca

trip_idea_create

Create a trip idea in AirTreks APEX system — hands off to a human consultant. Automatically runs plan_route to include full routing analysis, carrier

route_validate

Validate a multi-city flight routing for feasibility. Checks alliance carrier rules, identifies dead legs, warns about poison carriers, and estimates

route_suggest

Get suggested multi-stop flight routings based on regions, direction, and alliance preference. Returns up to 3 proven routing templates with bookabili

hub_check

Check the best connection between two airports. Identifies dead legs (routes that fail on alliance fares), suggests hub routing fixes, and shows prove

fare_product_match

Recommend the best fare product type for a route — RTW, Circle Pacific, Circle Atlantic, Open Jaw, or Custom Multi-City. Considers stop count, directi

custom_route_build

Break a complex multi-city itinerary into individually-ticketable segments with carrier recommendations. Handles routes that don

Spec / packaging20%100

✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 7 tool(s) detected in source

Security (OWASP MCP)30%25

⚠ references sensitive file paths / env secrets
scanned 6 source files

Maintenance / popularity20%92

published within 90 days
2 published versions

Tool hygiene15%70

no TypeScript types
3 runtime deps

Transparency / provenance15%90

✓ public repository linked
✓ ISC license
230 weekly downloads

Findings

WARNMCP08 References sensitive file paths / environment secrets.

INFO Static analysis of npm package airtreks-mcp@1.0.1 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.

Grade another server

We re-grade npm:airtreks-mcp on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:airtreks-mcp grade C-

Share on X Open card image

https://wmcp.sh/mcp/grade/npm%3Aairtreks-mcp

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade C-](https://wmcp.sh/mcp/grade/npm%3Aairtreks-mcp/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Aairtreks-mcp)

HTML

<a href="https://wmcp.sh/mcp/grade/npm%3Aairtreks-mcp"><img src="https://wmcp.sh/mcp/grade/npm%3Aairtreks-mcp/badge.svg" alt="MCP Trust Grade C- · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.