Release Alert
REMOTE · RELEASEALERT.DEV
Search packages across registries, and read their releases and CVEs.
Available components
Last scanned (10 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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 Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 826 tokens (~103/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).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.
- 3 Nov 26 +1
- Tool “list_project_release_notes” rewrote its description, which is the text the model reads security
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 72 → 103 ▼ functional
- New tool “check_manifest” functional
- New tool “list_project_release_notes” functional
- 30 Oct 26 0
- “list_project_cves” added an optional parameter “page” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 29 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.
- 27 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.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
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://releasealert.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=releasealert.dev | CN=WE1,O=Google Trust Services,C=US | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | e5569cdf8492bf771354b79bcc3f766c |
| SANs: releasealert.dev, *.releasealert.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of releasealert.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| releasealert.dev. | 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=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://releasealert.dev/mcp | Verified | 200 | |
| http (plaintext) | http://releasealert.dev/mcp | HTTPS enforced | 301 | https://releasealert.dev/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 →
check_manifest ~178
Check the dependencies a manifest or lockfile names, such as a package.json, go.mod, requirements.txt, or Cargo.lock. For each one, it reports how the version asked for compares with the latest release, and the advisories that affect that version, with the versions that fix them. A range is checked at the version it names, as ^1.2.0 is at 1.2.0. Dependencies that couldn't be checked are listed under skipped, with the reason. A project new to Release Alert is added; until it has been checked, releases_checked or advisories_checked is false, and checking again in a few minutes fills in the rest.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | the file's contents |
| filename | string | yes | the file's name, such as package.json or go.mod, which tells its format |
No output schema declared.
No examples provided.
get_cve ~39
Get a CVE by its id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | the CVE id, such as CVE-2024-3094 |
No output schema declared.
No examples provided.
get_project ~59
Get a project by its registry and name.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | the project's name in that registry, from a search result's name |
| registry | string | yes | the registry id, from list_registries or a search result's registry |
No output schema declared.
No examples provided.
list_project_cves ~80
List the CVEs that affect a project, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | the project's name in that registry, from a search result's name |
| page | integer | – | the page to return, starting at 1 |
| registry | string | yes | the registry id, from list_registries or a search result's registry |
No output schema declared.
No examples provided.
list_project_release_notes ~180
List the release notes of every release of a project after one version and up to another, newest first. A release without notes is still listed, with notes null and a link to the release. Pre-releases are left out unless the last version is one.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | list the releases after this version, written as a version or as a manifest names it (4.19.2 or ^4.19.2) |
| name | string | yes | the project's name in that registry, from a search result's name |
| page | integer | – | the page to return, starting at 1 |
| registry | string | yes | the registry id, from list_registries or a search result's registry |
| to | string | – | list the releases up to and including this version; the latest stable release when empty |
No output schema declared.
No examples provided.
list_project_releases ~89
List a project's releases, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | the project's name in that registry, from a search result's name |
| page | integer | – | the page to return, starting at 1 |
| registry | string | yes | the registry id, from list_registries or a search result's registry |
| version | string | – | only releases whose version contains this |
No output schema declared.
No examples provided.
list_registries ~31
List the registries Release Alert tracks. A registry's id is what search and the project tools take.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search ~100
Search for a project by its name, optionally followed by a version, or by its URL, or for a CVE by its id. Each project found carries the registry and name the project tools take.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | a project name, optionally followed by a version (redis 7.2), a CVE id, or a project's URL |
| registry | string | – | limit the search to this registry id, from list_registries |
No output schema declared.
No examples provided.
How do I install the Release Alert MCP server?
Release Alert is a hosted endpoint at https://releasealert.dev/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 · releasealert.dev
claude mcp add --transport http dev-releasealert-mcp 'https://releasealert.dev/mcp'
What is the Release Alert MCP server?
Release Alert is an MCP server listed in the public MCP registry as dev.releasealert/mcp. Search packages across registries, and read their releases and CVEs. This page covers its hosted endpoint (https://releasealert.dev/mcp).
Is the Release Alert MCP server safe to use?
Release Alert scores 79 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 Release Alert MCP server expose?
Release Alert exposes 8 tools: check_manifest, get_cve, get_project, list_project_cves, list_project_release_notes, and 3 more. Their descriptions and schemas cost roughly 756 tokens of context every time the server is loaded.
Does the Release Alert MCP server require authentication?
No. We connected to Release Alert without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Release Alert MCP server still maintained?
Release Alert 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.