io.github.CloudCorpRecords/versionbump vs io.github.kyungseopk1m/semver-checks
io.github.CloudCorpRecords/versionbump is an MCP server published by CloudCorpRecords. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.kyungseopk1m/semver-checks is an MCP server published by kyungseopk1m. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.CloudCorpRecords/versionbump |  io.github.kyungseopk1m/semver-checks |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.17.0 Downloads/month (npm): 1 010 Downloads/week (npm): 335 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.CloudCorpRecords/versionbump | io.github.kyungseopk1m/semver-checks |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-11-06 |
| Where it runs (differs) | On your machine (@reneturcios/versionbump) | On your machine (semver-checks) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/cloudcorprecords/versionbump | github.com/kyungseopk1m/semver-checks |
| Changes in the last 7 days (differs) | 2 | 1 |
| First seen (differs) | 2026-11-02 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.CloudCorpRecords/versionbump
Recommend a semver bump from commit types and API surface changes, with the evidence listed.
io.github.kyungseopk1m/semver-checks
Detect breaking changes in your TypeScript library's public API and recommend the SemVer bump.
How to run each
io.github.CloudCorpRecords/versionbump As a local MCP server: npm package
claude mcp add --transport stdio versionbump -- npx -y @reneturcios/versionbump mcpio.github.kyungseopk1m/semver-checks As a local MCP server: npm package
claude mcp add --transport stdio semver-checks -- npx -y semver-checks --mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: io.github.CloudCorpRecords/versionbump · What it can do: io.github.kyungseopk1m/semver-checks · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.