Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Havoptic AI Release Intelligence is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Release intelligence for AI coding tools: releases, typed changes, breaking changes, cadence.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http havoptic-ai-release-intelligence-mcp https://mcp.havoptic.com/mcp
# 2 — ask your agent for something these tools do
# list_tracked_tools, latest_releases, release_history and 12 more
Havoptic AI Release Intelligence costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http havoptic-ai-release-intelligence-mcp https://mcp.havoptic.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Deprecated: use list_tools. All AI coding tools Havoptic tracks (Claude Code, OpenAI Codex CLI, Cursor, Gemini CLI, Kiro CLI, GitHub Copilot CLI, Devin Desktop/Windsurf, Antigravity CLI, Grok Build), with release counts and their latest release.
No parameter schema on file.
Deprecated: use get_latest_releases. Most recent AI coding tool releases (newest first), optionally filtered to one tool. Returns summaries; use get_release for full notes. Default detail=brief omits infographic URLs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tool | string | no | Tool id, e.g. 'claude-code', 'openai-codex', 'cursor', 'gemini-cli', 'kiro', 'github-copilot', 'windsurf', 'antigravity-cli', 'grok-build', 'cline', 'opencode', 'zed', 'factory-droid', 'devin', 'lovab |
| limit | integer | no | Max releases to return (default 10) |
| detail | string | no | brief omits infographics and fullNotes; full includes complete notes on single-release reads. |
Deprecated: use get_latest_releases with since. Release history for one tool within an optional date window (newest first). Summaries only; use get_release for full notes. Default detail=brief omits infographic URLs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tool | string | yes | Tool id, e.g. 'claude-code', 'openai-codex', 'cursor', 'gemini-cli', 'kiro', 'github-copilot', 'windsurf', 'antigravity-cli', 'grok-build', 'cline', 'opencode', 'zed', 'factory-droid', 'devin', 'lovab |
| since | string | no | Only releases on/after this ISO date (e.g. '2026-01-01') |
| until | string | no | Only releases on/before this ISO date |
| limit | integer | no | Max releases to return (default 50) |
| detail | string | no | brief omits infographics and fullNotes; full includes complete notes on single-release reads. |
Deprecated: use search_changes. Full-text search across all tracked release notes — flags, error strings, feature names, config keys. Returns ranked matches with snippet context.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search terms, e.g. '--dangerously-skip-permissions' or 'MCP OAuth' |
| tool | string | no | Tool id, e.g. 'claude-code', 'openai-codex', 'cursor', 'gemini-cli', 'kiro', 'github-copilot', 'windsurf', 'antigravity-cli', 'grok-build', 'cline', 'opencode', 'zed', 'factory-droid', 'devin', 'lovab |
| limit | integer | no | Max results (default 10) |
Deprecated: use feature_adoption. Which tool shipped each notable cross-tool feature first (MCP support, subagents, planning mode, hooks, checkpoints, ...), follower lag in days, and copying-trend insights. Optionally filter to one feature.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feature | string | no | Feature id or name substring, e.g. 'subagents', 'mcp', 'planning' |
Catalog of the products Havoptic tracks (AI coding tools plus model/API platforms, agent SDKs and inference runtimes): id, name, vendor, category, release count and latest release. Use first to find valid tool ids (fuzzy query: 'copilot', 'devin').
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | — |
| vendor | string | no | Vendor id slug, e.g. 'anthropic', 'google' |
| query | string | no | Fuzzy match on name/alias |
Newest releases (newest first) across all or selected tools. Successor to latest_releases and release_history (pass since/until for a date window). Default channel=stable, detail=brief.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tools | array | no | Tool ids (fuzzy: 'claude', 'codex', 'copilot' resolve). Omit for all tools; see list_tools. |
| limit | integer | no | Max releases (default 10) |
| channel | string | no | Default stable |
| detail | string | no | brief (default) omits infographics and raw notes; standard adds evidence and links; full adds complete release notes. |
| max_tokens | integer | no | Soft cap on the text response, estimated as ceil(chars/3.5). Default 1500. |
| since | string | no | Only releases on/after this ISO date |
| until | string | no | Only releases on/before this ISO date |
| cursor | string | no | next_cursor from a previous truncated response. |
Digest of typed changes (breaking, security, features, fixes, …) since a date or relative window ('7d', '30d'), grouped by tool with breaking changes first. States how many releases in range are legacy records without typed changes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | string | yes | ISO-8601 date/datetime or relative: 7d, 30d |
| tools | array | no | Tool ids (fuzzy: 'claude', 'codex', 'copilot' resolve). Omit for all tools; see list_tools. |
| kinds | array | no | Change kinds to include, e.g. ['breaking','security']. |
| detail | string | no | brief (default) omits infographics and raw notes; standard adds evidence and links; full adds complete release notes. |
| max_tokens | integer | no | Soft cap on the text response, estimated as ceil(chars/3.5). Default 1500. |
| cursor | string | no | next_cursor from a previous truncated response. |
Search typed change items (title + evidence) and, unless kinds is set, legacy release notes — flags, error strings, feature names, config keys. Successor to search_release_notes. Brief mode returns snippets only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search terms, e.g. 'MCP OAuth' or '--dangerously-skip-permissions' |
| tools | array | no | Tool ids (fuzzy: 'claude', 'codex', 'copilot' resolve). Omit for all tools; see list_tools. |
| kinds | array | no | Change kinds to include, e.g. ['breaking','security']. |
| since | string | no | — |
| until | string | no | — |
| limit | integer | no | Max results per section (default 10) |
One release by id (e.g. 'claude-code-2.1.183', canonical 'claude-code@2.1.183') or by tool + version ('latest' allowed). detail=full (the default for a bare id lookup, as before) includes complete release notes; brief/standard omit them unless include_raw_notes is true.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | no | Canonical (tool@version) or legacy (tool-version) release id |
| tool | string | no | Tool id (fuzzy), used with version |
| version | string | no | Semver or 'latest' |
| include_raw_notes | boolean | no | Include the full upstream notes in any detail mode |
| detail | string | no | brief (default) omits infographics and raw notes; standard adds evidence and links; full adds complete release notes. |
Everything between two versions of one tool: breaking changes, deprecations, security fixes, features and fixes, plus an explicit coverage gap for legacy releases without typed changes. to_version defaults to latest.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tool | string | yes | Tool id (fuzzy) |
| from_version | string | yes | Version you are on (exclusive) |
| to_version | string | no | Target version (inclusive), default 'latest' |
| detail | string | no | brief (default) omits infographics and raw notes; standard adds evidence and links; full adds complete release notes. |
Breaking changes (and, by default, deprecations) across tools in a window (default last 30 days), newest first. Legacy releases without typed changes are counted, not guessed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tools | array | no | Tool ids (fuzzy: 'claude', 'codex', 'copilot' resolve). Omit for all tools; see list_tools. |
| since | string | no | ISO date or relative window, default 30d |
| include_deprecations | boolean | no | Default true |
Compare 2–4 AI coding tools: release cadence, feature-matrix differences, recent changes, and Havoptic's editorial verdict per pair. aspects defaults to cadence, features, verdict. Legacy inputs tool_a/tool_b still work.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tools | array | no | 2–4 tool ids (fuzzy) |
| since | string | no | Window for recent_changes (ISO date or 7d/30d; default 30d) |
| aspects | array | no | Default ['cadence','features','verdict'] |
| tool_a | string | no | Legacy: first tool (use tools instead) |
| tool_b | string | no | Legacy: second tool (use tools instead) |
Who shipped a cross-tool feature first (MCP support, subagents, planning mode, hooks, checkpoints, …), which tools followed and their lag in days. Successor to feature_timeline.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feature | string | yes | Feature id or substring, e.g. mcp-oauth, subagents, planning |
How fast tools ship: release counts over 7/30/90 days, average days between releases, and last release — for selected tools or all of them. Legacy input tool (single id) still works.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tools | array | no | Tool ids (fuzzy: 'claude', 'codex', 'copilot' resolve). Omit for all tools; see list_tools. |
| tool | string | no | Legacy: one tool id (use tools instead) |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Havoptic AI Release Intelligence or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_tracked_tools | no tags | |
| latest_releases | no tags | |
| release_history | no tags | |
| search_release_notes | no tags | |
| feature_timeline | no tags | |
| list_tools | no tags | |
| get_latest_releases | no tags | |
| whats_changed_since | no tags | |
| search_changes | no tags | |
| get_release | no tags | |
| get_upgrade_notes | no tags | |
| get_breaking_changes | no tags | |
| compare_tools | no tags | |
| feature_adoption | no tags | |
| cadence_stats | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 2.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Havoptic AI Release Intelligence can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.