Home / MCP registry index / com.pinsvit/api
Pinsvit
com.pinsvit/api in the official MCP registry.
Endpoint https://pinsvit.com/api/v1/mcp.
The registry describes it as: Find and book local businesses, or run yours with Pinsvit Business: bookings, front desk, bills.
We read its 32 tools on 2026-10-23. 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
accept_booking add_booking_note cancel_booking create_booking create_comment create_event create_post decline_booking delete_comment delete_post find_booking_times find_place_customers get_booking get_booking_bill get_comments get_current_country_code get_current_user_details get_month_availability get_place get_place_services get_post get_publishing_media_keys list_my_bookings list_my_places list_place_booking_requests list_place_bookings mark_no_show ping record_bill_payment search_events_near search_places search_posts_near
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-pinsvit-api)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.