mcp server
Booking Request
Self-authenticating booking-request receipt anchored to the Knox chain; never represents a person.
Description as published by the maintainer. Source
- version 1.0.0
- active
active — Registry entry last updated 2026-06-24.
What this server can do
3 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
list_represented_agents(livenessFilter)- 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_booking(brief, notes, startBy, agentSlug, archetype, budgetUsdMax, contactEmail, contactKnoxKeyId)- 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. Required: agentSlug, brief.
verify_booking(hash)- 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>. Required: hash.
Last successful function declaration observed on . Source: https://bonissystems.com/api/knox/agents/booking-request/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://bonissystems.com/api/knox/agents/booking-request/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-24 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-24 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 3 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | bonissystems.com | |
| mcp endpoint status | ok | The server listed 3 functions when asked. | as of probe | bonissystems.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json