API Deprecation Radar MCP server

by mrfentmen·io.github.mrfentmen/api-deprecation-radar-mcp·v1.0.1

No reviews yet

Count local API deprecation markers by broad severity without returning endpoint names, paths,...

A85/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A85/100

full report

Adoption

New

0 stars

Reviews

Write one

Nobody 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 posts

Read from the package source without running it. The installed server may list more.

inspect_deprecation_radar
Count local API deprecation markers by broad severity without returning endpoint names, paths, values, or source.

Public scan report

scanner v0.1.10 · 2026-11-01 · 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 84 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.Rubric Appeal a finding JSON

How API Deprecation Radar compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 85/100; higher than 72% of 48,114 servers
Tools: 1; the typical server has 7
Tools that change things: 0%; typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 1 read

Install API Deprecation Radar in Claude Code, Cursor or VS Code

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

Add to Cursor

What the publisher says

From the API Deprecation Radar repository's README, as published. We do not edit it. Read it on GitHub

api-deprecation-radar-mcp

API Deprecation Radar counts deprecation, sunset, and obsolete markers in local API-adjacent files. It gives maintainers a quick review queue without exposing endpoint names or code.

Quick start

npm install
npm test
npm start

Use inspectdeprecationradar with a bounded local project path.

Privacy and limits

The output contains counts and broad severity buckets only. Marker severity is heuristic and should be reviewed by a developer. No endpoint names, paths, source text, values, or filenames are emitted.

Nothing above is checked by us. What we check is on the safety report.

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, Cursor, VS Code or Claude Desktop 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 99 days ago (2026-08-09). The latest release is v1.0.1.
How does API Deprecation Radar compare with other MCP servers?: safety score 85/100 (higher than 72% of 48,114 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.