Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Antevo Executive Brief

REMOTE · API.ANTEVO.CH · 2 COMPONENTS · SCANNED OCT 3

Market and world intelligence — the daily editorial read, risk radar and dated archive.

0 this week 84 Trust /100
Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1724 tokens (~107/item across 16 items; 15 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 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
Install

How do I install the Antevo Executive Brief MCP server?

Antevo Executive Brief is a hosted endpoint at https://api.antevo.ch/mcp/executive/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

# add to Claude Code
claude mcp add --transport http ch-antevo-executive 'https://api.antevo.ch/mcp/executive/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "ch-antevo-executive": {
      "url": "https://api.antevo.ch/mcp/executive/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ch-antevo-executive": {
      "type": "http",
      "url": "https://api.antevo.ch/mcp/executive/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.ch-antevo-executive]
url = "https://api.antevo.ch/mcp/executive/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ch-antevo-executive": {
      "type": "remote",
      "url": "https://api.antevo.ch/mcp/executive/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ch-antevo-executive --url 'https://api.antevo.ch/mcp/executive/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ch-antevo-executive:
    url: "https://api.antevo.ch/mcp/executive/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ch-antevo-executive": {
      "Transport": "http",
      "Url": "https://api.antevo.ch/mcp/executive/mcp"
    }
  }
}
# add to Vellum
assistant mcp add ch-antevo-executive -t streamable-http -u 'https://api.antevo.ch/mcp/executive/mcp'
// mcp.json
{
  "mcpServers": {
    "ch-antevo-executive": {
      "type": "http",
      "url": "https://api.antevo.ch/mcp/executive/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 10 Sept 26 0
    • Stability: 0.97 → pass security
  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Sept 26 0
    • Schema quality: 1301 → 1724 ▼ functional
    • New tool “get_macro_series” functional
    • New tool “get_coverage” functional
    • New tool “list_coverage” functional
    • New tool “search_macro_indicators” functional
  • 31 Aug 26 0
    • Tool “track_risk_evolution” rewrote its description, which is the text the model reads security
    • Tool “get_world_events” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • “get_world_events” added an optional parameter “layers” cosmetic
    • “track_risk_evolution” added an optional parameter “detail” cosmetic
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 3 Oct 2026 · Probed https://api.antevo.ch/mcp/executive/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 No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
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=()

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/executive/mcp Verified 200
http (plaintext) http://api.antevo.ch/mcp/executive/mcp HTTPS enforced 301 https://api.antevo.ch/mcp/executive/mcp
MCP tools · 15 exposed · ~1,472 tokens

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 →

Tool Tokens
get_catalysts ~94

The forward calendar — dated events the Executive Brief is watching (data prints, decisions, deadlines), each with the signal to read from it and its category. Use days_ahead (1..90, default 14) to set the horizon. Answers 'what's coming up that could move things?'

NameTypeReqDescription
days_aheadstring––
marketstring––
scopestring––

Structured output declared, but exposes no named fields.

No examples provided.

get_coverage ~115

One coverage area's note in full — for example real-assets-shipping or real-assets-aviation. scope 'retail' (default) or 'institutional'; the institutional read is longer and assumes more. Optional as_of (YYYY-MM-DD) for a past edition, newest otherwise. Cheaper and more direct than pulling the whole brief to read one theme. Call list_coverage for the areas and their dates.

NameTypeReqDescription
areastringyes–
as_ofstring––
scopestring––

Structured output declared, but exposes no named fields.

No examples provided.

get_executive_brief ~178

The Antevo Executive Brief — today's editorial read on markets and world events: the hero takeaway, the regime, the themes that matter, key risks and a market snapshot. Pass as_of (YYYY-MM-DD) to retrieve the brief as it was published on a past date. scope: 'retail' or 'institutional'. The full brief is large; pass `sections` (comma-separated) to fetch only what you need — e.g. 'hero,regime,what_matters' for a quick read, 'signal' for the probability layer, or 'plain_language' for the desk's own jargon-free rendering (headline, decode, signal_read, theme_reads).

NameTypeReqDescription
as_ofstring––
marketstring––
scopestring––
sectionsstring––

Structured output declared, but exposes no named fields.

No examples provided.

get_executive_desk ~25

The longer-form desk read for today — analysis and research notes.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_executive_note ~82

One dated Executive Brief in full (YYYY-MM-DD) — the permanent record of what was published that day. Use after list_executive_notes to read a specific day, or to answer 'what did we say about X back then?'.

NameTypeReqDescription
as_ofstringyes–
marketstring––
scopestring––

Structured output declared, but exposes no named fields.

No examples provided.

get_indices ~44

Major indices with recent history — use days_back (1..365, default 30) to see how markets have moved over a period.

NameTypeReqDescription
days_backstring––

Structured output declared, but exposes no named fields.

No examples provided.

get_macro_series ~104

One macro series by ticker, newest first, with the date of its most recent observation stated on the response. These are QUARTERLY levels and they lag — the newest point is a quarter end, never today. Use search_macro_indicators to find the ticker. Optional since/until (YYYY-MM-DD) narrow the window.

NameTypeReqDescription
limitstring––
sincestring––
tickerstringyes–
untilstring––

Structured output declared, but exposes no named fields.

No examples provided.

get_market_snapshot ~23

Where markets stand right now — indices, FX, commodities, crypto.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_risk_radar ~114

The risk radar — what the Antevo Executive Brief judges could go wrong from here, each with its trend, impact, probability and why it matters, plus the regime it sits in and the indicators that would confirm or kill it. Pass as_of (YYYY-MM-DD) for the radar as it stood on a past date. For how risks have DEVELOPED over weeks, use track_risk_evolution.

NameTypeReqDescription
as_ofstring––
marketstring––
scopestring––

Structured output declared, but exposes no named fields.

No examples provided.

get_world_events ~184

Geopolitical events over a look-back window (days_back 1..90, default 7) — conflict, chokepoints, sanctions and related signals. The public cut. Pass layers to narrow — waterways, armed_conflicts, hotspots, regulatory, cyber, sanctions — comma-separated. All six together run large and two of them truncate; ask for one or two and those come back much deeper. row_limits on the response says what was in force, so you can tell a layer that ended from one that was cut off. Three reference layers are opt-in and not in the default set: submarine_cables (routes and landing points), disasters (USGS, GDACS, EONET) and displacement (UNHCR, by origin and corridor). Name them to get them.

NameTypeReqDescription
days_backstring––
layersstring––

Structured output declared, but exposes no named fields.

No examples provided.

list_capabilities ~21

What the Antevo Executive connector exposes. No account required.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_coverage ~76

What the Antevo desk writes on beyond the daily brief — shipping, aviation, yachts, energy, infrastructure, real estate, commodities, geopolitics, AI and technology, energy transition, demographics, generational wealth, succession planning, art. Each with the date of its most recent note. Pass an area to get_coverage.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_executive_notes ~91

The archive of past Executive Briefs, newest first — each with its date, title, subtitle and hero line. Use this to see what has been covered, to find the date of a story, or to follow how a theme developed over time, then call get_executive_note for the full text of a given day.

NameTypeReqDescription
limitstring––
marketstring––

Structured output declared, but exposes no named fields.

No examples provided.

search_macro_indicators ~128

Find a macro-economic series by name or country — CPI, policy and market interest rates, equity indices, house prices, industrial production, commodities. Covers 180 countries, some back to 1920. Returns each series' ticker and the span it actually covers; pass the ticker to get_macro_series. `country` takes either a name ('Switzerland') or an ISO-3 code ('CHE'). Search first: there are tens of thousands of series and they cannot be listed.

NameTypeReqDescription
countrystring––
limitstring––
querystringyes–

Structured output declared, but exposes no named fields.

No examples provided.

track_risk_evolution ~193

Every risk radar the brief published over recent weeks, in one call — each dated board with its regime and its risks, oldest first. Use this to see which risks are new, which have been carried for weeks, which dropped off, and how their trend, impact and probability moved. Read the boards in order and group the risks yourself: the brief rephrases the same risk every day, so match them by meaning, not wording. days_back 7..90, default 30. detail trades size for depth: 'counts' for grades only (chart the board), 'titles' to also group themes, 'full' (default) to also read why each risk matters — a 90-day pull is roughly a third the size at 'counts'.

NameTypeReqDescription
days_backstring––
detailstring––
marketstring––
scopestring––

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the Antevo Executive Brief MCP server?

Antevo Executive Brief is an MCP server listed in the public MCP registry as ch.antevo/executive. Market and world intelligence, the daily editorial read, risk radar and dated archive. This page covers its hosted endpoint (https://api.antevo.ch/mcp/executive/mcp).

Is the Antevo Executive Brief MCP server safe to use?

Antevo Executive Brief scores 84 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 Executive Brief MCP server expose?

Antevo Executive Brief exposes 15 tools: list_capabilities, get_executive_brief, list_executive_notes, get_executive_note, get_executive_desk, and 10 more. Their descriptions and schemas cost roughly 1,472 tokens of context every time the server is loaded.

Does the Antevo Executive Brief MCP server require authentication?

No. We connected to Antevo Executive Brief without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Antevo Executive Brief MCP server still maintained?

Antevo Executive Brief is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.