ai-capability-framework 1.1.1 → 1.1.2

package/CHANGELOG.md

@@ -4,6 +4,20 @@ All notable public changes to AI Capability Framework are documented here.
 
 ## Unreleased
 
+## 1.1.2 - 2026-10-26
+
+- Cleared the full development and optional-SDK dependency advisory backlog with
+  targeted compatible updates, including MCP/HTTP, test, documentation, source-map and
+  compression dependencies. Full-tree audits now accompany production audits.
+- Raised the optional MCP SDK minimum to 1.32.0 and tested 1.32.0 and 1.32.2 through
+  actual in-memory SDK clients. Corrected the private SDK bridge to convert JSON schemas
+  into SDK-supported schemas and describe the returned runtime envelope. Authorization,
+  approval requirements and commit exclusion are unchanged.
+- Preserved the 1.1.1 Zod and URI fixes. Existing consumer lockfiles need their own
+  targeted update and audit; see
+  [security update instructions](SECURITY.md#dependency-security-updates).
+  Lexical/native discovery still requires no optional SDK or model for retrieval.
+
 ## 1.1.1 - 2026-10-26
 
 - Updated locked `fast-uri` to 3.1.9 and Zod to 4.6.7. The optional Zod peer now

package/SECURITY.md

@@ -43,6 +43,11 @@ redacted or removed to protect users.
 
 ## Dependency Security Updates
 
+Version 1.1.2 updates the full repository dependency tree, including development tools
+and optional MCP/HTTP integrations. The optional MCP SDK now requires 1.32.0 or newer;
+the repository tests 1.32.0 and locks 1.32.2. Full and production audits run for both
+packages. The dependency updates preserve the existing runtime and discovery contracts.
+
 Version 1.1.1 raises the optional Zod minimum to 4.6.6 and updates the repository's
 locked Zod to 4.6.7 and `fast-uri` to 3.1.9. Zod's collection-validation issue can
 consume excessive memory; the `fast-uri` advisories concern URI normalization and
@@ -54,10 +59,10 @@ Publishing a framework patch does not rewrite an application's existing lockfile
 and verify your application dependencies:
 
 ```sh
-npm install ai-capability-framework@1.1.1
+npm install ai-capability-framework@1.1.2
 npm update fast-uri
 npm ls fast-uri zod
-npm audit --omit=dev
+npm audit
 ```
 
 If your application already uses Zod, also update it:
@@ -66,6 +71,22 @@ If your application already uses Zod, also update it:
 npm install zod@^4.6.6
 ```
 
+If your application uses MCP, update its existing SDK and compatible HTTP dependency
+resolutions, then inspect every nested resolution:
+
+```sh
+npm install @modelcontextprotocol/sdk@^1.32.2
+npm update proxy-addr hono @hono/node-server ip-address body-parser qs
+npm ls @modelcontextprotocol/sdk proxy-addr hono @hono/node-server ip-address body-parser qs
+npm audit
+```
+
+Verify that no old nested resolutions remain. Relevant security floors are `proxy-addr`
+2.0.8, Hono 4.13.11, Hono Node adapter 1.19.15, `ip-address` 10.7.4, `body-parser` 2.4.0
+and `qs` 6.16.1. A newer compatible parent may be required when a parent pins an
+affected version exactly. Keep host authentication, trusted-proxy configuration and
+request limits explicit; these updates do not configure them.
+
 Then repeat the dependency listing, audit and application tests. `npm update fast-uri`
 selects a compatible patched release within the installed dependency ranges; for the
 framework's current Ajv resolution this is 3.1.9. Do not use a forced major upgrade or

package/dist/mcp-server/sdk.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"sdk.d.ts","sourceRoot":"","sources":["../../src/mcp-server/sdk.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAEV,2BAA2B,EAC3B,0BAA0B,EAC3B,MAAM,YAAY,CAAC;AAEpB,wBAAsB,oBAAoB,CACxC,OAAO,EAAE,2BAA2B,GACnC,OAAO,CAAC,0BAA0B,CAAC,CA8BrC"}
+{"version":3,"file":"sdk.d.ts","sourceRoot":"","sources":["../../src/mcp-server/sdk.ts"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAEV,2BAA2B,EAC3B,0BAA0B,EAC3B,MAAM,YAAY,CAAC;AAEpB,wBAAsB,oBAAoB,CACxC,OAAO,EAAE,2BAA2B,GACnC,OAAO,CAAC,0BAA0B,CAAC,CAuCrC"}

package/dist/mcp-server/sdk.js

@@ -1,8 +1,18 @@
+import { loadOptionalProviderDependency } from "../providers/shared/optional-dependency.js";
 export async function registerAicfMcpTools(options) {
     const server = asMcpSdkServer(options.mcpServer);
     const list = await options.aicfServer.listTools(options.request ?? {});
+    const convertSchema = isProtocolBackedServer(options.mcpServer)
+        ? (await loadOptionalProviderDependency({
+            dependencyName: "zod",
+            provider: "mcp"
+        })).fromJSONSchema
+        : undefined;
+    // Convert the complete list before registration so unsupported schemas cannot
+    // leave a partially registered SDK server. Structural host adapters keep JSON Schema.
+    const configs = list.tools.map((tool) => toolConfig(tool, convertSchema));
     const toolNames = [];
-    for (const tool of list.tools) {
+    for (const [index, tool] of list.tools.entries()) {
         const handler = async (args, extra) => {
             return options.aicfServer.callTool({
                 ...(isRecord(options.request) ? options.request : {}),
@@ -15,7 +25,7 @@ export async function registerAicfMcpTools(options) {
             });
         };
         if (server.registerTool) {
-            server.registerTool(tool.name, toolConfig(tool), handler);
+            server.registerTool(tool.name, configs[index], handler);
         }
         else if (server.tool) {
             server.tool(tool.name, tool.description, tool.inputSchema, handler);
@@ -27,16 +37,39 @@ export async function registerAicfMcpTools(options) {
         toolNames
     };
 }
-function toolConfig(tool) {
+function toolConfig(tool, convertSchema) {
     return {
         _meta: tool._meta,
         annotations: tool.annotations,
         description: tool.description,
-        inputSchema: tool.inputSchema,
-        outputSchema: tool.outputSchema,
+        inputSchema: convertSchema ? convertSchema(tool.inputSchema) : tool.inputSchema,
+        // MCP structuredContent contains the runtime envelope, whose data is the
+        // manifest output. Validate that wire shape rather than the unwrapped data.
+        outputSchema: convertSchema && tool.outputSchema ? convertSchema({
+            type: "object",
+            properties: {
+                schemaVersion: { const: "1.0" },
+                capabilityId: { type: "string" },
+                capabilityVersion: { type: "string" },
+                operation: { enum: ["read", "prepare"] },
+                requestId: { type: "string" },
+                runId: { type: "string" },
+                status: { enum: ["success", "prepared", "approval_required", "denied", "failed", "unavailable", "validation_error"] },
+                data: tool.outputSchema
+            },
+            // Protocol errors use a minimal envelope without capability data or identity.
+            // The executor still validates successful data against the manifest schema.
+            required: ["schemaVersion", "status"],
+            additionalProperties: true
+        }) : tool.outputSchema,
         title: tool.title
     };
 }
+function isProtocolBackedServer(server) {
+    return isRecord(server) && isRecord(server.server)
+        && typeof server.server.setRequestHandler === "function"
+        && typeof server.connect === "function";
+}
 function asMcpSdkServer(server) {
     if (!isRecord(server)) {
         throw new Error("MCP SDK server must be an object.");

package/docs/mcp-server-runtime.md

@@ -66,6 +66,14 @@ remain authoritative.
 caller-provided MCP SDK server object that exposes `registerTool()` or `tool()`. It does
 not import MCP transports or create a long-running process.
 
+Use MCP SDK 1.32.0 or newer; 1.32.0 and 1.32.2 are tested with actual in-memory SDK
+clients. The helper converts JSON schemas for SDK registration and returns the runtime
+envelope as structured content. Registration captures a tool-list snapshot; refresh
+registration when the host changes scopes. Every call still rechecks current
+authorization, so an old registration cannot bypass a revoked permission. Refresh
+existing consumer lockfiles as described in the
+[security policy](../SECURITY.md#dependency-security-updates).
+
 ```ts
 await registerAicfMcpTools({
   aicfServer,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ai-capability-framework",
-  "version": "1.1.1",
+  "version": "1.1.2",
   "private": false,
   "description": "Provider-agnostic AI capability contracts, runtime controls, evals, and model/provider adapters.",
   "license": "MIT",
@@ -330,7 +330,7 @@
     "@google/genai": ">=2.8.0",
     "@langchain/core": ">=1.1.0 <2",
     "@langfuse/client": ">=5.4.1",
-    "@modelcontextprotocol/sdk": ">=1.29.0",
+    "@modelcontextprotocol/sdk": ">=1.32.0",
     "@openai/agents": ">=0.11.6",
     "@opentelemetry/api": ">=1.9.1",
     "ai": ">=6.0.0",
@@ -402,14 +402,14 @@
     "@aws-sdk/client-kms": "^3.1061.0",
     "@aws-sdk/client-sfn": "^3.1061.0",
     "@aws-sdk/lib-dynamodb": "^3.1061.0",
-    "@modelcontextprotocol/sdk": "^1.29.0",
+    "@modelcontextprotocol/sdk": "^1.32.2",
     "@openai/agents": "^0.11.6",
     "@types/node": "^24.12.4",
     "json-schema-to-typescript": "^15.0.4",
     "prettier": "^3.8.3",
     "typedoc": "^0.28.19",
     "typescript": "^6.0.3",
-    "vitest": "^4.1.8",
+    "vitest": "^4.1.12",
     "zod": "^4.6.6"
   }
 }