Release Alert MCP server
dev.releasealert/mcpreleasealert.devstreamable-httpv1.1.0Scanned
Connect AI assistants to Release Alert.
12 tools: 1 can delete or cancel things, 2 change things and 9 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Release Alert MCP server can do
The Release Alert MCP server is published by releasealert.dev, a domain the MCP Registry verified. It has 12 tools. It can delete or cancel things (1 tool: unfollow_project) and create or change data (2 tools: follow_project and scan_dependencies). 9 tools only read.
1 tool reads private data (list_project_release_notes); 1 tool brings in text other people can write (search).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 12, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
12 tools
Deletes or cancels 1Claude Code: deny
unfollow_projectUnfollow a project for the signed-in account, which stops its alerts and drops its alert settings.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Unfollow a project for the signed-in account, which stops its alerts and drops its alert settings.
Annotations the server declares
- destructiveHint: true
- idempotentHint: true
- readOnlyHint: false
Changes things 2Claude Code: ask
follow_projectFollow a project for the signed-in account, so it sends the alerts asked for through the account's alert integrations.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Follow a project for the signed-in account, so it sends the alerts asked for through the account's alert integrations. A project the account already follows keeps the alerts it has.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- readOnlyHint: false
scan_dependenciesScan the dependencies a manifest or lockfile names, such as a package.json, go.mod, requirements.txt, or Cargo.lock.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Scan 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.
Annotations the server declares
- idempotentHint: false
- readOnlyHint: true
Only reads 9Show 9 read-only tools
get_cveGet a CVE by its id.No findings
Why it is in this group
- The name "get_cve" says "get": a word for reading.
Description, as the server wrote it Get a CVE by its id.
Annotations the server declares
- idempotentHint: false
- readOnlyHint: true
get_projectGet a project by its registry and name.No findings
Why it is in this group
- The name "get_project" says "get": a word for reading.
Description, as the server wrote it Get a project by its registry and name.
Annotations the server declares
- idempotentHint: false
- readOnlyHint: true
list_followed_project_cvesList the CVEs that affect the projects the signed-in account follows, newest first.No findings
Why it is in this group
- The name "list_followed_project_cves" says "list": a word for reading.
Description, as the server wrote it List the CVEs that affect the projects the signed-in account follows, newest first. The second part of the answer maps each CVE's id to the followed projects it affects, with the versions affected and fixed.
Annotations the server declares
- idempotentHint: false
- readOnlyHint: true
list_followed_projectsList the projects the signed-in account follows, with the alerts each one sends.No findings
Why it is in this group
- The name "list_followed_projects" says "list": a word for reading.
Description, as the server wrote it List the projects the signed-in account follows, with the alerts each one sends.
Annotations the server declares
- idempotentHint: false
- readOnlyHint: true
list_project_cvesList the CVEs that affect a project, newest first.No findings
Why it is in this group
- The name "list_project_cves" says "list": a word for reading.
Description, as the server wrote it List the CVEs that affect a project, newest first.
Annotations the server declares
- idempotentHint: false
- readOnlyHint: true
list_project_release_notesList the release notes of every release of a project after one version and up to another, newest first.Reads private dataNo findings
Why it is in this group
- The name "list_project_release_notes" says "list": a word for reading.
What it can reach
- private-dataThe name "list_project_release_notes" says "list" and "note": it reads notes.
- private-dataThe description's first sentence says "list" and "note": it reads notes.
Description, as the server wrote it 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.
Annotations the server declares
- idempotentHint: false
- readOnlyHint: true
list_project_releasesList a project's releases, newest first.No findings
Why it is in this group
- The name "list_project_releases" says "list": a word for reading.
Description, as the server wrote it List a project's releases, newest first.
Annotations the server declares
- idempotentHint: false
- readOnlyHint: true
list_registriesList the registries Release Alert tracks.No findings
Why it is in this group
- The name "list_registries" says "list": a word for reading.
Description, as the server wrote it List the registries Release Alert tracks. A registry's id is what search and the project tools take.
Annotations the server declares
- idempotentHint: false
- readOnlyHint: true
searchSearch for a project by its name, optionally followed by a version, or by its URL, or for a CVE by its id.Reads text others writeNo findings
Why it is in this group
- The name "search" says "search": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "search" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- idempotentHint: false
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 21, 2026, 19:24 UTC, unchanged since Nov 14, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://releasealert.dev/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://releasealert.dev
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- no
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://releasealert.dev/mcp: tools/list returned 13 tools to an anonymous client, including unfollow_project (destructive), follow_project (write), scan_dependencies (write)
Posture changes
- Nov 14, 2026
- Tools that change things, listed without credentials: 1 to 3
- RFC 9728 protected resource metadata: none to https://releasealert.dev/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://releasealert.dev
- Dynamic client registration: not observed to no
- Client ID metadata documents: not observed to yes
- Oct 30, 2026
- Tools that change things, listed without credentials: 0 to 1
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 3; RFC 9728 protected resource metadata: none -> https://releasealert.dev/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://re…View diff
- Tools that change things, listed without credentials: 1 to 3
- RFC 9728 protected resource metadata: none to https://releasealert.dev/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://releasealert.dev
- Dynamic client registration: not observed to no
- Client ID metadata documents: not observed to yes
Tools5 added, 1 removed, 7 changed.+5 added−1 removed~7 changedView diff
- Added:follow_projectChanges things
- Added:list_followed_project_cvesOnly reads
- Added:list_followed_projectsOnly reads
- Added:scan_dependenciesChanges things
- Added:unfollow_projectDeletes or cancels
- Removed:check_manifest
- Changed:get_cveOnly readstitle
- Changed:get_projectOnly readstitle
- Changed:list_project_cvesOnly readstitle
- Changed:list_project_release_notesOnly readstitle
- Changed:list_project_releasesOnly readstitle
- Changed:list_registriesOnly readstitle
- Changed:searchOnly readstitle
Tools2 added, 1 changed.+2 added~1 changedView diff
- Added:check_manifestChanges things
- Added:list_project_release_notesOnly reads
- Changed:list_project_cvesOnly readsinputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 1.View diff
- Tools that change things, listed without credentials: 0 to 1
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http releasealert https://releasealert.dev/mcpclaude mcp add --transport http releasealert https://releasealert.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__releasealert__get_cve",
"mcp__releasealert__get_project",
"mcp__releasealert__list_followed_project_cves",
"mcp__releasealert__list_followed_projects",
"mcp__releasealert__list_project_cves",
"mcp__releasealert__list_project_release_notes",
"mcp__releasealert__list_project_releases",
"mcp__releasealert__list_registries",
"mcp__releasealert__search"
],
"ask": [
"mcp__releasealert__follow_project",
"mcp__releasealert__scan_dependencies"
],
"deny": [
"mcp__releasealert__unfollow_project"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as releasealert. Review it before you use it.
Capability tags behind 2 rules
- mcp__releasealert__list_project_release_notes private-data
- mcp__releasealert__search untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.releasealert/mcp/verify?hash=0d95bfab1115e08ae91e9a5ae5d94eac5ca69f0c2f2771655ff5c5e2047f6e68" | jq -e '.changed == false'Pinned hash 0d95bfab1115, from Nov 12, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.releasealert/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.releasealert/mcp)Source: MCP Registry. Synced Nov 12, 2026, 22:17 UTC.
Release Alert MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Release Alert MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Release Alert MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: unfollow_project.
Can the Release Alert MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Release Alert MCP server have?
- 12 tools: 1 destructive, 2 write, 9 read. unfollow_project, follow_project, scan_dependencies, get_cve, get_project, list_followed_project_cves, list_followed_projects, list_project_cves and 4 more.
Does the Release Alert MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Release Alert MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Release Alert MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.