Skip to content

Release Radar MCP by usefulapi

by usefulapi.io · remote · no sign-in to list tools · v1.16.3 · published by io.usefulapi

Correlate GitHub releases with Sentry issues and PagerDuty incidents.

Changes · 4
CompareRegistry entry

5 tools: 4 change things and 1 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http release-radar https://release-radar.usefulapi.io/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Changes things 4Claude Code: ask
  • github_latest_deployLow-level building block: the latest GitHub deployment for a repo (falls back to the latest release), returning sha + timestamp.No findings

    Why it is in this group

    • The name "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 whats_broken_since_last_deploy. GitHub: GET /repos/{owner}/{repo}/deployments.
  • 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.
    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.
  • 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.
    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.
  • whats_broken_since_last_deployCOMPOSITE.No findings

    Why it is in this group

    • The name "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).
Only reads 1Claude Code: allow
  • incident_snapshotCOMPOSITE.No findings

    Why it is in this group

    • The name "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.

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.

Install

Pinned to version 1.16.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http release-radar https://release-radar.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__release-radar__incident_snapshot"
    ],
    "ask": [
      "mcp__release-radar__whats_broken_since_last_deploy",
      "mcp__release-radar__oncall_handoff",
      "mcp__release-radar__github_latest_deploy",
      "mcp__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. It assumes the server is installed as release-radar. Review it before you use it.