The 07:00 Brief
REMOTE · API.ANTEVO.CH
Your agent knows the markets by 07:00, every day. We read them so you don't have to.
Available components
Last scanned (3 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 586 tokens (~146/item across 4 items; 4 tools + 0 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 Management63
- Stability observed for 19 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 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.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://api.antevo.ch/mcp/0700/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/0700/mcp | Verified | 200 | |
| http (plaintext) | http://api.antevo.ch/mcp/0700/mcp | HTTPS enforced | 301 | https://api.antevo.ch/mcp/0700/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 →
get_morning_brief Get morning brief ~103
The 07:00 Brief for one day: title, subtitle, hero line, market regime, what matters and why, the take, the signal being watched, upcoming catalysts, risks and what to watch, with that morning's Market Map, Big Picture and Three Minute Brief notes when they were published. Without a date it is the latest brief; with date (YYYY-MM-DD) it is the brief published that day.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_risk_radar Get risk radar ~121
The Risk Radar from The 07:00 Brief: the ranked risks being watched, each with its theme, trend, impact, probability, summary, the indicator to watch, what it would mean for portfolios, when it was first seen and on how many mornings it has appeared. The latest radar also gives when tracking began, how many mornings have been read and how many risks have been tracked. Without a date it is the latest radar; with date (YYYY-MM-DD) it is the radar published that day.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_sector_notes Get sector notes ~134
Sector notes from The 07:00 Brief, each with its sector, title, text and date. Five sectors: markets-commodities (Markets & Commodities), themes-ai-technology (AI & Technology), themes-energy-transition (Energy Transition), real-assets-energy (Energy) and geopolitics-core (Geopolitics). sectors narrows the set (all five by default); names outside the five are listed as unavailable. Without a date, the latest note in each sector; with date (YYYY-MM-DD), the notes published that day.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | – |
| sectors | array | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_recent_briefs List recent briefs ~61
Recent editions of The 07:00 Brief, newest first: the date, title and hero line of each brief published in the last `days` days, today included (1 to 30, default 7).
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the The 07:00 Brief MCP server?
The 07:00 Brief is a hosted endpoint at https://api.antevo.ch/mcp/0700/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-0700-brief 'https://api.antevo.ch/mcp/0700/mcp'
What is the The 07:00 Brief MCP server?
The 07:00 Brief is an MCP server listed in the public MCP registry as ch.antevo/0700-brief. Your agent knows the markets by 07:00, every day. We read them so you don't have to. This page covers its hosted endpoint (https://api.antevo.ch/mcp/0700/mcp).
Is the The 07:00 Brief MCP server safe to use?
The 07:00 Brief scores 78 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 The 07:00 Brief MCP server expose?
The 07:00 Brief exposes 4 tools: get_morning_brief, list_recent_briefs, get_risk_radar, get_sector_notes. Their descriptions and schemas cost roughly 419 tokens of context every time the server is loaded.
Does the The 07:00 Brief MCP server require authentication?
No. We connected to The 07:00 Brief without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the The 07:00 Brief MCP server still maintained?
The 07:00 Brief is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.