This release includes 1 breaking change for platform teams planning a safe upgrade.
✓ No known CVEs patched in this version
Affected surfaces
ReleasePort's take
Light signalThe `server.tool()` shorthand has been removed; all tools must now be registered with `server.registerTool()`. Additionally, tool metadata now includes a human‑readable title and behavior annotations.
Why it matters: Migration to `registerTool()` is required for any code using the deprecated `server.tool()` API. Tools lacking a title or behavior annotations will fail validation in this release.
Summary
AI summaryUpdates What hosts get, Back-compat, and Also across a mixed release.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Breaking | High |
Migrated all tools from `server.tool()` shorthand to `server.registerTool()`. Migrated all tools from `server.tool()` shorthand to `server.registerTool()`. Source: llm_adapter@2026-06-12 Confidence: high |
— |
| Feature | Medium |
Every tool now has a human‑readable title field. Every tool now has a human‑readable title field. Source: llm_adapter@2026-06-12 Confidence: high |
— |
| Feature | Medium |
All tools declare behavior annotations (`readOnlyHint`, `destructiveHint`, `idempotentHint`, `openWorldHint`). All tools declare behavior annotations (`readOnlyHint`, `destructiveHint`, `idempotentHint`, `openWorldHint`). Source: llm_adapter@2026-06-12 Confidence: high |
— |
| Feature | Medium |
Every tool now declares an `outputSchema` and returns structured content alongside JSON text. Every tool now declares an `outputSchema` and returns structured content alongside JSON text. Source: llm_adapter@2026-06-12 Confidence: high |
— |
| Feature | Medium |
`categories` resource migrated to `registerResource` with a title. `categories` resource migrated to `registerResource` with a title. Source: llm_adapter@2026-06-12 Confidence: high |
— |
| Bugfix | Low |
Fixed a stale link in `load_knowledge_pack` description pointing to the archived registry. Fixed a stale link in `load_knowledge_pack` description pointing to the archived registry. Source: llm_adapter@2026-06-12 Confidence: high |
— |
Full changelog
What's new in 1.7.0
Step #2 of the MCP modernization roadmap: the entire tool surface migrated off the deprecated `server.tool()` shorthand (removed in SDK 2.0) onto `server.registerTool()`. No engine behavior changes; full back-compat.
What hosts get
- Titles — every tool has a human-readable display name ("Forget a fact", not `memory_forget`).
- Behavior annotations — all 23 tools declare `readOnlyHint` / `destructiveHint` / `idempotentHint` / `openWorldHint`:
- the 3 destructive tools (`memory_forget`, `unload_pack`, `unregister_platform`) are flagged for confirmation UIs
- the read-only inspectors (`list_*`, `memory_search`, `get_trace`, `explain_last_curation`, …) are flagged safe-to-call-freely
- the 7 network-reaching tools (LLM / embeddings / web search) carry `openWorldHint: true`
- Structured output — every tool declares an `outputSchema` and returns `structuredContent` alongside the JSON text. Schemas are permissive by design (all-optional, passthrough) — they document the shape without ever rejecting engine output.
- The `categories` resource migrated to `registerResource` with a title.
Back-compat (verified, not assumed)
- Text content is byte-identical for every tool — including the three array-returning `list_*` tools, whose text stays a bare array while `structuredContent` wraps it in an object per the MCP spec.
- Error returns unchanged (`isError: true` + JSON text); error responses skip output-schema validation by SDK design.
- Verified: wire test 7/7 · integration 9/9 · day2 ✅ · 26/27 local evals with zero output-validation errors · CI evals green on gpt-4o-mini.
Found during verification (external, not this release)
#3 — cloud `gpt-oss` thinking-channel responses can yield an empty `optimizedPrompt` (remote API change exposing a pre-existing field-name gap in `client.ts`). Root cause + fix sketch in the issue; targeted for 1.7.1.
Also
- Fixed a stale link in `load_knowledge_pack`'s description that still pointed at the archived `clarifyprompt-packs` registry — now points at the canonical `packs/` home.
Install
```bash
npm install -g [email protected]
```
Breaking Changes
- Removed the deprecated `server.tool()` shorthand; all tools must now be registered with `server.registerTool()`.
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
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).
Related context
Beta — feedback welcome: [email protected]