Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Release Radar MCP by usefulapi

REMOTE · RELEASE-RADAR.USEFULAPI.IO

Correlate GitHub releases with Sentry issues and PagerDuty incidents.

0 this week 18 Trust /100

Last scanned (15 hours ago)

Scores higher than 3% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Monitoring and Observability

Trust breakdown (7 categories)

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 Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (4)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (7)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 2 Nov 26 −45
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 31 Oct 26 +3
    • Authorization: partial → pass ▲ security
    • MCP protocol: fail → pass ▲ functional
    • New prompt “check_when_the_latest_deploy_went_out” functional
    • New prompt “find_what_broke_since_the_last_deploy” functional
    • New prompt “get_a_snapshot_of_what_is_on_fire_now” functional
    • New prompt “list_recent_unresolved_sentry_issues” functional
    • New prompt “prepare_an_on_call_handoff_briefing” functional
    • MCP protocol version: 2025-06-18 → 2025-11-25 functional
    • Server version: 1.33.0 → 1.35.0 functional
    • Server version: 1.32.0 → 1.33.0 functional
    • Server version: 1.31.2 → 1.32.0 functional
  • 30 Oct 26 0
    • Server version: 1.31.1 → 1.31.2 functional
    • Server version: 1.31.0 → 1.31.1 functional
  • 29 Oct 26 0
    • Server version: 1.30.0 → 1.31.0 functional
    • Server version: 1.29.0 → 1.30.0 functional
  • 28 Oct 26 0
    • Server version: 1.27.0 → 1.29.0 functional
  • 27 Oct 26 0
    • Server version: 1.26.0 → 1.27.0 functional
  • 25 Oct 26 0
    • Server version: 1.24.0 → 1.26.0 functional
    • Server version: 1.23.0 → 1.24.0 functional
    • Server version: 1.22.4 → 1.23.0 functional
    • Server version: 1.22.3 → 1.22.4 functional
    • Server version: 1.22.0 → 1.22.3 functional
Diagnostics

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 21 Nov 2026 · Probed https://release-radar.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usefulapi.io CN=WE1,O=Google Trust Services,C=US 11 Nov 2026 9 Feb 2027 ECDSA 256 ECDSA-SHA256 93e2fea3bbc31354138c8a47c5e87592
SANs: usefulapi.io, *.usefulapi.io
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 release-radar.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
usefulapi.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 302

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://release-radar.usefulapi.io/mcp Redirected 302 https://usefulapi.io/release-radar/
http (plaintext) http://release-radar.usefulapi.io/mcp Inconclusive 302 http://release-radar.usefulapi.io/mcp
MCP tools · 5 exposed · ~729 tokens

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 →

Tool Tokens
release_radar_github_latest_deploy ~104

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.

NameTypeReqDescription
environmentstring–Filter deployments to this environment.
ownerstringyesGitHub repo owner/org.
repostringyesGitHub repo name.

No output schema declared.

No examples provided.

release_radar_incident_snapshot ~104

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.

NameTypeReqDescription
sentry_projectstring–Sentry project slug/id. Falls back to SENTRY_PROJECT env if omitted.
urgencystring–Filter PagerDuty incidents by urgency.

No output schema declared.

No examples provided.

release_radar_oncall_handoff ~206

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.

NameTypeReqDescription
ownerstringyesGitHub repo owner/org, e.g. 'vercel'.
repostringyesGitHub repo name, e.g. 'next.js'.
sentry_projectstring–Sentry project slug/id. Falls back to SENTRY_PROJECT env if omitted.

No output schema declared.

No examples provided.

release_radar_sentry_recent_issues ~123

Low-level building block: unresolved Sentry issues over a relative window. Sentry: GET /api/0/projects/{org}/{project}/issues/?query=is:unresolved.

NameTypeReqDescription
environmentstring–Filter issues to this environment.
limitinteger–Max issues. Default 25.
sentry_projectstring–Sentry project slug/id (falls back to SENTRY_PROJECT env).
statsPeriodstring–Relative window, e.g. '24h', '14d'. Default 24h.

No output schema declared.

No examples provided.

release_radar_whats_broken_since_last_deploy ~192

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).

NameTypeReqDescription
environmentstring–Filter GitHub deployments and Sentry issues to this environment, e.g. 'production'.
ownerstringyesGitHub repo owner/org, e.g. 'vercel'.
repostringyesGitHub repo name, e.g. 'next.js'.
sentry_projectstring–Sentry project slug/id. Falls back to SENTRY_PROJECT env if omitted.

No output schema declared.

No examples provided.

Install

How do I install the Release Radar MCP by usefulapi server?

Release Radar MCP by usefulapi is a hosted endpoint at https://release-radar.usefulapi.io/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 · release-radar.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-release-radar 'https://release-radar.usefulapi.io/mcp'
Common questions

What is the Release Radar MCP by usefulapi server?

Release Radar MCP by usefulapi is listed in the public MCP registry as io.usefulapi/release-radar. Correlate GitHub releases with Sentry issues and PagerDuty incidents. This page covers its hosted endpoint (https://release-radar.usefulapi.io/mcp).

Is the Release Radar MCP by usefulapi server safe to use?

Release Radar MCP by usefulapi scores 18 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 Radar MCP by usefulapi server expose?

Release Radar MCP by usefulapi exposes 5 tools: release_radar_whats_broken_since_last_deploy, release_radar_incident_snapshot, release_radar_oncall_handoff, release_radar_github_latest_deploy, release_radar_sentry_recent_issues. Their descriptions and schemas cost roughly 729 tokens of context every time the server is loaded.

Does the Release Radar MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Release Radar MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Release Radar MCP by usefulapi server still maintained?

Release Radar MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Release Radar MCP by usefulapi server?

VerifyMCP ran 4 checks on Release Radar MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Release Radar MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.