‹ directory
83MCP SCORE
B
weekendflights
https://weekendflights.app/mcp
3 tools~1.4k tok/req0% annot.proto 2026-07-28
Score by pillar
Security ·20100
Tool design ·18100
Schemas / desc ·1680
Reliability ·14100
Context-cost ·1265
Compliance ·1270
Coverage ·850
reliability: LOW (T1 single-shot, not credited - requires T3 >=24h)
Context-cost
1.4ktokens for
tools/listPaid on every request. Lean footprint for 3 tools.
this server1.4k
median≈ 3k
MCP primitive coverage
the quality score covers tools3
Tools
0
Resources · none
0
Prompts · none
Why this score — causal attribution
Each penalty: measure → mechanism → effect → Δscore.
Compliance · MEDIUM−3.6
0 declared annotations → destructiveHint/openWorldHint missing -> worst-case defaults → the tool is treated as destructive & open-world by clients
Badge — paste it in your README
[](https://checkmcp.dev/report?url=https%3A%2F%2Fweekendflights.app%2Fmcp)Own this server?Get verified — fresh re-audit, badge if you pass ›
About weekendflights — FAQ
Is the weekendflights MCP server safe to use?+
CheckMCP audited weekendflights and gave it an MCP Score of 83/100 (grade B) — good — only minor issues. The audit runs an OWASP MCP Top 10 security pass (tool poisoning, hardcoded secrets, command injection, the lethal trifecta) against the live endpoint; see the per-pillar breakdown and the "why this score" attribution on this page, and re-audit anytime at checkmcp.dev.
What is the MCP Score of weekendflights?+
weekendflights scores 83/100 (grade B) on CheckMCP's vendor-neutral audit across six weighted pillars — security, tool design, schemas, context-cost, compliance and coverage — with reliability measured and shown but not yet credited.
How many tools does weekendflights expose, and what is its context cost?+
weekendflights exposes 3 tools, and its tools/list response costs roughly 1.4k tokens — paid on every request your agent makes to it. Lower is better for your context budget.
How was weekendflights scored?+
By probing the live MCP endpoint (https://weekendflights.app/mcp), inspecting its tools, schemas and protocol compliance, running an OWASP MCP Top 10 security pass, and measuring the token cost of tools/list — then attributing every penalty as measure → mechanism → effect. The methodology is open: checkmcp.dev/#methodology.