Back to MCP servers
● healthy

# RowHint MCP Server Airline seat quality intelligence via MCP. Per-seat quality scores (1-10) with plain-English notes for **66+ aircraft configurations** across 10 US airlines. Every score is hand-verified against live airline seat maps. ## Setup Add to your Claude Desktop config: ```json { "mcpServers": { "rowhint": { "url": "https://mcp.rowhint.com/mcp" } } } ``` No API key required. All 5 tools are free. ## Key Features - Per-seat quality scores (1-10) with transparent methodology - Plain-English notes explaining why each seat scores the way it does - Best seat finder filtered by cabin class - Side-by-side seat comparison with score differences and summary - Windowless window seat detection - 66+ hand-verified configs across AA, DL, UA, WN, B6, AS, HA, F9, NK, G4 ## Available Tools 1. **`rowhint_get_seat_score`** — Get quality score and notes for a specific seat 2. **`rowhint_get_best_seats`** — Find the highest-rated seats by cabin class 3. **`rowhint_compare_seats`** — Compare two seats side by side 4. **`rowhint_get_config_overview`** — Get full seat map overview for an aircraft 5. **`rowhint_get_windowless_seats`** — Find window seats that actually have no window ## Use Cases - Travelers asking AI assistants "What's the best seat on my Delta A321neo flight?" - Travel app developers adding seat quality data to booking tools - AI travel agents making personalized seat recommendations - Corporate travel tools optimizing seat assignments ## FAQ **Does it cover international airlines?** Not yet — currently covers 10 US airlines. International carriers are on the roadmap. **How are scores calculated?** Each seat is scored 1-10 based on legroom, recline, proximity to galley/lavatory, window alignment, and hardware. Full methodology at [rowhint.com](https://rowhint.com). **Is an API key required?** No. All tools are free with no authentication required. **How often is the data updated?** Configurations are hand-verified against live airline booking sites and updated when airlines change their layouts.

Transport
streamable-http
Auth
smithery_api_key
Cost
—
Protocol revision
2025-11-25
negotiated, not declared

MCP readiness

B · 86/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 10/10 initialize and tools/list both answered.
Live MCP endpoint 23/25 Endpoint answers the MCP initialize handshake (6325 ms); very slow response -2.
Protocol revision 8/10 Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 15/15 31/31 probes succeeded over 30 days (100%).
Tool declaration 10/10 Lists 8 tool(s) with descriptions.
Verified identity 5/10 Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags 4/5 seen in a source within 7 days.
Auth declaration 2/5 Declares credential scheme: smithery_api_key.
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Very slow (6325 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness
Higher than 80% of peers
This listing 86 · peer median 81
Latency
Faster than 22% of peers
This listing 595 ms · peer median 326 ms

Where it loses the most points, and how to win them back

  • Verified identity −5 — Claim the listing and prove control of its domain.
    Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
  • Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
    Now: Declares credential scheme: smithery_api_key.
  • Live MCP endpoint −2 — Answer initialize and tools/list at the declared endpoint.
    Now: Endpoint answers the MCP initialize handshake (6325 ms); very slow response -2.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

How to connect

MCP endpoint (streamable-http)
https://server.smithery.ai/rowhint-ntm5/RowHint/mcp
JSON-RPC initialize probe
curl -X POST https://server.smithery.ai/rowhint-ntm5/RowHint/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://rowhint.com/
Listed at (smithery)
https://rowhint.com/