mcpbeat Sign in

Booking Request MCP Server

by bonissystems Your server? Claim it
answering

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

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

Uptime history 91 days of history · worst day 94%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
312 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 16 September 2026. No other catalogue keeps this.

13 Oct a tool changed the parameters it asks for request_booking
16 Sep a tool description was rewritten request_booking

Booking Request missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add booking-request --transport http https://bonissystems.com/api/knox/agents/booking-request/mcp
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "booking-request": {
      "type": "http",
      "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 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

URLTransportStateLatencyChecked
https://bonissystems.com/api/knox/agents/booking-request/mcp streamable-http answering 308 ms 9 min ago

Alternatives to Booking Request

same job, measured the same way
vault-ask
by erseni

Request and send secrets for AI agents, end-to-end encrypted and never shown in the chat.

164 installs/wk local only
SSTV Decoder
by bonissystems

Decode an SSTV audio recording and anchor its fingerprint and image hash to the Knox event chain.

2 tools answering
Dodo Payments Docs
by dodopayments

Semantic search over the current Dodo Payments documentation. No authentication required.

1 tools answering
Content Provenance
by bonissystems

Anchor a content-creation event to the Knox chain; returns a C2PA-aligned, FRE 902-shaped bundle.

2 tools answering
Scout
by dinewithscout

Find Resy restaurants and request reservations through Scout; the user approves every booking.

answering
Tenpace Review Router
by patrax

Human-authenticated setup for routing GitHub pull requests into the right Slack channel.

5 tools answering
Tenpace Review Router
by tenpace-app

Human-authenticated setup for routing GitHub pull requests into the right Slack channel.

5 tools answering
Fetch SCITT receipts and on-chain anchors for offline verification
by forestrie

Fetch a SCITT receipt, its genesis and on-chain accumulator for @forestrie/mcp-verify to verify

195 installs/wk local only

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 91 of 91 checks got a reply (100.0%), average response time 312 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 in the form 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 312 ms on average, which is faster than 46% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.