@ttoss/http-server-mcp 0.24.1 → 0.25.1

package/README.md

@@ -360,7 +360,7 @@ The `WWW-Authenticate: Bearer resource_metadata="…"` header is how MCP clients
 
 The two behaviors the [MCP authorization spec](https://spec.modelcontextprotocol.io/specification/2025-03-26/basic/authorization/) requires for client bootstrapping are built into the `auth` option, so you no longer need the hand-rolled middleware shown above:
 
-- **`publicMethods`** — JSON-RPC methods that bypass verification, read from the request body's `method` field. Defaults to `['initialize', 'tools/list']` so clients can discover the server before authenticating. Pass `[]` to require a token for every method, or a custom list to change the exempt set.
+- **`publicMethods`** — JSON-RPC methods that bypass verification, read from the request body's `method` field. Defaults to `['initialize', 'tools/list']` so clients can discover the server before authenticating. Pass `[]` to require a token for every method, or a custom list to change the exempt set. Leaving it unset serves the full tool catalogue — every tool name, description, and input schema — to unauthenticated callers, and logs a one-time warning explaining that and how to close it. Set `publicMethods` explicitly (even to the same default) to silence the warning.
 - **`resourceMetadataUrl`** — when set, a `401` responds with `WWW-Authenticate: Bearer resource_metadata="<resourceMetadataUrl>"` (RFC 9728) instead of a bare `Bearer`, pointing MCP clients at the protected-resource metadata document. When omitted, the header falls back to `Bearer`.
 
 ```typescript
@@ -871,6 +871,8 @@ expect(call.status).toBe(200);
 
 Use the default when token auth is handled outside the OAuth flow (Cognito, API keys, Bearer tokens). Set `publicMethods: []` only when you want OAuth clients to self-discover and authenticate before anything else.
 
+Leaving `publicMethods` unset also exposes the full tool catalogue (`tools/list`) to unauthenticated callers — a tool's name, description, and input schema can leak internal resource names and, for an OpenAPI-derived server, the shape of the whole underlying API. A one-time warning is logged when `auth` is configured without an explicit `publicMethods`, naming the exposure and how to close it. This default is a candidate to tighten to `['initialize']` in a future major; track the decision in [ttoss/ttoss#1176](https://github.com/ttoss/ttoss/issues/1176).
+
 ## AWS Lambda Deployment
 
 The default **stateless** mode (see [Stateless vs stateful mode](#stateless-vs-stateful-mode)) is built for serverless: a fresh transport is created per request, nothing is kept in memory between invocations, and responses are plain JSON (no SSE) — exactly the request/response shape API Gateway and Lambda Function URLs expect.

package/dist/index.cjs

@@ -531,6 +531,7 @@ var createMcpRouter = (server, options = {}) => {
   let authCheck;
   if (auth) {
     const verifyToken = buildVerifyToken(auth);
+    if (auth.publicMethods === void 0) console.warn(`[@ttoss/http-server-mcp] "auth" is configured but "publicMethods" was not set, so it defaults to ${JSON.stringify(DEFAULT_PUBLIC_METHODS)}. This means "tools/list" — the full tool catalogue, including names, descriptions, and input schemas — is served to unauthenticated callers. To require a token for "tools/list" too, set publicMethods: ['initialize']. To keep the current behaviour and silence this warning, set publicMethods: ${JSON.stringify(DEFAULT_PUBLIC_METHODS)} explicitly.`);
     const publicMethods = new Set(auth.publicMethods ?? DEFAULT_PUBLIC_METHODS);
     const verify = (0, _ttoss_http_server_auth.authMiddleware)({
       strategies: ["oauth"],

package/dist/index.d.cts

@@ -892,6 +892,10 @@ interface McpAuthOptions {
   requiredScopes?: string[];
   /**
    * JSON-RPC methods (read from `body.method`) that bypass verification.
+   * Leaving this unset serves `tools/list` — the full tool catalogue —
+   * to unauthenticated callers, and logs a one-time warning explaining how
+   * to close it. Set explicitly (even to the same default) to silence the
+   * warning; set to `['initialize']` to require a token for `tools/list` too.
    * @default ['initialize', 'tools/list']
    */
   publicMethods?: string[];

package/dist/index.d.mts

@@ -893,6 +893,10 @@ interface McpAuthOptions {
   requiredScopes?: string[];
   /**
    * JSON-RPC methods (read from `body.method`) that bypass verification.
+   * Leaving this unset serves `tools/list` — the full tool catalogue —
+   * to unauthenticated callers, and logs a one-time warning explaining how
+   * to close it. Set explicitly (even to the same default) to silence the
+   * warning; set to `['initialize']` to require a token for `tools/list` too.
    * @default ['initialize', 'tools/list']
    */
   publicMethods?: string[];

package/dist/index.mjs

@@ -528,6 +528,7 @@ var createMcpRouter = (server, options = {}) => {
   let authCheck;
   if (auth) {
     const verifyToken = buildVerifyToken(auth);
+    if (auth.publicMethods === void 0) console.warn(`[@ttoss/http-server-mcp] "auth" is configured but "publicMethods" was not set, so it defaults to ${JSON.stringify(DEFAULT_PUBLIC_METHODS)}. This means "tools/list" — the full tool catalogue, including names, descriptions, and input schemas — is served to unauthenticated callers. To require a token for "tools/list" too, set publicMethods: ['initialize']. To keep the current behaviour and silence this warning, set publicMethods: ${JSON.stringify(DEFAULT_PUBLIC_METHODS)} explicitly.`);
     const publicMethods = new Set(auth.publicMethods ?? DEFAULT_PUBLIC_METHODS);
     const verify = authMiddleware({
       strategies: ["oauth"],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ttoss/http-server-mcp",
-  "version": "0.24.1",
+  "version": "0.25.1",
   "description": "Model Context Protocol (MCP) server integration for @ttoss/http-server",
   "keywords": [
     "ai",
@@ -36,9 +36,9 @@
     "@modelcontextprotocol/node": "^2.0.0",
     "@modelcontextprotocol/server": "^2.0.0",
     "zod": "^4.4.3",
-    "@ttoss/auth-core": "^0.13.0",
-    "@ttoss/http-server-auth": "^0.6.0",
-    "@ttoss/http-server": "^0.7.1"
+    "@ttoss/http-server-auth": "^0.6.1",
+    "@ttoss/http-server": "^0.8.0",
+    "@ttoss/auth-core": "^0.13.0"
   },
   "devDependencies": {
     "@types/koa": "^3.0.3",