@clipform/mcp-server 2.10.2 → 2.10.3

package/dist/index.js

@@ -2,10 +2,10 @@
 import {
   JSONRPCMessageSchema,
   createServer
-} from "./chunk-NCWQ42GI.js";
-import "./chunk-4QF4KGPE.js";
-import "./chunk-UBJ7CZL2.js";
-import "./chunk-IL26A4IN.js";
+} from "./chunk-ZOBK6CK7.js";
+import "./chunk-QZO6MGNN.js";
+import "./chunk-A5RVUIGS.js";
+import "./chunk-O35IVA4L.js";
 import "./chunk-ENHVQDSI.js";
 import {
   setMcpVersion

package/dist/instrument.d.ts

@@ -12,9 +12,21 @@ declare function getMcpAnalyticsClient(): McpAnalyticsClient | null;
  * Pulled out so the options object is unit-testable without standing up the
  * raw-HTTP handler.
  */
+interface InstrumentServerOptions {
+    /**
+     * Inject PostHog's `get_more_tools` virtual tool (default true). Off for
+     * the Claude Connectors Directory surface (#3681): the reviewer's tool
+     * scan sees every listed tool, and a third-party virtual tool whose
+     * description nudges the model to call it - and whose only input is a
+     * free-text description of the user's goal - reads as both a
+     * prompt-injection pattern and conversation-data collection under the
+     * directory policy. The bare endpoint keeps it for the mcp-miner sweep.
+     */
+    reportMissing?: boolean;
+}
 declare function buildInstrumentOptions(mcpAuth: {
     user_id?: string;
-} | null): MCPAnalyticsOptions;
+} | null, opts?: InstrumentServerOptions): MCPAnalyticsOptions;
 /**
  * Wraps the per-request/per-connection server with PostHog MCP analytics
  * (#3408, extended in-process #3432), additively - `mcp_request`/`$exception`
@@ -25,6 +37,6 @@ declare function buildInstrumentOptions(mcpAuth: {
  */
 declare function instrumentServer(server: unknown, posthogClient: McpAnalyticsClient | null, mcpAuth: {
     user_id?: string;
-} | null): void;
+} | null, opts?: InstrumentServerOptions): void;
 
-export { buildInstrumentOptions, getMcpAnalyticsClient, instrumentServer, setMcpAnalyticsClient };
+export { type InstrumentServerOptions, buildInstrumentOptions, getMcpAnalyticsClient, instrumentServer, setMcpAnalyticsClient };

package/dist/instrument.js

@@ -5236,7 +5236,7 @@ function setMcpAnalyticsClient(client) {
 function getMcpAnalyticsClient() {
   return installedClient;
 }
-function buildInstrumentOptions(mcpAuth) {
+function buildInstrumentOptions(mcpAuth, opts = {}) {
   return {
     context: {
       description: "Describe the user's underlying goal in one sentence - not the tool you're calling."
@@ -5263,13 +5263,13 @@ function buildInstrumentOptions(mcpAuth) {
     // tool covers. Injected by the wrapper only - never touches
     // packages/mcp-server's own catalog, so it does not trip the MCP
     // parity/catalog tests.
-    reportMissing: true
+    reportMissing: opts.reportMissing ?? true
   };
 }
-function instrumentServer(server, posthogClient, mcpAuth) {
+function instrumentServer(server, posthogClient, mcpAuth, opts = {}) {
   if (!posthogClient) return;
   try {
-    instrument(server, posthogClient, buildInstrumentOptions(mcpAuth));
+    instrument(server, posthogClient, buildInstrumentOptions(mcpAuth, opts));
   } catch (err) {
     console.error("[mcp] Failed to instrument server for PostHog MCP analytics:", err);
   }