API Deprecation Radar MCP server
Count local API deprecation markers by broad severity without returning endpoint names, paths,...
A85/100grade A
Adoption
New
0 stars
Reviews
Write oneNobody has reviewed API Deprecation Radar yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
API Deprecation Radar tools (1)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
inspect_deprecation_radarCount local API deprecation markers by broad severity without returning endpoint names, paths, values, or source.
Public scan report
scanner v0.1.9 · 2026-09-21 · same rubric, same numbers if you re-run it
no findings
- Code scan8 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 44 days ago12/15
- Maintainer identityregistry namespace matches repository owner6/10
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
Runs npx -y api-deprecation-radar-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add api-deprecation-radar-mcp -- npx -y api-deprecation-radar-mcp
API Deprecation Radar: common questions
- Is API Deprecation Radar MCP server safe?
- Yes, by our scan: it is graded A (85/100). Read the API Deprecation Radar safety report
- How do I install API Deprecation Radar?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does API Deprecation Radar need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is API Deprecation Radar maintained?
- The last commit was 45 days ago (2026-08-09). The latest release is v1.0.1.