mcp-registry/ch.antevo/mandates · v1.12.4
As of 2026-10-22 21:28 UTC, the Antevo Mandates MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 4 minutes.
Your client book: who is due a review, what their mandate allows, and what has moved.
Claude Code
claude mcp add --transport http antevo-mandates-mcp-server https://api.antevo.ch/mcp/mandates/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"antevo-mandates-mcp-server": {
"type": "http",
"url": "https://api.antevo.ch/mcp/mandates/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
94 parameter(s) across 24 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
24 of 24 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
7 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~1,873 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 0 tool(s) removed and 6 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 24 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fch.antevo%2Fmandates/fixes
{
"name": "assign_team_member",
"description": "Assign a team member to an EAM client. role: PRIMARY, ADVISOR, SUPPORT. Needs a firm OWNER or ADMIN.",
"inputSchema": {
"type": "object",
"title": "assign_team_memberArguments",
"required": [
"client_id",
"member_id"
],
"properties": {
"role": {
"type": "string",
"title": "Role",
"default": "ADVISOR"
},
"firm_id": {
"type": "string",
"title": "Firm Id",
"default": ""
},
"client_id": {
"type": "string",
"title": "Client Id"
},
"member_id": {
"type": "string",
"title": "Member Id"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "convert_prospect",
"description": "Convert a prospect to an active client: creates the client's household and its\n primary entity, as the web's Convert does. entity_type: PERSON, COMPANY, TRUST,\n FOUNDATION (defaults from the client type). household_name defaults to the client's name.",
"inputSchema": {
"type": "object",
"title": "convert_prospectArguments",
"required": [
"client_id"
],
"properties": {
"confirm": {
"type": "boolean",
"title": "Confirm",
"default": false
},
"firm_id": {
"type": "string",
"title": "Firm Id",
"default": ""
},
"client_id": {
"type": "string",
"title": "Client Id"
},
"entity_type": {
"type": "string",
"title": "Entity Type",
"default": null
},
"household_name": {
"type": "string",
"title": "Household Name",
"default": null
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "create_client_goal",
"description": "Create a financial goal. goal_type: RETIREMENT, EDUCATION, PROPERTY, LEGACY, LIFESTYLE, EMERGENCY, MAJOR_PURCHASE, CUSTOM.",
"inputSchema": {
"type": "object",
"title": "create_client_goalArguments",
"required": [
"client_id",
"goal_type",
"goal_name"
],
"properties": {
"firm_id": {
"type": "string",
"title": "Firm Id",
"default": ""
},
"priority": {
"type": "integer",
"title": "Priority",
"default": 1
},
"client_id": {
"type": "string",
"title": "Client Id"
},
"goal_name": {
"type": "string",
"title": "Goal Name"
},
"goal_type": {
"type": "string",
"title": "Goal Type"
},
"description": {
"type": "string",
"title": "Description",
"default": null
},
"target_date": {
"type": "string",
"title": "Target Date",
"default": null
},
"target_amount": {
"type": "number",
"title": "Target Amount",
"default": null
},
"target_currency": {
"type": "string",
"title": "Target Currency",
"default": "CHF"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ch.antevo/mandates"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ch.antevo/mandates"}) over MCP.
complete_review ~247 tokensupload_document ~242 tokenscreate_client_goal ~240 tokenscreate_eam_client ~220 tokensconvert_prospect ~202 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fch.antevo%2Fmandates?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fch.antevo%2Fmandates?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fch.antevo%2Fmandates.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fch.antevo%2Fmandates.svg :target: https://glimind.com/server/mcp-registry%2Fch.antevo%2Fmandates?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:013f15226cdb1c45…, first seen 2026-10-17, included at leaf 10837 of 48,233. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable data servers · most reliable files servers · most reliable ml servers · most reliable productivity servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 21:28 UTC, the Antevo Mandates MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 4 minutes.
Antevo Mandates MCP server advertises 24 tools, including assign_team_member, complete_review, convert_prospect, create_client_goal, create_eam_client.
Point your MCP client at this streamable-http endpoint: https://api.antevo.ch/mcp/mandates/mcp
Glimind scanned all 24 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.