Api Deprecation Radar Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.1Updated Oct 30, 2026

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

VerifiedSTDIODesktop onlyDeveloper ToolsData & Analytics

Overview

AI-generated overview

A local MCP server that counts API deprecation, sunset and obsolete markers in a project's files and returns only severity totals.

What you can do
  • Inspect a bounded local project path for API deprecation markers.
  • Return counts grouped into broad severity buckets.
  • Keep output free of endpoint names, paths, filenames, source text or values.
When to use it
Useful when a maintainer wants a quick, privacy-preserving review queue of deprecation, sunset and obsolete markers across a local codebase before planning cleanup work.
Requirements
Runs as a local stdio process installed from the npm package api-deprecation-radar-mcp, so Node.js and npm are needed. It reads a local project path supplied by the user. No authentication, environment variables or headers are declared.
Before you install
It reads files from a local project path, so point it only at directories you intend to scan. Severity buckets are heuristic and should be reviewed by a developer. Output is limited to counts and buckets, with no endpoint names, paths, filenames or source text.

Installation

In SourceWeft

  1. Open Api Deprecation Radar Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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

bash
npm installnpm testnpm 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.

Source: README.md at commit 1083b5d

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 22, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.