Home / MCP registry index / au.com.nexwin/nexwin
Nexwin
au.com.nexwin/nexwin in the official MCP registry.
Endpoint https://mcp.nexwin.com.au/mcp.
The registry describes it as: Check bookings, review calls and chats, and manage appointments in your Nexwin AI receptionist.
We read its 22 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
about_nexwin get_bookings list_team_members get_call_chat_history get_call_chat_detail get_account_usage_summary create_booking reschedule_booking cancel_booking get_activity_summary find_customer get_ai_setup update_ai_setup restore_ai_setup_version update_service_area invite_team_member add_team_member update_team_member remove_team_member list_assets add_assets import_customers
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/au-com-nexwin-nexwin)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.