Vela Breakout
REMOTE · BREAKOUT.VELA.PARTNERS
What's growing in tech, measured daily: AI apps, models, dev tools, software spend, hiring.
Available components
Last scanned (3 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Data and Analytics
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability38
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 607 tokens (~86/item across 7 items; 6 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 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 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 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 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 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.
- 20 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.
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://breakout.vela.partners/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=breakout.vela.partners | CN=WR3,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | RSA 2048 | SHA256-RSA | edb0854e5e48efee102a02439dabe001 |
| SANs: breakout.vela.partners | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of breakout.vela.partners. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| partners. | present | 27907 | 8 | Verified |
| vela.partners. | present | 32092 | 8 | Verified |
| breakout.vela.partners. | Verified address RRset verified with the apex keys |
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 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' data: blob: https://lh3.googleusercontent.com; connect-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self' https://accounts.google.com; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://breakout.vela.partners/mcp | Verified | 200 | |
| http (plaintext) | http://breakout.vela.partners/mcp | HTTPS enforced | 302 | https://breakout.vela.partners/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 →
ask Ask what's growing ~51
Answer any question about what is growing in tech with checked figures and links to the charts. Best first call. Shows the chart inline where the client supports it.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The question in plain words |
No output schema declared.
No examples provided.
find_breakouts Fastest growers in one group ~270
The fastest-growing items of one group over a window. Groups: ai_apps (AI apps: tokens); ai_models (AI models: tokens a week); ai_labs (AI labs: share of all AI tokens); ai_work (AI work: open jobs); open_models (Open models: downloads in 30 days); editor_extensions (Code editor extensions: installs); open_editor_extensions (Open-source editor extensions: installs); workplace_add_ons (Workplace add-ons: installs); browser_extensions (Browser extensions: installs); agent_skills (Agent skills: installs a week); agent_tools (Agent tools: downloads a week); company_packages (Company packages: downloads in 30 days); business_software (Business software: adoption score); web_technologies (Web technologies: websites); company_hiring (Companies hiring: open roles); company_buzz (In the news: points in 12 months).
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | yes | Group id from list_groups |
| limit | integer | – | – |
| min_size | string | – | Leave out tiny items (default median) |
| steady | boolean | – | Set true for 'steadily', 'starting to', 'sustained': keeps only items also up over a longer window |
| window_days | – | – | Leave out for the group's usual window |
No output schema declared.
No examples provided.
get_company One company, every signal ~50
Everything measured about one company: each signal's growth, how it compares with peers, and its page.
| Name | Type | Req | Description |
|---|---|---|---|
| name_or_domain | string | yes | Company name or web domain, e.g. supabase.com |
No output schema declared.
No examples provided.
list_groups Groups and what they measure ~25
Every group you can ask about, with its unit, caveat and usual window.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
research_ideas Research ideas gaining or losing ground ~45
AI research ideas by change in their share of all papers, last 3 months against the 3 before.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
rising_companies Companies rising on several measures ~32
Companies breaking out on two or more measures at once, ranked by how much.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
How do I install the Vela Breakout MCP server?
Vela Breakout is a hosted endpoint at https://breakout.vela.partners/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 · breakout.vela.partners
claude mcp add --transport http partners-vela-breakout-breakout 'https://breakout.vela.partners/mcp'
What is the Vela Breakout MCP server?
Vela Breakout is an MCP server listed in the public MCP registry as partners.vela.breakout/breakout. What's growing in tech, measured daily: AI apps, models, dev tools, software spend, hiring. This page covers its hosted endpoint (https://breakout.vela.partners/mcp).
Is the Vela Breakout MCP server safe to use?
Vela Breakout scores 71 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 Vela Breakout MCP server expose?
Vela Breakout exposes 6 tools: ask, find_breakouts, get_company, research_ideas, rising_companies, list_groups. Their descriptions and schemas cost roughly 473 tokens of context every time the server is loaded.
Does the Vela Breakout MCP server require authentication?
No. We connected to Vela Breakout without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Vela Breakout MCP server still maintained?
Vela Breakout 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.