Home / MCP registry index / com.hamptonsverified/hamptons-verified
Hamptons Verified
com.hamptonsverified/hamptons-verified in the official MCP registry.
Endpoint https://hamptonsverified.com/api/ai/mcp.
The registry describes it as: Verified Hamptons & North Fork data: open now, events, beaches, permits, closures.
We read its 19 tools on 2026-10-27. 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
plan_my_day search_places find_shops whats_open_now upcoming_events beach_info parking_permit_rules recently_closed where_to_stay getting_here things_to_do community_help picnic_spots golden_hour work_out play_sport tap_water urgent_care benefit_galas
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-hamptonsverified-hamptons-verified)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.