A
licenseA
qualityC
maintenanceEnables scanning repositories for hardcoded service URLs and clients, and building service-to-service API dependency maps.
3
ISC
@mhdd_24/api-deprecation-mcp
by Mhdd-24
Related Servers
Alternatives to @mhdd_24/api-deprecation-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables whole-program callgraph reachability analysis to locate dead functions and stale flags, and integrates with MCP-compliant clients for automated code review, breaking-change audits, and CI/CD workflow pruning.8-
- AlicenseNot gradedqualityDmaintenanceEnables scanning projects for dependency vulnerabilities, secrets, license conflicts, code quality, and git health, returning a 0-100 health score with actionable suggestions.1 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to scan codebases for TODO/FIXME/XXX patterns and get prioritized results over MCP, supporting CI gates and multiple output formats.-
- FlicenseNot gradedqualityCmaintenanceEnables scanning of EKS cluster maturity and repository configuration through MCP tools, providing diagnostic reports as markdown.-
- AlicenseAqualityFmaintenanceEnables scanning projects for leaked secrets and security issues directly from Claude Code, detecting secret categories, dangerous code patterns, and git hygiene issues.220 PyPI1MIT
TDQS
B3/5.0
Scored across 3 tools
Disambiguation4/5
The three tools have clearly distinct purposes: status shows the scan root, scan performs the actual deprecation search, and catalog builds a structured result. Minor overlap exists between status and scan since status may imply scanning state, but descriptions are sufficient to differentiate them.
Naming Consistency4/5
All tools share the consistent 'apidepr_' prefix, which creates a clear namespace. However, the suffix pattern is mixed: 'status' and 'catalog' are nouns while 'scan' is a verb, so it is not a strict verb_noun convention.
Tool Count4/5
Three tools is a reasonable, focused count for a narrow deprecation-scanning server. The scope is small enough that each tool earns its place without feeling thin or excessive.
Completeness3/5
The core scan workflow is covered: view the scan root, run the scan, and build a catalog. However, there is no obvious tool for configuring the scan root, viewing raw scan results, or performing follow-up actions on detected deprecations, which leaves minor gaps.
Maintenance
ActivityMaintained
ResponsivenessNo issues