Skip to content

This release includes breaking changes for platform teams planning a safe upgrade.

Published 1mo MCP Developer Tools
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Summary

AI summary

Minor fixes and improvements.

Full changelog

Patch release on top of 1.5.0

Runtime behavior is identical to 1.5.0. This release exists to fix the README marketing-surface drift that shipped with the 1.5.0 npm tarball, and to add the missing ship-check audit so a future release can't repeat the mistake.

What was wrong

The 1.5.0 release shipped with:

  • package.json ✅ on 1.5.0
  • package-lock.json ✅ on 1.5.0
  • server.json ✅ on 1.5.0
  • src/index.ts McpServer literal ✅ on 1.5.0
  • CHANGELOG.md [1.5.0] entry ✅ present
  • README headline blockquote ❌ still on 1.4.0
  • README "What's new in X" heading ❌ still on 1.4.0
  • README "cumulative through X" annotation ❌ still on 1.4.0

Every machine-readable version surface was correct. Only the prose drifted, because nothing automated touched the README's marketing surfaces. The existing version-consistency ship-check (general check #1) didn't catch it.

What 1.5.1 fixes

  • Headline blockquote, "What's new in 1.5.1" section, and "cumulative through 1.5.1" annotation all reference the current version.
  • The 1.5.0 narrative is preserved (renamed ## What's new in 1.5.0) because that's where the actual runtime changes shipped.
  • The eval-fixture count in the 1.4 section corrected to reflect the post-1.5 reality (23 fixtures, not 20).

What 1.5.1 adds (ship-check)

  • CP-11 — README marketing-surface coherence. Hard-fails the audit if the headline blockquote, "What's new in X" heading, or "cumulative through X" annotation reference any version other than package.json#version.
  • CP-12 — Platform-pack format validity. Parses every packs/platforms/*.yaml and asserts schema validity (known category.id, ≥1 platform with id/label/description, defaultPlatform references an existing platform).
  • CP-11 promoted to the cross-project user-scoped ship-check skill the same day, so future projects (not just clarifyprompt-mcp) get this check by default. The promotion uses heuristics that don't hardcode this repo's specific heading templates — any project with a marketing-style README benefits.

Compatibility

  • No code changes. No new MCP tools, no removed tools, no new env vars.
  • No reason to upgrade urgently. If you're on 1.5.0, the engine is identical. The only reason to bump is so the npm package page shows the correct story.
  • Tarball: 140.1 kB packed (was 137.9 kB) / 468.9 kB unpacked. The +2.2 kB is README + CHANGELOG.

Install

npx clarifyprompt-mcp

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track LumabyteCo/clarifyprompt-mcp

Get notified when new releases ship.

Sign up free

About LumabyteCo/clarifyprompt-mcp

MCP server for AI prompt optimization — transforms vague prompts into platform-optimized prompts for 58+ AI platforms across 7 categories (image, video, voice, music, code, chat, document).

All releases →

Beta — feedback welcome: [email protected]