Home / MCP registry index / io.usefulapi/booqable

Booqable MCP by usefulapi

io.usefulapi/booqable in the official MCP registry. Endpoint https://booqable.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: Browse rental orders, customers, products and availability, and create bookings in Booqable.

We read its 21 tools on 2026-10-31. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http booqable https://booqable.usefulapi.io/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "booqable": {
      "url": "https://booqable.usefulapi.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"booqable","type":"http","url":"https://booqable.usefulapi.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

booqable_get_company booqable_list_orders booqable_get_order booqable_list_customers booqable_get_customer booqable_list_product_groups booqable_list_products booqable_check_inventory_availability booqable_get_availability_calendar booqable_list_plannings booqable_list_documents booqable_list_payments booqable_list_locations booqable_list_notes booqable_create_customer booqable_update_customer booqable_create_order booqable_update_order booqable_book_product booqable_transition_order_status booqable_create_note

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): d1651429e6ae3461. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-usefulapi-booqable/badge.svg)](https://lazaretto.dev/mcp-registry/io-usefulapi-booqable)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.