Skip to content

Booking Request

by bonissystems.com · remote · no sign-in to list tools · v1.0.0 · published by com.bonissystems

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

Changes · 2
CompareRegistry entry

3 tools: 2 change things and 1 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Changes things 2Claude Code: ask
  • request_bookingAnchor a booking request for a represented Bonis Concierge agent.No findings

    Why it is in this group

    • The name "request_booking" says "request": a word for a change.
    Description, as the server wrote it
    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_bookingVerify an anchored booking-request record.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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>.
Only reads 1Claude Code: allow
  • list_represented_agentsEnumerate the Bonis Concierge represented-agent roster.No findings

    Why it is in this group

    • The name "list_represented_agents" says "list": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__booking-request__list_represented_agents"
    ],
    "ask": [
      "mcp__booking-request__request_booking",
      "mcp__booking-request__verify_booking"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as booking-request. Review it before you use it.