@mhdd_24/api-versioning-mcp
Related Servers
Alternatives to @mhdd_24/api-versioning-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI clients to validate OpenAPI specs, compare versions, detect breaking changes, and generate changelogs.4MIT
- FlicenseNot gradedqualityDmaintenanceProvides a streamable HTTP endpoint for compatibility analysis, with published contracts and schemas for integration.-
- AlicenseNot gradedqualityBmaintenanceProvides semantic versioning tools to parse, compare, and check range satisfaction for version strings, enabling version management through natural language queries.7 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to browse, read, compare, and validate OpenAPI contracts for providers and consumers.1MIT
- AlicenseAqualityBmaintenanceEnables checking project files like Dockerfile, .nvmrc, and CI workflows to determine whether pinned runtime, database, and OS versions are still supported, providing end-of-life dates, latest patches, and upgrade targets for 470+ products.31MIT
- FlicenseNot gradedqualityDmaintenanceProvides breaking changes analysis for libraries across multiple languages, enabling version upgrade planning, dependency audits, and migration reports through MCP tool access and expert workflows.-
TDQS
Scored across 3 tools
The three tools have clearly distinct purposes: status is a health check, compare diffs two path lists, and strategy produces advisory notes. No overlap or ambiguity exists between them.
All tools share the consistent apiver_ prefix followed by a single descriptive noun (status, compare, strategy). The pattern is predictable and readable throughout.
Three tools is a small but reasonable set for a narrow, focused domain like API versioning diagnostics. It is slightly thin but each tool earns its place without redundancy.
The surface covers health, comparison, and strategy advice, but lacks core versioning operations such as detecting breaking changes, transforming/rewriting paths, or applying a versioning scheme. Notable gaps remain for real versioning workflows.