@wrongstack/mcp 1.0.3 → 1.0.5

package/dist/constants.d.ts

@@ -6,9 +6,36 @@
  * - Reconnect parameters can be overridden via config in the future
  * - No scattered magic values across multiple files
  */
+/**
+ * Protocol revisions this package actually implements, newest first.
+ *
+ * Deliberately conservative: a revision belongs here only once its wire
+ * requirements are met, because the version we send in `initialize` is a
+ * promise about what the peer may then use. WrongStack speaks the 2024-11-05
+ * shape — tools, resources, prompts, sampling — and does not implement the
+ * additions of later revisions (elicitation, structured tool output, resource
+ * links), so listing one of those would advertise capabilities that are not
+ * there.
+ *
+ * Adding a revision: implement its additions, then put it at the FRONT.
+ * `PROTOCOL_VERSION` follows automatically, and the negotiation below starts
+ * accepting a peer that asks for it.
+ */
+export declare const SUPPORTED_PROTOCOL_VERSIONS: readonly string[];
+/**
+ * Pick the version to answer an `initialize` with.
+ *
+ * The spec's rule: echo what the peer asked for when it is supported,
+ * otherwise reply with our own latest and let the peer decide whether it can
+ * continue. Before this existed the server ignored the request entirely and
+ * always answered `2024-11-05`, so a peer that asked for a newer revision was
+ * told it had been granted nothing of the sort — silently, with no way to see
+ * the mismatch.
+ */
+export declare function negotiateProtocolVersion(requested: unknown): string;
 export declare const MCP_CONSTANTS: Readonly<{
-    /** MCP protocol version advertised during handshake. */
-    readonly PROTOCOL_VERSION: '2024-11-05';
+    /** MCP protocol version advertised during handshake: the newest we implement. */
+    readonly PROTOCOL_VERSION: string;
     /** Identity announced to MCP servers during `initialize`. */
     readonly CLIENT_INFO: Readonly<{
         name: "wrongstack";

package/dist/index.d.ts

@@ -1,7 +1,7 @@
 export { authorizationHeaderForToken, authorizationServerMetadataUrls, canonicalMcpResource, createMcpAuthorizationRequest, discoverMcpAuthorization, exchangeMcpAuthorizationCode, type MCPAccessToken, type MCPAuthorizationChallenge, type MCPAuthorizationContext, type MCPAuthorizationDiscoveryOptions, type MCPAuthorizationDiscoveryResult, type MCPAuthorizationJsonFetcher, type MCPAuthorizationProvider, type MCPAuthorizationRequestOptions, type MCPAuthorizationServerMetadata, type MCPAuthorizationSession, type MCPProtectedResourceMetadata, type MCPTokenExchangeOptions, type MCPTokenRefreshOptions, type MCPTokenSet, parseAuthorizationServerMetadata, parseMcpAuthorizationCallback, parseMcpBearerChallenge, parseProtectedResourceMetadata, protectedResourceMetadataUrls, refreshMcpAccessToken, validateMcpAuthorizationServerMetadata, } from './authorization.js';
 export { type MCPAuthorizationCompleteInput, MCPAuthorizationManager, type MCPAuthorizationManagerOptions, type MCPAuthorizationStartInput, type MCPAuthorizationStartResult, type MCPAuthorizationStatus, } from './authorization-manager.js';
 export { MCPClient, type MCPClientOptions, type MCPListChangedListener, type MCPPageOptions, type MCPRequestOptions, type Transport, } from './client.js';
-export { MCP_CONSTANTS } from './constants.js';
+export { MCP_CONSTANTS, negotiateProtocolVersion, SUPPORTED_PROTOCOL_VERSIONS, } from './constants.js';
 export { DEFAULT_MCP_INSERTION_MAX_BYTES, DEFAULT_MCP_RESOURCE_SCHEMES, type MCPContentProvenance, type MCPInsertionPolicy, type MCPPromptInsertion, type MCPResourceInsertion, preparePromptInsertion, prepareResourceInsertion, } from './content-selection.js';
 export type { ConnectionState, JsonRpcResponse, MCPTool, ToolCallResult, } from './contracts.js';
 export { addMcp, disableMcp, discoverMcp, enableMcp, listMcp, MCP_ENV_MASK, type McpManageDeps, type McpOpResult, type McpServerInfo, type McpServerInput, removeMcp, restartMcp, updateMcp, } from './manage.js';

package/dist/index.js

@@ -875,9 +875,16 @@ function parseEmptyResult(value) {
 }
 
 // src/constants.ts
+var SUPPORTED_PROTOCOL_VERSIONS = Object.freeze(["2024-11-05"]);
+function negotiateProtocolVersion(requested) {
+  if (typeof requested === "string" && SUPPORTED_PROTOCOL_VERSIONS.includes(requested)) {
+    return requested;
+  }
+  return MCP_CONSTANTS.PROTOCOL_VERSION;
+}
 var MCP_CONSTANTS = Object.freeze({
-  /** MCP protocol version advertised during handshake. */
-  PROTOCOL_VERSION: "2024-11-05",
+  /** MCP protocol version advertised during handshake: the newest we implement. */
+  PROTOCOL_VERSION: SUPPORTED_PROTOCOL_VERSIONS[0],
   /** Identity announced to MCP servers during `initialize`. */
   CLIENT_INFO: Object.freeze({
     name: "wrongstack",
@@ -2464,6 +2471,7 @@ var MCPClient = class _MCPClient {
     this.disconnectListeners.delete(listener);
   }
   async connect() {
+    if (this.state === "connected" || this.state === "connecting") return;
     this.state = "connecting";
     this._serverMetadata = void 0;
     try {
@@ -5029,7 +5037,9 @@ var MCPServer = class {
     switch (method) {
       case "initialize":
         return {
-          protocolVersion: MCP_CONSTANTS.PROTOCOL_VERSION,
+          protocolVersion: negotiateProtocolVersion(
+            params?.protocolVersion
+          ),
           capabilities: {
             tools: { listChanged: false },
             ...this.resources.length > 0 ? { resources: { subscribe: false, listChanged: false } } : {},
@@ -5118,13 +5128,17 @@ var MCPServer = class {
    * tools are written against the schema they declared.
    *
    * SCOPE: `validateAgainstSchema` is the shared validator that also gates the
-   * agent's own tool executor. It checks `type`, `enum`, and `required`, and
-   * recurses through `properties`/`items` — it does NOT check
-   * `additionalProperties: false`, numeric bounds, or string lengths. So those
-   * keywords stay advisory here. Teaching the shared validator about them
-   * would change what the agent accepts on every tool call in the product,
-   * which is a deliberate decision that does not belong inside a transport
-   * fix; it is tracked separately.
+   * agent's own tool executor. It checks `type`, `enum`, `required`, recurses
+   * through `properties`/`items`, enforces numeric bounds
+   * (`minimum`/`maximum`), rejects unknown keys on strict-closed objects
+   * (`additionalProperties: false`), validates the `additionalProperties`
+   * subschema form against unknown-key values, applies `patternProperties`
+   * to matching keys, enforces string lengths (`minLength`/`maxLength`) and
+   * `pattern`, array lengths (`minItems`/`maxItems`/`uniqueItems`), and the
+   * combinators `allOf`/`anyOf`/`oneOf` (all landed 2026-09-11). Still
+   * advisory per the 2026-09-11 usage survey: `const` and `$ref` — declared
+   * only in the techstack rulebook, which validates with its own
+   * `validateRulebook`, not this validator.
    *
    * Unknown tool names are left alone — the host owns that error, and
    * answering "no such tool" here would fork the message for no benefit.
@@ -5807,6 +5821,7 @@ export {
   MCP_OPERATION_LIMITS,
   SSEReader,
   SSETransport,
+  SUPPORTED_PROTOCOL_VERSIONS,
   StreamableHTTPTransport,
   addMcp,
   authorizationHeaderForToken,
@@ -5821,6 +5836,7 @@ export {
   exchangeMcpAuthorizationCode,
   listMcp,
   manifestConfigHash,
+  negotiateProtocolVersion,
   parseAuthorizationServerMetadata,
   parseGetPromptResult,
   parseListPromptsResult,

package/dist/server.d.ts

@@ -93,13 +93,17 @@ export declare class MCPServer {
      * tools are written against the schema they declared.
      *
      * SCOPE: `validateAgainstSchema` is the shared validator that also gates the
-     * agent's own tool executor. It checks `type`, `enum`, and `required`, and
-     * recurses through `properties`/`items` — it does NOT check
-     * `additionalProperties: false`, numeric bounds, or string lengths. So those
-     * keywords stay advisory here. Teaching the shared validator about them
-     * would change what the agent accepts on every tool call in the product,
-     * which is a deliberate decision that does not belong inside a transport
-     * fix; it is tracked separately.
+     * agent's own tool executor. It checks `type`, `enum`, `required`, recurses
+     * through `properties`/`items`, enforces numeric bounds
+     * (`minimum`/`maximum`), rejects unknown keys on strict-closed objects
+     * (`additionalProperties: false`), validates the `additionalProperties`
+     * subschema form against unknown-key values, applies `patternProperties`
+     * to matching keys, enforces string lengths (`minLength`/`maxLength`) and
+     * `pattern`, array lengths (`minItems`/`maxItems`/`uniqueItems`), and the
+     * combinators `allOf`/`anyOf`/`oneOf` (all landed 2026-09-11). Still
+     * advisory per the 2026-09-11 usage survey: `const` and `$ref` — declared
+     * only in the techstack rulebook, which validates with its own
+     * `validateRulebook`, not this validator.
      *
      * Unknown tool names are left alone — the host owns that error, and
      * answering "no such tool" here would fork the message for no benefit.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wrongstack/mcp",
-  "version": "1.0.3",
+  "version": "1.0.5",
   "license": "MIT",
   "description": "WrongStack Model Context Protocol client and registry: stdio, SSE, and streamable HTTP transports.",
   "repository": {
@@ -26,7 +26,7 @@
     "!dist/**/*.map"
   ],
   "dependencies": {
-    "@wrongstack/core": "1.0.3",
+    "@wrongstack/core": "1.0.5",
     "undici": "^8.10.0"
   },
   "devDependencies": {