---
summary: "Invalid tool arguments now come back as a structured InvalidParams envelope on both response surfaces, a blank NWS_USER_AGENT from a plugin host falls through to the default instead of the literal placeholder, and the development skill tree moved out of the directory plugin hosts auto-load. mcp-ts-core moves ^0.12.5 to ^0.13.0."
breaking: false
security: false
---

# 0.9.3 — 2026-09-13

## Changed

- **An invalid tool argument returns a structured `InvalidParams` (-32602) envelope** (mcp-ts-core 0.12.7) — an unknown key, wrong type, missing required field, or out-of-range value fails with `isError: true` and matching `structuredContent.error` and `content[]`, on both the 2025-11-25 and 2026-07-28 protocol revisions. No upstream NWS request is made. A client that read these rejections as `ValidationError` now sees `InvalidParams`.
- **`NWS_USER_AGENT` treats an empty string and an unsubstituted `${…}` placeholder as unset** (mcp-ts-core 0.13.0) — the default `(nws-weather-mcp-server, github.com/cyanheads/nws-weather-mcp-server)` applies instead of the literal text reaching `api.weather.gov`. A placeholder embedded in a real value is kept. The MCPB `user_config` option now defaults to `""` for this reason.
- **`NWS_USER_AGENT` is a declared, host-collected option in both plugin manifests** — `.claude-plugin/plugin.json` declares it under `userConfig` and passes `${user_config.nws_user_agent}`; `.codex-plugin/mcp.json` lists it in `env_vars` so Codex forwards an exported value.
- **The framework skill tree moved from `skills/` to `framework-skills/`** (mcp-ts-core 0.13.0) — Claude Code and Codex auto-load a plugin's root `skills/`, so installing this server as a plugin handed its development skills to the installing agent. No runtime behavior changed.
- **Bun engines floor raised to `>=1.4.0`** (mcp-ts-core 0.12.9). Node stays at `>=24.0.0`.
- **`bun run audit:fix` runs `bun audit fix`** (mcp-ts-core 0.13.0) — previously a read-only audit that changed nothing.
- **`nws_search_alerts` describes its `cursor` against the active-alert feed** rather than the upstream `/alerts/active` route a caller never constructs.
- Tooling and scaffold resync: `devcheck` parses Bun 1.4 `bun audit` output and attributes aliased `bun outdated` rows, `lint:packaging` gains the MCPB `user_config` wiring checks, and the issue forms accept blank reports and route vulnerabilities to a private advisory.

## Removed

- **`MCP_RESPONSE_VERBOSITY` and the `OAUTH_PROXY_*` variables are no longer recognized** (mcp-ts-core 0.12.8) — both were validated at startup and read by nothing; drop them from any `.env` or deployment config.

## Fixed

- **A trailing slash on `MCP_PUBLIC_URL` no longer doubles in advertised links** (mcp-ts-core 0.12.8) — the landing page and `/.well-known/mcp.json` server card resolve the public origin the way the OAuth metadata paths already did.
- **A cancelled request's SSE stream closes immediately** (mcp-ts-core 0.12.9) — `notifications/cancelled` for an in-flight single-request POST closes that stream instead of holding it to keep-alive or session expiry.
- **The landing page's curl snippet sends a handshake `initialize` accepts** (mcp-ts-core 0.12.9) — it pinned a protocol revision in a header; it now sends the latest revision with `Accept: application/json, text/event-stream`.

## Dependencies

- `@cyanheads/mcp-ts-core` `^0.12.5 → ^0.13.0`
- `zod` `^4.5.4 → ^4.6.1`
- `@biomejs/biome` (dev) `^2.5.11 → ^2.5.13`
- `@types/node` (dev) `^26.4.0 → ^26.5.1`
- `vitest`, `@vitest/coverage-istanbul` (dev) `^4.1.11 → ^5.0.0`
- `ignore` (dev) `^7.0.8 → ^7.0.9`
- `tsc-alias` (dev) `^1.9.3 → ^1.9.4`
