# BookingTruth Booking Assurance (remote · api.bookingtruth.com)

Verifies travel bookings against supplier-authoritative evidence; honest UNKNOWN verdicts.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `api.bookingtruth.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/com-bookingtruth-bookingtruth/api.md), [page](https://verifymcp.io/servers/com-bookingtruth-bookingtruth/api)

## Channel facts

- Endpoint: `https://api.bookingtruth.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-29.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 83/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 209 tokens (~52/item across 4 items; 2 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the BookingTruth Booking Assurance MCP server?

BookingTruth Booking Assurance is a hosted endpoint at https://api.bookingtruth.com/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.

### Claude

```bash
claude mcp add --transport http com-bookingtruth-bookingtruth 'https://api.bookingtruth.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-bookingtruth-bookingtruth": {
      "url": "https://api.bookingtruth.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-bookingtruth-bookingtruth": {
      "type": "http",
      "url": "https://api.bookingtruth.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-bookingtruth-bookingtruth]
url = "https://api.bookingtruth.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-bookingtruth-bookingtruth": {
      "type": "remote",
      "url": "https://api.bookingtruth.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-bookingtruth-bookingtruth --url 'https://api.bookingtruth.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-bookingtruth-bookingtruth:
    url: "https://api.bookingtruth.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-bookingtruth-bookingtruth": {
      "Transport": "http",
      "Url": "https://api.bookingtruth.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-bookingtruth-bookingtruth -t streamable-http -u 'https://api.bookingtruth.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-bookingtruth-bookingtruth": {
      "type": "http",
      "url": "https://api.bookingtruth.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-29 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-28 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 66)

First indexed and scored.

## MCP tools (2)

### `booking_check` (~88 tokens)

Verify a booking (check)

Parse booking/confirmation documents (emails, receipts) and return reconciled booking-state verdicts: confirmed/held/pending/cancelled/unknown, each with a citable proof packet. CONFIRMED is returned only on supplier-authoritative evidence; anything weaker returns UNKNOWN plus the indicated state. Sandbox: free, no signup.

Input parameters:

- `documents` (array, required): Raw booking documents to parse and reconcile.

Output parameters:

- `bookings` (array): Reconciled bookings with verdicts.

### `supplier_coverage` (~31 tokens)

Supplier coverage list

List suppliers BookingTruth can currently parse or look up, with per-supplier status (seeded/planned).

Output parameters:

- `coverage` (array): Per-supplier parser/lookup coverage.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-bookingtruth-bookingtruth/api#diagnostics

## Score history

- 2026-09-29: 67
- 2026-09-28: 66
- 2026-09-27: 66

## Common questions

### What is the BookingTruth Booking Assurance MCP server?

BookingTruth Booking Assurance is an MCP server listed in the public MCP registry as com.bookingtruth/bookingtruth. Verifies travel bookings against supplier-authoritative evidence; honest UNKNOWN verdicts. This page covers its hosted endpoint (https://api.bookingtruth.com/mcp).

### Is the BookingTruth Booking Assurance MCP server safe to use?

BookingTruth Booking Assurance scores 67 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 BookingTruth Booking Assurance MCP server expose?

BookingTruth Booking Assurance exposes 2 tools: booking_check, supplier_coverage. Their descriptions and schemas cost roughly 119 tokens of context every time the server is loaded.

### Does the BookingTruth Booking Assurance MCP server require authentication?

No. We connected to BookingTruth Booking Assurance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the BookingTruth Booking Assurance MCP server still maintained?

BookingTruth Booking Assurance is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.bookingtruth.com/mcp
- Repository: https://github.com/bookingtruth/bookingtruth-mcp
- Website: https://api.bookingtruth.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-bookingtruth-bookingtruth/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-bookingtruth-bookingtruth/api.json
- HTML version of this page: https://verifymcp.io/servers/com-bookingtruth-bookingtruth/api