Skip to content
Bonis Systems logo

Bonis Systems MCP server

Which servers in the official MCP registry are Bonis Systems's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-24

← Back to Bonis Systems

Whose server it is
  • Registry namecom.bonissystems/booking-requestverified in the MCP registry

The registry name sits under bonissystems.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-24
  • Stateanswerschecked 2026-10-24
  • Tools3
  • Server calls itselfagentcy-booking
  • Server version1.0.0
  • Protocol version2025-03-26

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 131 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-10-24
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer183 ms
  • Space in an agent's context≈ 780 tokensthe definitions of all its tools (3), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
  • Not saying whether it only reads or can destroy: 3 of 3

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers3 tools · read 2026-10-24
  • 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…

  • 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…

  • 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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

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

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://bonissystems.com/api/knox/agents/booking-request/mcp as a custom connector in the settings.

Other servers listed as Bonis Systems's
  • com.bonissystems/compliance-batchanswers, 1 toolsverified in the MCP registry
  • com.bonissystems/content-provenanceanswers, 2 toolsverified in the MCP registry
  • com.bonissystems/knox-anchornot asked yetverified in the MCP registry
  • com.bonissystems/ofac-sdn-screeningnot asked yetverified in the MCP registry
  • com.bonissystems/registry-expansionnot asked yetverified in the MCP registry
  • com.bonissystems/sstv-decodernot asked yetverified in the MCP registry
  • com.bonissystems/trustai-verifynot asked yetverified in the MCP registry

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.