Home / MCP registry index / io.usefulapi/tokeet
Tokeet MCP by usefulapi
io.usefulapi/tokeet in the official MCP registry.
Endpoint https://tokeet.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read Tokeet rentals, rates, guests, tasks and expenses; add guests, notes and tasks.
We read its 24 tools on 2026-10-21. 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.
Tools it advertises
tokeet_get_current_user tokeet_list_users tokeet_get_user tokeet_list_rentals tokeet_get_rental tokeet_list_rentals_by_owner tokeet_get_rental_availability tokeet_list_rates tokeet_list_guests tokeet_get_guest tokeet_get_guest_by_email tokeet_list_tasks tokeet_get_task tokeet_list_expenses tokeet_get_expense tokeet_list_templates tokeet_get_template tokeet_list_triggers tokeet_create_guest tokeet_update_guest tokeet_add_guest_note tokeet_record_guest_interaction tokeet_create_task tokeet_update_task
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-tokeet)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.