Model Context Protocol server for Rollbar
Nothing to run from here
Release Radar is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
5
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Correlate GitHub releases with Sentry issues and PagerDuty incidents.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http release-radar-mcp https://release-radar.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# whats_broken_since_last_deploy, incident_snapshot, oncall_handoff and 2 more
Release Radar costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http release-radar-mcp https://release-radar.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| owner | string | yes | GitHub repo owner/org, e.g. 'vercel'. |
| repo | string | yes | GitHub repo name, e.g. 'next.js'. |
| sentry_project | string | no | Sentry project slug/id. Falls back to SENTRY_PROJECT env if omitted. |
| environment | string | no | Filter GitHub deployments and Sentry issues to this environment, e.g. 'production'. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sentry_project | string | no | Sentry project slug/id. Falls back to SENTRY_PROJECT env if omitted. |
| urgency | string | no | Filter PagerDuty incidents by urgency. |
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 wit
| Parameter | Type | Required | Notes |
|---|---|---|---|
| owner | string | yes | GitHub repo owner/org, e.g. 'vercel'. |
| repo | string | yes | GitHub repo name, e.g. 'next.js'. |
| sentry_project | string | no | Sentry project slug/id. Falls back to SENTRY_PROJECT env if omitted. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| owner | string | yes | GitHub repo owner/org. |
| repo | string | yes | GitHub repo name. |
| environment | string | no | Filter deployments to this environment. |
Low-level building block: unresolved Sentry issues over a relative window. Sentry: GET /api/0/projects/{org}/{project}/issues/?query=is:unresolved.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sentry_project | string | no | Sentry project slug/id (falls back to SENTRY_PROJECT env). |
| statsPeriod | string | no | Relative window, e.g. '24h', '14d'. Default 24h. |
| environment | string | no | Filter issues to this environment. |
| limit | integer | no | Max issues. Default 25. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Release Radar or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
1.11.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Release Radar can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.