Deprecation Radar
Count local API deprecation markers by broad severity without returning endpoint names, paths,...
Runs on your machine from its package; the steps are below.
What it does
- Reads
- Writes
- High impact
At most: only reads or looks up information.
What it costs
FreeOdel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y api-deprecation-radar-mcp
MCP client config
{
"mcpServers": {
"deprecation-radar": {
"command": "npx",
"args": [
"-y",
"api-deprecation-radar-mcp"
]
}
}
}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 inspect_deprecation_radar 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.
