MCP SDK for TypeScript 1

Apply the Node.js 24 and TypeScript 7 prompts first. These rules cover MCP SDK for TypeScript 1 transports, authentication, tools, resources, prompts, sampling, elicitation, sessions, and deployment, and were checked against 1.30.0 and 1.30.1.

Transports and authentication

• Use Streamable HTTP for remote servers and keep stdio inside a trusted local process boundary; do not expose stdio through an unauthenticated bridge.
• Set enableDnsRebindingProtection: true on WebStandardStreamableHTTPServerTransport; it defaults false, so allowedHosts and allowedOrigins are otherwise not enforced.
• Populate both host and origin allowlists and bind to loopback for local servers; reject absent or unexpected Origin in middleware on browser-reachable endpoints, since the transport accepts an absent Origin.
• Enforce request-body limits before handleRequest or supplying parsedBody: 1.30.0's Streamable HTTP has no built-in byte limit, 1.30.1's maxRequestBodySize (4 MiB by default, answered with 413) is skipped when you supply parsedBody, and pre-parsing also bypasses legacy SSEServerTransport's 4mb read limit.
• Validate OAuth issuer, signature, expiry, scopes, and resource/audience for this MCP server; implement the specification's resource parameter handling.
• For protected HTTP servers, publish RFC 9728 protected-resource metadata and return a WWW-Authenticate challenge on 401; use 403 plus error="insufficient_scope" and the minimum required scope for step-up rather than silently broadening access.
• Never forward the MCP client's bearer token to an