Release Radar MCP by usefulapi
io.usefulapi/release-radar
Correlate GitHub releases with Sentry issues and PagerDuty incidents.
This endpoint completed initialize and tools/list. No tool was called.
- Rank
- #2392
- Score
- 82
- Tool tokens
- 976
- Tools
- 5
Tools
Token cost is the o200k count of the tools list JSON, including schemas, before any tool is called.
whats_broken_since_last_deploy
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'
incident_snapshot
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
oncall_handoff
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)
github_latest_deploy
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/{
sentry_recent_issues
Low-level building block: unresolved Sentry issues over a relative window. Sentry: GET /api/0/projects/{org}/{project}/issues/?query=is:unresolved.
Nearby in GitHub
Up-to-date code docs for any prompt
MCP server for Financial Modeling Prep API with 250+ financial data tools
Official SerpApi MCP server for Google, Bing, and other search engines.
Comprehensive PostgreSQL documentation and best practices, including ecosystem tools