Skip to main content
Glama
weiseer

@weiseer/api-changelog-mcp

by weiseer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to @weiseer/api-changelog-mcp

No user-submitted related servers found.

    Related Servers

    • Vigia

      MatiasDelosSantos
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Verified, dated facts for AI coding agents: what breaks between npm package versions (diffed from TypeScript types), per-version vulnerabilities, the newest version compatible with a given Node/Python/Rust/PHP, end-of-life dates of ~480 runtimes and frameworks, and AI model prices. Covers npm, PyPI, crates.io and Packagist.
      AGPL 3.0

    • dependency-migration-mcp

      SolvoHQ
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides 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.
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    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

    Resources