Home / MCP registry index / ch.antevo/mandates
Antevo Mandates
ch.antevo/mandates in the official MCP registry.
Endpoint https://api.antevo.ch/mcp/mandates/mcp. Source: github.com/ANTEVO-CH/antevo-mcp.
The registry describes it as: Your client book: who is due a review, what their mandate allows, and what has moved.
We read its 24 tools on 2026-10-26. 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
get_succession_scan generate_meeting_brief list_documents get_document_detail get_eam_clients get_client_dossier get_client_reviews_due get_client_team create_eam_client update_eam_client convert_prospect complete_review assign_team_member get_client_goals create_client_goal update_client_goal delete_document create_share_link upload_document update_document extract_document_data get_email_messages get_email_detail link_email_to_client
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ch-antevo-mandates)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.