DeepSeek Responses API update
This release brings the MCP server up to date with DeepSeek's August 2026 V4 API surface and current supported MCP SDK v1 dependencies.
Added
create_responsefor the native DeepSeek/responsesAPI.- Non-streaming and semantic streaming response handling.
- Structured Responses input, function tools, web-search tools, structured output, and reasoning effort controls.
- Chat Completions
lowreasoning effort anduser_idsupport. - Streamable HTTP integration coverage for both stateless and stateful modes.
MCP_HTTP_ALLOWED_ORIGINSfor explicit browser Origin allowlisting.
Fixed
- Stateless Streamable HTTP now creates a fresh MCP server and transport per request, as required by MCP SDK 1.30.
- Failed Responses results now return MCP tool errors with provider details and retryability hints.
- Structured response items and nested content parts validate required fields before reaching DeepSeek.
- Responses calls now honor
DEEPSEEK_DEFAULT_MODELwhenmodelis omitted. - Browser preflight responses include current MCP protocol/session headers and reject unapproved origins.
Updated
@modelcontextprotocol/sdk1.30.0- Zod 4.4.3
- Vitest 4.1.10
- Node type definitions 25.9.5
- Registry metadata, API notes, README, and local/remote smoke scripts
Verified
- Clean
npm ci npm audit— 0 vulnerabilitiesnpm run buildnpm test— 25 tests across 4 files- Stateful and stateless Streamable HTTP behavior
npm pack --dry-run --jsonserver.jsonvalidation against the published MCP Registry schema- Snyk PR security check
- Multi-round Codex review with all actionable findings resolved
The OCI image remains at 0.5.0; this repository does not contain an automated Docker publishing workflow.