MCP Tools DirectoryAbout this integration
Detect breaking changes in your TypeScript library's public API and recommend the SemVer bump.
- Transport
- stdio
- Authentication
- none
- Initial setup
- none
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.13.0
- Package
- semver-checks
- Last compatibility test
- Not independently tested
Connect your agent
semver-checksPublisher documentation and the package manifest were reviewed only; the package, TypeScript analysis, dependency installation option, git operations, and npm retrieval were not executed or independently security-audited. Local-path operations need repository access, and npm or git inputs may cause network or repository reads when the tool is actually used.
Capabilities: Compare TypeScript API surfaces, Recommend semantic-version bumps, Extract bounded public API snapshots, Grade declared release bumps, Analyze local paths, git references, and npm packages
Connected profiles
Additional details
io.github.kyungseopk1m/semver-checks
Source ↗ · Checked 2026-09-170.13.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17semver-checks
Source ↗ · Checked 2026-09-190.13.0
Source ↗ · Checked 2026-09-19The publisher documents an npx command that starts the MCP server over stdio using the `--mcp` flag.
Source ↗ · Checked 2026-09-19No server credential is documented for local or public npm analysis; the README says npm-spec analysis needs nothing extra. Private registries or repositories may rely on ambient tooling configuration outside this review.
Source ↗ · Checked 2026-09-19The MCP client launches the package locally over stdio; individual calls can read local paths and git refs or retrieve public npm artifacts.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19