Antevo Mandates
REMOTE · API.ANTEVO.CH · 2 COMPONENTS · SCANNED SEP 24
Your client book: who is due a review, what their mandate allows, and what has moved.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1660 tokens (~69/item across 24 items; 24 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_document" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Antevo Mandates MCP server?
Antevo Mandates is a hosted endpoint at https://api.antevo.ch/mcp/mandates/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.antevo.ch
claude mcp add --transport http ch-antevo-mandates 'https://api.antevo.ch/mcp/mandates/mcp'
{
"mcpServers": {
"ch-antevo-mandates": {
"url": "https://api.antevo.ch/mcp/mandates/mcp"
}
}
} {
"servers": {
"ch-antevo-mandates": {
"type": "http",
"url": "https://api.antevo.ch/mcp/mandates/mcp"
}
}
} [mcp_servers.ch-antevo-mandates] url = "https://api.antevo.ch/mcp/mandates/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ch-antevo-mandates": {
"type": "remote",
"url": "https://api.antevo.ch/mcp/mandates/mcp",
"enabled": true
}
}
} openclaw mcp add ch-antevo-mandates --url 'https://api.antevo.ch/mcp/mandates/mcp' --transport streamable-http
mcp_servers:
ch-antevo-mandates:
url: "https://api.antevo.ch/mcp/mandates/mcp" {
"McpServers": {
"ch-antevo-mandates": {
"Transport": "http",
"Url": "https://api.antevo.ch/mcp/mandates/mcp"
}
}
} assistant mcp add ch-antevo-mandates -t streamable-http -u 'https://api.antevo.ch/mcp/mandates/mcp'
{
"mcpServers": {
"ch-antevo-mandates": {
"type": "http",
"url": "https://api.antevo.ch/mcp/mandates/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Stability: unverified → 0.03 ▲ functional
- “assign_team_member” made “firm_id” optional cosmetic
- “complete_review” made “firm_id” optional cosmetic
- “convert_prospect” made “firm_id” optional cosmetic
- “create_eam_client” made “firm_id” optional cosmetic
- “generate_meeting_brief” made “firm_id” optional cosmetic
- “get_client_dossier” made “firm_id” optional cosmetic
- “get_client_reviews_due” made “firm_id” optional cosmetic
- “get_client_team” made “firm_id” optional cosmetic
- “get_eam_clients” made “firm_id” optional cosmetic
- “get_email_detail” made “firm_id” optional cosmetic
- “get_email_messages” made “firm_id” optional cosmetic
- “get_succession_scan” made “firm_id” optional cosmetic
- “link_email_to_client” made “firm_id” optional cosmetic
- “update_eam_client” made “firm_id” optional cosmetic
- 14 Sept 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://api.antevo.ch/mcp/mandates/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.antevo.ch | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 6 Aug 2026 | 6 Feb 2027 | RSA 2048 | SHA256-RSA | 909fd7f3310a15b23f9995e4159bbf0 |
| SANs: api.antevo.ch | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.antevo.ch. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ch. | present | 58745 | 13 | Verified |
| antevo.ch. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.antevo.ch/.well-known/oauth-protected-resource/mcp/mandates/mcp"
Bearer resource_metadata="https://api.antevo.ch/.well-known/oauth-protected-resource/mcp/mandates/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self'; connect-src 'self' https://*.vestai.ai https://api.vestai.ai https://*.ciamlogin.com https://*.clerk.accounts.dev |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Protected resource metadata
| Document | https://api.antevo.ch/.well-known/oauth-protected-resource/mcp/mandates/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://api.antevo.ch/mcp/mandates/mcp |
| Authorisation server | https://api.antevo.ch |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.antevo.ch/mcp/mandates/mcp | Verified | 200 | |
| http (plaintext) | http://api.antevo.ch/mcp/mandates/mcp | HTTPS enforced | 301 | https://api.antevo.ch/mcp/mandates/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
assign_team_member ~59
Assign a team member to an EAM client. role: PRIMARY, SECONDARY, SUPPORT.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | yes | – |
| firm_id | string | – | – |
| member_id | string | yes | – |
| role | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
complete_review ~155
Record that this client's review is done, and schedule the next one. Stamps last_reviewed_at and moves next_review_date forward by next_review_months (default 12). Any notes are filed as an OBSERVATION note against the client. NOTE: this tool used to take a `review_id`. It queried eam_client_review, a table that exists in no schema, so it errored on every call and the id never had a referent. Review state is a pair of columns on the client row.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | yes | – |
| firm_id | string | – | – |
| next_review_months | integer | – | – |
| notes | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
convert_prospect ~40
Convert a prospect to active client status.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | yes | – |
| confirm | boolean | – | – |
| firm_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_client_goal ~106
Create a financial goal. goal_type: RETIREMENT, EDUCATION, PROPERTY, LIFESTYLE, CHARITABLE, LEGACY, LIQUIDITY, CUSTOM.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | yes | – |
| description | string | – | – |
| goal_name | string | yes | – |
| goal_type | string | yes | – |
| priority | integer | – | – |
| target_amount | number | – | – |
| target_currency | string | – | – |
| target_date | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_eam_client ~113
Create a new EAM client/prospect. client_type: INDIVIDUAL, COMPANY, TRUST. pipeline_stage: LEAD, PROSPECT, QUALIFIED, PROPOSAL, NEGOTIATION.
| Name | Type | Req | Description |
|---|---|---|---|
| client_type | string | – | – |
| confirm | boolean | – | – |
| display_name | string | yes | – |
| string | – | – | |
| firm_id | string | – | – |
| notes | string | – | – |
| phone | string | – | – |
| pipeline_stage | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_share_link ~59
Create a shareable link for a document. Link is valid for expires_in_hours (max 720 = 30 days).
| Name | Type | Req | Description |
|---|---|---|---|
| doc_id | string | yes | – |
| expires_in_hours | integer | – | – |
| household_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
delete_document ~42
Soft-delete a document (sets status to DELETED).
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| doc_id | string | yes | – |
| household_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
extract_document_data ~38
Trigger OCR / data extraction from a document. Returns extraction status.
| Name | Type | Req | Description |
|---|---|---|---|
| doc_id | string | yes | – |
| household_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
generate_meeting_brief ~57
Generate a full meeting brief for a client — 11 sections covering portfolio, compliance, macro, relationship health, next best conversation. Consumes credits.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | yes | – |
| firm_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_client_dossier ~44
Get full client dossier — profile, entities, AUM, review status, team assignments.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | yes | – |
| firm_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_client_goals ~36
Get financial goals for a client — retirement, education, property, etc. with progress.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_client_reviews_due ~42
Get compliance reviews due for a client, or all clients if client_id omitted.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | – | – |
| firm_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_client_team ~35
Get assigned team members for an EAM client.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | yes | – |
| firm_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_document_detail ~40
Get document metadata, ACLs, and share links for a specific document.
| Name | Type | Req | Description |
|---|---|---|---|
| doc_id | string | yes | – |
| household_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_eam_clients ~64
List EAM clients for a firm. Filter by status (ACTIVE/ARCHIVED), pipeline_stage, or search term.
| Name | Type | Req | Description |
|---|---|---|---|
| firm_id | string | – | – |
| pipeline_stage | string | – | – |
| search | string | – | – |
| status | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_email_detail ~44
Get full email with AI analysis — sentiment, summary, topics, compliance flags, suggested action.
| Name | Type | Req | Description |
|---|---|---|---|
| firm_id | string | – | – |
| message_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_email_messages ~86
List email messages for an EAM firm with AI analysis. Filter by client_id, priority (CRITICAL,HIGH,MEDIUM,LOW), category (INQUIRY,INSTRUCTION,UPDATE).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| client_id | string | – | – |
| firm_id | string | – | – |
| page | integer | – | – |
| priority | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_succession_scan ~35
Firm-wide succession urgency scan — identifies clients with incomplete succession planning (EAM).
| Name | Type | Req | Description |
|---|---|---|---|
| firm_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
link_email_to_client ~45
Link an email message to an EAM client record.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | yes | – |
| firm_id | string | – | – |
| message_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_documents ~45
List documents for a household. Optionally filter by category (STATEMENT, TAX, LEGAL, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| household_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_client_goal ~85
Update goal progress. status: ON_TRACK, AHEAD, BEHIND, AT_RISK, ACHIEVED, PAUSED, CANCELLED.
| Name | Type | Req | Description |
|---|---|---|---|
| current_amount | number | – | – |
| goal_id | string | yes | – |
| notes | string | – | – |
| status | string | – | – |
| target_amount | number | – | – |
| target_date | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_document ~59
Update document metadata — description, category, or tags (comma-separated).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| description | string | – | – |
| doc_id | string | yes | – |
| household_id | string | yes | – |
| tags | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_eam_client ~70
Update an EAM client record.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | yes | – |
| display_name | string | – | – |
| string | – | – | |
| firm_id | string | – | – |
| notes | string | – | – |
| phone | string | – | – |
| pipeline_stage | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
upload_document ~129
Initialize a document record. domain: WEALTH, TAX, LEGAL, COMPLIANCE, PERSONAL. category: STATEMENT, TAX_RETURN, WILL, TRUST_DEED, INSURANCE, CONTRACT, ID, OTHER. If base64_content is provided, the document blob is stored. Otherwise returns a doc_id for separate upload.
| Name | Type | Req | Description |
|---|---|---|---|
| base64_content | string | – | – |
| category | string | yes | – |
| confirm | boolean | – | – |
| description | string | – | – |
| domain | string | yes | – |
| file_name | string | yes | – |
| household_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the Antevo Mandates MCP server?
Antevo Mandates is an MCP server listed in the public MCP registry as ch.antevo/mandates. Your client book: who is due a review, what their mandate allows, and what has moved. This page covers its hosted endpoint (https://api.antevo.ch/mcp/mandates/mcp).
Is the Antevo Mandates MCP server safe to use?
Antevo Mandates scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Antevo Mandates MCP server expose?
Antevo Mandates exposes 24 tools: get_succession_scan, generate_meeting_brief, list_documents, get_document_detail, get_eam_clients, and 19 more. Their descriptions and schemas cost roughly 1,528 tokens of context every time the server is loaded.
Does the Antevo Mandates MCP server require authentication?
Yes. Antevo Mandates asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Antevo Mandates MCP server still maintained?
Antevo Mandates is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.