A
licenseNot graded
qualityC
maintenanceEnables coding agents to retrieve maintainer-written release notes and compare installed versus target dependency versions, search packages, and report on projects pushed to a dashboard.
MIT
@weiseer/api-changelog-mcp
by weiseer
Related Servers
Alternatives to @weiseer/api-changelog-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceProvides structured migration briefs for LLM coding agents covering breaking changes, codemod coverage, and hallucination warnings for major version bumps of packages like tailwindcss, next, and react.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to monitor web documentation for changes, perform semantic search with RAG, and analyze breaking changes in APIs.9-
- AlicenseAqualityCmaintenanceProvides accurate, source-grounded breaking-change briefings for npm packages by reading real GitHub release notes and CHANGELOGs, helping coding agents avoid hallucinated dependency migrations.33 npmMIT
- AlicenseAqualityCmaintenanceChecks npm and PyPI packages for outdated versions, deprecation status, and breaking changes with cited sources, enabling AI agents to verify dependency freshness.17 npmISC
- AlicenseNot gradedqualityAmaintenanceEnables coding agents to query breaking API changes in dependencies since a model's training cutoff, retrieve project dependency change summaries, and look up model training cutoff dates.1MIT
TDQS
A3.7/5.0
Scored across 4 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: listing tracked packages, fetching a full record, querying recent breaking changes across packages, and checking breaking changes for a specific version. No ambiguity between them.
Naming Consistency5/5
All tool names follow a consistent verb_noun snake_case pattern: list_tracked, get_package, get_recent_breaking, check_version. Naming is predictable and clear.
Tool Count4/5
With 4 tools, the server is well-scoped for its purpose of tracking API changelogs. It covers the essential operations (list, detail, recent, version check) without being too few or too many.
Completeness4/5
The tool set covers the main use cases: listing packages, getting full details, recent breaking changes, and version-specific impact. A minor gap is the lack of a tool to view actual changelog entries, but check_version essentially provides that for breaking changes.
Maintenance
ActivityInactive
ResponsivenessNo issues