Booking Request MCP Server

com.bonissystems/booking-request

answering

Booking Request is answering right now. Last checked moments ago. It exposes 3 tools.

Self-authenticating booking-request receipt anchored to the Knox chain; never represents a person.

Uptime history 39 hours of history

39 hours agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

257 ms

Response time

average over 24h

open, no key

Access

streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add booking-request --transport http https://bonissystems.com/api/knox/agents/booking-request/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "booking-request": {
      "url": "https://bonissystems.com/api/knox/agents/booking-request/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.booking-request]
url = "https://bonissystems.com/api/knox/agents/booking-request/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "booking-request": {
      "url": "https://bonissystems.com/api/knox/agents/booking-request/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "booking-request": {
      "url": "https://bonissystems.com/api/knox/agents/booking-request/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

represented

list_represented_agents

Enumerate the Bonis Concierge represented-agent roster. Returns slug, name, charter, bureau, archetype, liveness ('live' = verifiable POST endpoint and Knox event-chain integration today / 'charter' = description filed, integration in progress), and capability-page URL for each agent.

request

request_booking

Anchor a booking request for a represented Bonis Concierge agent. Returns a self-authenticating booking bundle: Knox anchor record + C2PA-aligned envelope (subset of C2PA 1.4 — adapted for booking events) + FRE 902(13)/(14)-shape representation affidavit. The agency does not adjudicate the merits of any booking, does not guarantee acceptance by the listed agent, does not handle payment under this primitive, and does not represent any natural person. Requires a Knox Bearer API key on the Authorization header — unauthenticated calls are rejected.

verify

verify_booking

Verify an anchored booking-request record. Given a SHA-256 anchor hash (the payload_hash from a prior request_booking call), return the anchor record, predecessor hash, sequence number, and timestamp. Public — no authentication required. The verification path is also accessible at GET /api/knox/verify?hash=<hash>.

Endpoints

URL	Transport	State	Latency	Checked
https://bonissystems.com/api/knox/agents/booking-request/mcp	streamable-http	answering	252 ms	0 min ago

Booking Request — questions

Answers built from our own checks of this server.

What can Booking Request do?

It exposes 3 tools, read directly from the server on our last check. Among them: list_represented_agents, request_booking, verify_booking. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Booking Request working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 257 ms. The bar chart above shows every period we have measured.

How do I connect Booking Request?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Booking Request need an API key?

No. Booking Request completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Booking Request?

It answers our handshake in 257 ms on average, which is faster than 52% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.