Release Radar MCP by usefulapi
io.usefulapi/release-radarusefulapi.iostreamable-httpv1.42.4Scanned
Correlate GitHub releases with Sentry issues and PagerDuty incidents.
5 tools: 4 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 2 findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
4 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Release Radar MCP by usefulapi can do
The Release Radar MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 5 tools. It can create or change data (4 tools: release_radar_whats_broken_since_last_deploy, release_radar_oncall_handoff, release_radar_github_latest_deploy and release_radar_sentry_recent_issues), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Oct 25, 2026, version 1.42.4.
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.
5 tools
Changes things 4Claude Code: ask
release_radar_github_latest_deployLow-level building block: the latest GitHub deployment for a repo (falls back to the latest release), returning sha + timestamp.1 finding
Why it is in this group
- The name "release_radar_github_latest_deploy" says "deploy": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "release_radar_github_latest_deploy" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "release_radar_github_latest_deploy" says "deploy": a word for a change.
Description, as the server wrote it Low-level building block: the latest GitHub deployment for a repo (falls back to the latest release), returning sha + timestamp. Used internally by release_radar_whats_broken_since_last_deploy. GitHub: GET /repos/{owner}/{repo}/deployments.
Annotations the server declares
- readOnlyHint: true
release_radar_oncall_handoffCOMPOSITE.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 COMPOSITE. A start-of-shift briefing for whoever is currently on call, fusing all three services: (a) PagerDuty current on-call + any active (triggered/acknowledged) incidents they're inheriting, (b) the GitHub deployment/release that most recently shipped (what's live), and (c) Sentry's top unresolved errors. Correlates them into one object — including a heads-up when a fresh deploy coincides with active incidents (a likely culprit). Degrades gracefully: every service is optional; whatever's unconfigured or failing is named in `notes` and the briefing still returns. Never crashes.
Annotations the server declares
- readOnlyHint: true
release_radar_sentry_recent_issuesLow-level building block: unresolved Sentry issues over a relative window.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 Low-level building block: unresolved Sentry issues over a relative window. Sentry: GET /api/0/projects/{org}/{project}/issues/?query=is:unresolved.
Annotations the server declares
- readOnlyHint: true
release_radar_whats_broken_since_last_deployCOMPOSITE.1 finding
Why it is in this group
- The name "release_radar_whats_broken_since_last_deploy" says "deploy": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "release_radar_whats_broken_since_last_deploy" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "release_radar_whats_broken_since_last_deploy" says "deploy": a word for a change.
Description, as the server wrote it COMPOSITE. Finds the latest GitHub deployment/release for a repo, then queries Sentry for unresolved issues SINCE that deploy's timestamp (the deploy time drives the Sentry window), then looks up who's currently on-call in PagerDuty — and synthesizes one situational-awareness object. Degrades gracefully: if Sentry or PagerDuty creds are absent it returns what it can plus a note. GitHub is required (it's the anchor).
Annotations the server declares
- readOnlyHint: true
Only reads 1Show 1 read-only tool
release_radar_incident_snapshotCOMPOSITE.No findings
Why it is in this group
- The name "release_radar_incident_snapshot" says "snapshot": a word for reading.
Description, as the server wrote it COMPOSITE. A right-now on-call picture: top unresolved Sentry issues + active (triggered/acknowledged) PagerDuty incidents + who's currently on-call, fused into one snapshot with a human summary. Each service degrades independently if its creds are missing.
Annotations the server declares
- 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 private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 4 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://release-radar.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://release-radar.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
The server marks "release_radar_whats_broken_since_last_deploy" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "release_radar_whats_broken_since_last_deploy" says "deploy": a word for a change.
The server marks "release_radar_github_latest_deploy" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "release_radar_github_latest_deploy" says "deploy": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 4 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://release-radar.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://release-radar.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Tools5 changed.~5 changedView diff
- Changed:release_radar_github_latest_deployChanges thingsannotations
- Changed:release_radar_incident_snapshotOnly readsannotations
- Changed:release_radar_oncall_handoffChanges thingsannotations
- Changed:release_radar_sentry_recent_issuesChanges thingsannotations
- Changed:release_radar_whats_broken_since_last_deployChanges thingsannotations
Tools5 added, 5 removed.+5 added−5 removedView diff
- Added:release_radar_github_latest_deployChanges things
- Added:release_radar_incident_snapshotOnly reads
- Added:release_radar_oncall_handoffChanges things
- Added:release_radar_sentry_recent_issuesChanges things
- Added:release_radar_whats_broken_since_last_deployChanges things
- Removed:github_latest_deploy
- Removed:incident_snapshot
- Removed:oncall_handoff
- Removed:sentry_recent_issues
- Removed:whats_broken_since_last_deploy
Install
Pinned to version 1.42.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http release-radar https://release-radar.usefulapi.io/mcpclaude mcp add --transport http release-radar https://release-radar.usefulapi.io/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__release-radar__release_radar_incident_snapshot"
],
"ask": [
"mcp__release-radar__release_radar_whats_broken_since_last_deploy",
"mcp__release-radar__release_radar_oncall_handoff",
"mcp__release-radar__release_radar_github_latest_deploy",
"mcp__release-radar__release_radar_sentry_recent_issues"
],
"deny": []
}
}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 release-radar. Review it before you use it.
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/io.usefulapi/release-radar/verify?hash=5edfa390ff05fa9769eaf86ae4248388b4c0795e7469e643d6369c5778c63a3b" | jq -e '.changed == false'Pinned hash 5edfa390ff05, from Oct 25, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/release-radar/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/release-radar)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.
Release Radar MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Release Radar MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 5 tools, 4 of which can change, send or delete something, and 2 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 Radar MCP by usefulapi delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Release Radar MCP by usefulapi 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 Radar MCP by usefulapi have?
- 5 tools: 4 write, 1 read. release_radar_whats_broken_since_last_deploy, release_radar_oncall_handoff, release_radar_github_latest_deploy, release_radar_sentry_recent_issues and release_radar_incident_snapshot.
Does the Release Radar MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Release Radar MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Release Radar MCP by usefulapi changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Oct 25, 2026. Every change is on this page and in its Atom feed.