Home / MCP registry index / io.usefulapi/roller
ROLLER MCP by usefulapi
io.usefulapi/roller in the official MCP registry.
Endpoint https://roller.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Search bookings, check availability, and read guests, waivers and payments in ROLLER.
We read its 42 tools on 2026-11-14. 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 about every two weeks.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http roller https://roller.usefulapi.io/mcp{
"mcpServers": {
"roller": {
"url": "https://roller.usefulapi.io/mcp"
}
}
}code --add-mcp '{"name":"roller","type":"http","url":"https://roller.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.
claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
roller_get_venue roller_search_bookings roller_get_booking roller_get_booking_form_responses roller_get_company roller_list_products roller_get_product_availability roller_get_product_availability_calendar roller_get_price_rules roller_list_segments roller_get_guest roller_get_guest_multi_passes roller_get_signed_waiver roller_get_signed_waiver_form_responses roller_get_discount roller_list_modifier_groups roller_get_modifier_group roller_get_gift_card_balance roller_report_bookings roller_report_tickets roller_report_gift_cards roller_report_guests roller_report_attendance roller_report_signed_waivers roller_report_booking_signed_waivers roller_report_payments roller_report_revenue_entries roller_report_gx_scores roller_report_till_reconciliations roller_report_membership_redemptions roller_report_membership_statuses roller_report_membership_credits roller_report_guest_segment_members roller_report_products roller_report_modifiers roller_report_discounts roller_report_resources roller_report_devices roller_report_staff roller_report_roles roller_report_waivers roller_report_reporting_categories
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-11-14):
9dd9b15270e06dd5. 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.
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-roller)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. How tool poisoning works. What we found across the registry. Check another server.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.