@mhdd_24/api-dependency-mcp
Related Servers
Alternatives to @mhdd_24/api-dependency-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables scanning code for deprecated annotations and comments, building a deprecation catalog, and tracking deprecated endpoints and features.311 npmISC
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to track cross-repo dependencies, surface affected consumers before changing shared artifacts, and monitor pinned versions for vulnerabilities.4MIT
- AlicenseBqualityCmaintenanceEnables static analysis and code smell detection by connecting to an external analysis API.131MIT
- AlicenseNot gradedqualityCmaintenanceEnables cross-repository architecture discovery and dependency routing across multi-service codebases, with automated scanning and batch AST indexing for AI agents to trace request lifecycles and navigate service boundaries.16 npmMIT
- AlicenseAqualityDmaintenanceEnables AI agents to map cross-repository dependencies, detect breaking changes in API contracts, and assess impact across services.10MIT
- FlicenseNot gradedqualityCmaintenanceEnables scanning code and URLs for API deprecations, auditing websites for professional quality, and running resale value scans from photo URLs over MCP streamable HTTP.-
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: status reports the scan root, scan discovers hardcoded URLs/clients, and map builds the dependency graph. There is no meaningful overlap between these operations.
All tools share the consistent 'apidep_' prefix and lowercase snake_case naming. The operation words—status, scan, map—are short and predictable within the server's domain.
With only three tools, the server is tightly scoped to the API dependency scanning workflow. Each tool serves a necessary purpose without redundant or filler operations.
The set covers the core workflow of showing the scan root, scanning for dependencies, and building a map. A minor gap is the lack of an explicit way to configure or update the scan root through the tool surface.