Home / MCP registry index / ch.antevo/executive

Antevo Executive Brief

ch.antevo/executive in the official MCP registry. Endpoint https://api.antevo.ch/mcp/executive/mcp. Source: github.com/ANTEVO-CH/antevo-mcp.

The registry describes it as: Market and world intelligence — the daily editorial read, risk radar and dated archive.

We read its 15 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

list_capabilities get_executive_brief list_executive_notes get_executive_note get_executive_desk get_market_snapshot get_indices get_world_events get_risk_radar track_risk_evolution get_catalysts search_macro_indicators list_coverage get_macro_series get_coverage

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/ch-antevo-executive/badge.svg)](https://lazaretto.dev/mcp-registry/ch-antevo-executive)

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.