mcpbeat Sign in

Release Notes Index MCP Server

answering

Release Notes Index is answering right now. Last checked 15 min ago. It exposes 18 tools. Last commit 6 Nov 2026.

Release notes and changelogs from across the web, indexed for agents. Also via CLI and REST API.

Uptime history 91 days of history · worst day 93%
91 days agonow
100.0%
Uptime 24h
182 of 182 checks
18
Tools
read from the server
310 ms
Response time
average over 24h
14
Stars
last commit 6 Nov 2026

What changed 11

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 11 September 2026. No other catalogue keeps this.

24 Oct a tool changed the parameters it asks for manage_webhook
16 Oct 3 tool descriptions were rewritten get_personalized_feed, get_release, whats_changed
5 Oct 2 tools changed the parameters they ask for get_latest_releases, search
3 Oct a tool changed version2 times that day
23 Sep 2 tools appeared list_webhooks, manage_webhook
11 Sep a tool changed version
and 1 more, back to 11 September 2026

What the code does

We read the source, 2 h ago · tools taken from the live server · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

            Turbopack is now stable for both dev and build. Compile times drop up to 72% on large
  const result = spawnSync(finder, [cmd], {
Builds a file path from a variable apps/web/src/lib/docs.ts:78
  const filePath = path.join(CONTENT_ROOT, dir, `${slug}.md`);
  "AAEAAAASAQAABAAgR0RFRmviZHgAAYZwAAABSEdQT1OHH3IHAAGHuAAAT2xHU1VCe5lenQAB1yQAABSwT1MvMjyEb9oAAAGoAAAAYGNtYXA+eTXjAAARPAAACHhjdnQgIKgTSAAAKJgAAACkZnBnbWIvA38AABm0AAAODGdhc3AAAAAQAAGGaAAAAAhnbHlmS12R2gAAMNgAASs4aGVhZDL0b20AAAEsAAAANmhoZWEMSg0yAAABZAAAACRobXR4QyS4wQAAAggAAA80bG9jY…

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.releases.sh/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.releases.sh/mcp
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.releases.sh/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.releases.sh/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.releases.sh/mcp"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 18

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

catalog
get_catalog_entry
Detail for a single catalog entry — accepts a prod_ id, src_ id, or an org-scoped coordinate in the form orgSlug/slug (e.g. 'vercel/nextjs' or 'vercel/next-js'). Returns the union of product / source detail fields depending on the entry kind. Source entries list tracked CHANGELOG files by path and byte size. Pass `include_changelog: true` to inline the root CHANGELOG, or `changelog_path` / `changelog_offset` / `changelog_limit` / `changelog_tokens` to embed a specific file or slice — heading-aligned, supports per-package files in monorepos (e.g. `packages/next/CHANGELOG.md`), and emits `totalTokens` / `sliceTokens` for LLM context budgeting. Files over 1MB are flagged as truncated so you know the tail is missing.
list_catalog
List catalog entries — products and standalone sources combined into one list with an `entryType: 'product' | 'source'` discriminator per row. Orgs that group multiple sources under a product (e.g. Vercel → Next.js, Turborepo) surface those products; orgs with a single source that isn't part of a product surface it directly as an `entryType: 'source'` entry. Either shape is a reasonable thing to pass to `search(entity: ...)`. Paginated: defaults to 50 entries per page. Pass `page: 2` for the next slice. The footer surfaces the total when more pages exist.
collection
get_collection
Detail for a single collection — name, description, and the ordered list of member organizations. Hidden / on-demand orgs never leak through; only publicly visible orgs appear in the member list.
get_collection_releases
Interleaved cross-org release feed for a collection — same shape as `get_latest_releases` but scoped to the collection's member orgs. Cursor-paginated: pass `limit` for slice size (default 20), `cursor` to continue from a prior call. The result's `_meta.pagination` carries `kind: 'cursor'`, `hasMore`, and `nextCursor` when more rows exist; the response text echoes `nextCursor` so an LLM caller can chain without parsing `_meta`. Cursors are stable under inserts.
collections
list_collections
List curated collections — named cross-org playlists (e.g. 'Frontier AI Labs') independent of the fixed category taxonomy. Use `get_collection` for a collection's full member list, or `get_collection_releases` for the interleaved cross-org release feed. Paginated: defaults to 50 entries per page; pass `page: 2` for the next slice.
follow
follow
Follow an organization or a product so it appears in your personalized feed (`get_personalized_feed`). Following an organization implicitly includes all of its products. Requires a signed-in user (a `relu_` user key or an OAuth token). `entity` is a typed id — an `org_…` id or a `prod_…` id — as returned by `search`, `get_organization`, or `get_catalog_entry`. Idempotent: following something you already follow is a no-op.
follows
list_follows
List the organizations and products you follow (newest first). Requires a signed-in user.
latest
get_latest_releases
Get the most recent releases, optionally filtered by product or organization. Excludes prereleases (canaries / alphas / betas / RCs) by default — pass `include_prereleases: true` to include them. Cursor-paginated: pass `limit` for slice size (default 10), `cursor` to continue from a prior call. The result's `_meta.pagination` carries `kind: 'cursor'`, `hasMore`, and `nextCursor` when more rows exist; the response text echoes `nextCursor` so an LLM caller can chain without parsing `_meta`. Cursors are stable under inserts — a release added between calls won't shift the slice.
lookup
lookup_domain
Resolve a domain to the org or product that owns it. The domain is normalized first (scheme, `www.`, path, and trailing slash stripped, lowercased), so `https://vercel.com/about` and `vercel.com` both look up the same row. Returns the matching org (with primary-vs-alias distinction) and any products whose alias targets the same domain. Pure resolution — does not probe the domain or materialize anything; unknown domains surface a 'no match' message. Use `lookup_domain` when you have a URL-shaped input; use `get_organization` when you already have a slug or id.
manage
manage_webhook
Create, update, delete, test, or rotate the signing key of an outbound release webhook — personal or workspace. Requires a signed-in user. This tool sends requests to an external URL you supply and can delete or disable delivery, so treat it as a write. Pass `workspace` (an id or slug) to act on a workspace's webhooks instead of your personal ones; workspace webhooks are always org-scoped (`scope: "follows"` is personal-only and is rejected up front). Only workspace owners and admins can create, update, delete, or rotate a workspace webhook — any member can test one. `action: "create"` needs `url` and `format` (`json`, `slack`, or `discord`), plus either `scope: "follows"` (personal only — everything you follow) or an org-scoped target: `org` (an org slug or `org_…` id), optionally narrowed by `product` (slug or `prod_…` id) or `source` (slug or `src_…` id). `action: "update"` needs `id` plus any fields to change; pass `source: null` or `product: null` to clear a filter. `action: "delete"`, `action: "test"`, and `action: "rotate_secret"` need only `id`. `create` and `rotate_secret` return a one-time `signingKey` for `json`-format webhooks — store it now, it will not be shown again. `slack` and `discord` deliveries aren't signed, so those formats never return one.
organization
get_organization
Get detailed information about a single organization — accounts, tags, sources, products, aliases. When an AI-generated overview exists the response includes a short preview; pass `include_overview: true` to inline the full briefing (with a stale warning if the content is older than 30 days since last write).
organizations
list_organizations
List all indexed organizations, optionally filtered. Paginated: defaults to 50 entries per page; pass `page: 2` for the next slice. Orgs with zero indexed releases are hidden by default (curator-stub noise); set `include_empty: true` to see them.
personalized
get_personalized_feed
Your personalized release feed — recent releases from the organizations and products you follow, newest first. Requires a signed-in user. Same item shape as `get_latest_releases`, scoped to your follows. Each item prints `URL:` (the original source — cite that) before `Web:` (the releases.sh copy), when present. Cursor-paginated: pass `cursor` from a prior response's `_meta.pagination.nextCursor` and optional `limit` (1–100, default 30).
release
get_release
Fetch the full content of a single release by id. Release ids are returned by search or get_latest_releases — pass them here to read the whole entry (e.g. to quote a specific Next.js release note). Accepts the full rel_<nanoid> form or the bare 21-char nanoid. Cite `URL:` (the original source) ahead of `Web:` (the releases.sh copy). Structured `url` and `webUrl` carry the same pair.
search
search
Unified search across the registry and release content. Returns up to four sections — organizations, catalog entries (products + standalone sources folded into one list), curated collections (cross-org playlists), and releases with CHANGELOG chunks interleaved by relevance. Use `type` to narrow the surfaces you want and skip the expensive paths. For example, pass `type: ['catalog']` to look up a known entity by name (fast, registry-only); pass `type: ['releases']` when you only care about release content and want to avoid entity lookups. Omit `type` to search all four. Collections surface via two paths: a direct match on the collection's name/description (lexical in every mode, plus a vector match in hybrid/semantic mode) and a member rollup that includes every collection containing one of the matched orgs. Member rollups carry a list of result-set org slugs that triggered the rollup so a UI can render an "includes X" hint. Use `entity` (product slug / prod_ id OR source slug / src_ id) to scope release results to one catalog entry. Product identifiers expand to every source under the product. Use `organization` to scope to a whole org. Release retrieval defaults to hybrid (FTS5 + semantic vectors fused via RRF); it silently degrades to lexical when vector infra is unavailable and flags the result.
unfollow
unfollow
Stop following an organization or product. Requires a signed-in user. `entity` is an `org_…` or `prod_…` id. Idempotent: unfollowing something you don't follow is a no-op.
webhooks
list_webhooks
List your outbound release webhooks, personal or workspace. Requires a signed-in user (a `relu_` user key or an OAuth token). With no `workspace`, lists your personal webhooks (`GET /v1/me/webhooks`) and includes a short list of your workspaces (id, slug, role) so you can target one next. Pass `workspace` (an id or a slug) to list that workspace's webhooks instead. Pass `id` to see one webhook plus its 10 most recent deliveries. Pass `enabled` to filter by enabled/disabled state.
whats
whats_changed
Given a package and a `from`/`to` version, return the changelog entries between them — `(from, to]`, from exclusive, to inclusive — with summaries and breaking-change verdicts. One call instead of reading N changelog pages to plan an upgrade. `package` is a tracked source slug or a GitHub `owner/repo` coordinate (set `ecosystem: "github"` for a bare coordinate). Reads already-indexed releases only. If the package isn't in the catalog you'll get a clear 'not tracked' answer (npm/PyPI names may not be mapped to a source yet). Each entry prints `URL:` (the original source — cite that) before `Web:` (the releases.sh copy), when present. Structured results still include both `url` and `webUrl`.

Endpoints

URLTransportStateLatencyChecked
https://mcp.releases.sh/mcp streamable-http answering 305 ms 15 min ago
https://agents.releases.sh/mcp streamable-http answering 384 ms 15 min ago

Alternatives to Release Notes Index

same job, measured the same way
AgentWeb (agentweb.us)
by agentweb

The action index for the web: real sites as callable, verified actions for AI agents.

answering
CatchAll
by newscatcherapi

Web search API: find every relevant event across the open web, not just the top results.

61 tools answering
Recoup: AI agents for the music industry
by recoupable

Music industry tools for AI agents: artist research, catalogs, release plans and content.

answering
Web Search
by groundroute

Web search for AI agents — one tool across 6 engines, routed to the cheapest + cached.

answering
HaloPSA
by wyre-ai

MCP server for HaloPSA — clients, tickets, and PSA workflows via the HaloPSA REST API.

local only
HaloPSA
by wyre-technology

MCP server for HaloPSA — clients, tickets, and PSA workflows via the HaloPSA REST API.

local only
Valorant MCP
by mrfentmen

Agents, maps, and weapons from the Valorant community API. No key required.

62 installs/wk local only
Kanye MCP
by mrfentmen

Kanye West quotes from the Kanye Rest API. No key required.

63 installs/wk local only

Release Notes Index — questions

Answers built from our own checks of this server.

What can Release Notes Index do?
It exposes 18 tools, read directly from the server on our last check. Among them: follow, get_catalog_entry, get_collection, get_collection_releases, get_latest_releases, get_organization and 12 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 Release Notes Index mostly used for?
Its tools cluster around catalog and collection. 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 Release Notes Index working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 182 of 182 checks got a reply (100.0%), average response time 310 ms. The bar chart above shows every period we have measured.
How do I connect Release Notes Index?
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 Release Notes Index need an API key?
No. Release Notes Index completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 18 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Release Notes Index?
It answers our handshake in 310 ms on average, which is faster than 45% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Release Notes Index open source?
The code is open source: it is published under the Apache-2.0 licence, written in TypeScript, 14 stars on GitHub and 197 open issues. The licence covers the code in the repository, not the hosted service at mcp.releases.sh, which runs on its operator's own terms.