
BookingTruth Booking Assurance
com.bookingtruthPublished by bookingtruth.comOfficial publisherv0.1.1Updated Oct 24, 2026
Verifies travel bookings against supplier-authoritative evidence; honest UNKNOWN verdicts.
Overview
A remote MCP endpoint that lets an assistant verify travel bookings against supplier-authoritative evidence, returning honest UNKNOWN verdicts when proof is not
- What you can do
- Verify travel bookings against supplier-authoritative evidence and return a verdict for each one, including an honest UNKNOWN result when the evidence does not settle the question. No tool list is published, so the exact operations are not documented; the description centers on booking verification rather than booking or changing travel.
- When to use it
- Useful when an assistant needs to check whether a travel booking is genuine or matches supplier records, and when an explicit UNKNOWN answer is preferable to a guess. Not intended for making, changing or cancelling bookings based on the available description.
- Requirements
- A remote streamable HTTP endpoint at the provider's API host; no local runtime, package, environment variables or headers are declared. The manifest declares no authentication, so whether an account or key is needed is not stated.
Installation
In SourceWeft
- Open BookingTruth Booking Assurance in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.bookingtruth%2Fbookingtruth/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"bookingtruth-booking-assurance": {
"type": "http",
"url": "https://api.bookingtruth.com/mcp"
}
}
}README
This repository has no README.
Tools
0Version history
2- v0.1.1LatestSep 27, 2026
- v0.1.0Sep 27, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.