https://mcp.b2a.bluepillow.com/mcp ↗
Neutral hotel & stay price comparison for AI agents: live prices from 16+ booking operators. No signup. Blue Pillow consolidates live availability, per-operator pricing, ratings and booking links across millions of properties — hotels, B&Bs, apartments, vacation rentals, farmstays, hostels, villas and resorts. One query returns the multi-source price comparison an agent would otherwise have to assemble by visiting each booking site, with date-specific quotes, per-operator scarcity signals and free-cancellation flags. **No signup, no OAuth, no card.** The `b2a_get_key` tool issues a free anonymous key in-band; it is permanent and reusable across sessions. **Tools** - `b2a_get_key` — issue a free anonymous API key - `resolve_destination` — turn a place name into a destination id - `discover_destinations_near` — fan out sub-destinations from coordinates, for region-level intents - `search_stays` — ranked search across operators for a location and stay parameters - `get_property_details
Blue Pillow Hotels & Stays is a remote MCP server published at mcp.b2a.bluepillow.com. It has been probed 7 times since 9/10/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 344 ms, placing it among the faster endpoints. It offers a narrow, focused set of 6 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
search_stays — Description cuts off mid-sentence, missing critical details about ranking logic.get_property_details — Ambiguous 'headline rating' definition; unclear if it includes breakdowns.resolve_destination — Unclear if coordinates are required or optional in input parameters.b2a_get_key — No input parameters defined despite being a key-issuing tool.Risk: medium
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/bluepillow-hotels)<a href="https://mcpmetrics.io/servers/bluepillow-hotels"><img src="https://mcpmetrics.io/badge/bluepillow/hotels/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-11 11:20:19 | Legacy | 400 | 275 | 200 | 272 | 2025-11-25 |
| 2026-09-11 09:28:19 | Legacy | 400 | 344 | 200 | 317 | 2025-11-25 |
| 2026-09-11 07:35:54 | Legacy | 400 | 399 | 200 | 396 | 2025-11-25 |
| 2026-09-11 05:44:28 | Legacy | 400 | 276 | 200 | 271 | 2025-11-25 |
| 2026-09-11 03:50:39 | Legacy | 400 | 533 | 200 | 548 | 2025-11-25 |
| 2026-09-11 01:59:45 | Legacy | 400 | 417 | 200 | 419 | 2025-11-25 |
| 2026-09-10 21:16:35 | Unknown | 404 | 323 | 404 | 319 | — |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.