Havoptic AI Release Intelligence is answering right now. Last checked 5 min ago. It exposes 15 tools.
Release intelligence for AI coding tools: releases, typed changes, breaking changes, cadence.
The linked repository no longer exists on GitHub — it was deleted or made private.
Uptime history
13 days of history
13 days agonow
100.0%
Uptime 24h
91 of 91 checks
15
Tools
read from the server
177 ms
Response time
average over 24h
open, no key
Access
streamable-http
This one has been quiet for a while
Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.
run in your terminal
claude mcp add releases --transport http https://mcp.havoptic.com/mcpSettings → Connectors → Add custom connector, then paste this address
https://mcp.havoptic.com/mcp~/.codex/config.toml
[mcp_servers.releases]
url = "https://mcp.havoptic.com/mcp".cursor/mcp.json
{
"mcpServers": {
"releases": {
"url": "https://mcp.havoptic.com/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"releases": {
"type": "http",
"url": "https://mcp.havoptic.com/mcp"
}
}
}Available tools 15
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
release
get_release
One release by id (e.g. 'claude-code-2.1.183', canonical '[email protected]') 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.
release_history
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.
search_release_notes
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.
feature
feature_adoption
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.
feature_timeline
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.
latest
get_latest_releases
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.
latest_releases
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.
breaking
get_breaking_changes
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.
cadence
cadence_stats
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.
changes
search_changes
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.
compare
compare_tools
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.
tools
list_tools
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').
tracked
list_tracked_tools
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.
upgrade
get_upgrade_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.
whats
whats_changed_since
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.havoptic.com/mcp | streamable-http | answering | 134 ms | 5 min ago |
Alternatives to Havoptic AI Release Intelligence
same job, measured the same way
R
release-gate-mcp
by abduljabbarbxr
Release intelligence for AI agents. Detects breaking changes and recommends semver.
Overdrive Intel
by looney-tic
AI coding ecosystem intelligence — breaking changes, tools, security alerts from 900+ sources
Ratatosk MCP
by garlickim21
CNCF release intelligence: typed changes from release notes; check_stack compares versions locally.
Ratatosk MCP
by basphere
CNCF release intelligence: typed changes from release notes; check_stack compares versions locally.
Graqle
by graqle
Dev intelligence layer: 7 MCP tools for graph-powered codebase reasoning.
Constellation
by shiftinbits
Code Intelligence Platform for AI Coding Agents
Marketbasketanalysis MCP
by 48x-ai
Co-purchase intelligence and merchant ops tools for AI shopping, ecommerce, and B2B agents
Reality Graph Verification Tools
by realitygraph
Read-only AI coding tools for change verification, release readiness, capacity, and guidance.
Havoptic AI Release Intelligence — questions
Answers built from our own checks of this server.
What can Havoptic AI Release Intelligence do?
It exposes 15 tools, read directly from the server on our last check. Among them: cadence_stats, compare_tools, feature_adoption, feature_timeline, get_breaking_changes, get_latest_releases and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Havoptic AI Release Intelligence mostly used for?
Its tools cluster around release, feature and latest. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Havoptic AI Release Intelligence working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 177 ms. The bar chart above shows every period we have measured.
Is Havoptic AI Release Intelligence still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Havoptic AI Release Intelligence?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Havoptic AI Release Intelligence need an API key?
No. Havoptic AI Release Intelligence completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Havoptic AI Release Intelligence?
It answers our handshake in 177 ms on average, which is faster than 76% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.