What this kind of tool is for
- Chain multi-step workflows across the other tools in this directory.
- Run a scheduled or triggered job instead of retyping the same request.
- Have your agent watch a feed, queue, or repo and act on new items.
How to compare servers like this
- Trigger model:
- Understand what starts the automation — a command, a schedule, or an event — before relying on it.
- Blast radius:
- Prefer tools that hand you a review point before an irreversible action runs.
- Chaining cost:
- Each chained step adds a failure point; keep critical paths on the fewest tools.
- Maintenance signal:
- Automations break quietly; a maintained tool is the difference between repair and rediscovery.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the Booking Request MCP server?
Self-authenticating booking-request receipt anchored to the Knox chain; never represents a person.
How to install Booking Request
Copy-paste configuration for popular MCP clients.
{
"mcpServers": {
"booking-request": {
"url": "https://bonissystems.com/api/knox/agents/booking-request/mcp"
}
}
}Related MCP servers
Check whether a NAICS code aligns with a vertical: a routing-for-review signal, not a determination.
Anchor a content-creation event to the Knox chain; returns a C2PA-aligned, FRE 902-shaped bundle.
Bitcoin-anchored, tamper-evident audit-permanence layer for AI agents, FRE 902(13)/(14)-shaped.
Screen a name against the U.S. Treasury OFAC SDN list. Information, not a compliance determination.
Public-registry routing map by entity kind. Read-only reference data, not a determination.
Decode an SSTV audio recording and anchor its fingerprint and image hash to the Knox event chain.