github · mongodb-mcp-server83cc14597676

Evidence

import { type StreamableHTTPServerTransport } from "@modelcontextprotocol/sdk/server/streamableHttp.js";

import { isInitializeRequest } from "@modelcontextprotocol/sdk/types.js";

import express from "express";

import { LogId } from "../common/logging/loggingDefinitions.js";

import { getRandomUUID } from "../helpers/getRandomUUID.js";

import {

    type UserConfig,

    type ISessionStore,

    type Metrics,

    type DefaultMetrics,

    type Server,

    type LoggerBase,

} from "../lib.js";

import { 

Remediation

Apply auth middleware at the route or router level: - Express / Fastify / Koa: `passport.authenticate(...)`, `requireAuth`, `verifyToken`, or an equivalent JWT middleware applied via `router.use(authMw)` or as a per-route handler. - FastAPI: `Depends(get_current_user)`, `OAuth2PasswordBearer`, `HTTPBearer`, or `verify_jwt` dependency. - Flask: `@login_required`, `@auth_required`, `@jwt_required`, or call `verify_jwt_in_request()` in the handler. Mounting MCP behind a s

Remediation

Typosquat: verify you meant the popular package. If so, correct the spelling; if you truly intended the less-common name, suppress with an inline waiver. Stale release: check whether the package has a maintained fork or successor. If no patched release exists, vendor the code or migrate to an active alternative before the unmaintained code accrues unfixed CVEs.

Evidence

});

await runner.start();

console.log(

  `MongoDB MCP Server running with role-based request overrides at ${runner.serverAddress}`

);

```

### Use Case 3: Adding Custom Tools

Remediation

Strip C0/C1 control codes before printing user-controlled values. Python: re.sub(r"[\x00-\x08\x0b-\x1f\x7f]", "", s). Prefer a structured logger (json/logfmt) over raw print to stdout.

Evidence

`Setup complete! You can now use the MongoDB MCP Server in ${displayName}. You will probably need to restart your application to see the changes.\n`

        )

    );

    console.log("Try a query to get started:\n");

    console.log(availablePrompts.join("\n"));

    printNewLine();

};

Remediation

Strip C0/C1 control codes before printing user-controlled values. Python: re.sub(r"[\x00-\x08\x0b-\x1f\x7f]", "", s). Prefer a structured logger (json/logfmt) over raw print to stdout.

Evidence

// You can also access payload.attributes for additional context

    if (payload.attributes) {

      console.log("  Attributes:", JSON.stringify(payload.attributes));

    }

  }

}

Remediation

Strip C0/C1 control codes before printing user-controlled values. Python: re.sub(r"[\x00-\x08\x0b-\x1f\x7f]", "", s). Prefer a structured logger (json/logfmt) over raw print to stdout.

Evidence

private autoEmbedFieldSchema = z

        .object({

            type: z.literal("autoEmbed"),

            path: z.string().describe(

                `\

Name of the field containing the source text from which embeddings will be automatically generated by MongoDB. \

This should be the text field itself, NOT a separate embeddings field containing the vector embeddings. \

Remediation

Shape the schema to the tool's actual intent: - Zod: chain `.enum([...])`, `.regex(/.../)`, or `.max(n)`; prefer `z.enum([...])` or `z.literal(...)` when the value set is small. - Pydantic: use `Literal["a", "b"]` or `Field(max_length=..., pattern=r"...")`. - JSON Schema: add `"enum"`, `"pattern"`, or `"maxLength"` to the property. An overbroad schema is an "overpowered tool" — the model has nothing to prevent it from calling the tool with input far beyond what the tool's prose contract

Evidence

* @example

     * ```typescript

     * public argsShape = {

     *   query: z.string().describe("The search query"),

     *   limit: z.number().optional().describe("Maximum results to return"),

     * };

     * ```

Remediation

Shape the schema to the tool's actual intent: - Zod: chain `.enum([...])`, `.regex(/.../)`, or `.max(n)`; prefer `z.enum([...])` or `z.literal(...)` when the value set is small. - Pydantic: use `Literal["a", "b"]` or `Field(max_length=..., pattern=r"...")`. - JSON Schema: add `"enum"`, `"pattern"`, or `"maxLength"` to the property. An overbroad schema is an "overpowered tool" — the model has nothing to prevent it from calling the tool with input far beyond what the tool's prose contract

Evidence

*   // Required abstract properties

 *   public description = "My custom tool description";

 *   public argsShape = {

 *     query: z.string().describe("The query parameter"),

 *   };

 *

 *   // Required abstract method: implement the tool's logic

Remediation

Shape the schema to the tool's actual intent: - Zod: chain `.enum([...])`, `.regex(/.../)`, or `.max(n)`; prefer `z.enum([...])` or `z.literal(...)` when the value set is small. - Pydantic: use `Literal["a", "b"]` or `Field(max_length=..., pattern=r"...")`. - JSON Schema: add `"enum"`, `"pattern"`, or `"maxLength"` to the property. An overbroad schema is an "overpowered tool" — the model has nothing to prevent it from calling the tool with input far beyond what the tool's prose contract

Evidence

.optional()

            .describe("AWS config for S3, Kinesis, and Lambda connections."),

        // Https

        url: z.string().optional().describe("Webhook URL for Https connections."),

        headers: z.record(z.string(), z.string()).optional().describe("HTTP headers for Https connections."),

        // SchemaRegistry

        provider: z

Remediation

Shape the schema to the tool's actual intent: - Zod: chain `.enum([...])`, `.regex(/.../)`, or `.max(n)`; prefer `z.enum([...])` or `z.literal(...)` when the value set is small. - Pydantic: use `Literal["a", "b"]` or `Field(max_length=..., pattern=r"...")`. - JSON Schema: add `"enum"`, `"pattern"`, or `"maxLength"` to the property. An overbroad schema is an "overpowered tool" — the model has nothing to prevent it from calling the tool with input far beyond what the tool's prose contract

Evidence

private vectorFieldSchema = z

        .object({

            type: z.literal("vector"),

            path: z.string().describe(

                `\

Name of the field containing vector embeddings as arrays of numbers. This must be a dedicated embeddings field, separate from any source text field, if any. \

For nested fields, use dot notation to specify path to embedded fields.\

Remediation

Shape the schema to the tool's actual intent: - Zod: chain `.enum([...])`, `.regex(/.../)`, or `.max(n)`; prefer `z.enum([...])` or `z.literal(...)` when the value set is small. - Pydantic: use `Literal["a", "b"]` or `Field(max_length=..., pattern=r"...")`. - JSON Schema: add `"enum"`, `"pattern"`, or `"maxLength"` to the property. An overbroad schema is an "overpowered tool" — the model has nothing to prevent it from calling the tool with input far beyond what the tool's prose contract

Evidence

*   // Required abstract properties

 *   public description = "My custom tool description";

 *   public argsShape = {

 *     query: z.string().describe("The query parameter"),

 *   };

 *

 *   // Required abstract method: implement the tool's logic

Remediation

Shape the schema to the tool's actual intent: - Zod: chain `.enum([...])`, `.regex(/.../)`, or `.max(n)`; prefer `z.enum([...])` or `z.literal(...)` when the value set is small. - Pydantic: use `Literal["a", "b"]` or `Field(max_length=..., pattern=r"...")`. - JSON Schema: add `"enum"`, `"pattern"`, or `"maxLength"` to the property. An overbroad schema is an "overpowered tool" — the model has nothing to prevent it from calling the tool with input far beyond what the tool's prose contract

Evidence

"start": "node dist/index.js --transport http --loggers 'stderr, mcp'",

    "start:stdio": "node dist/index.js --transport stdio --loggers 'stderr, mcp'",

    "start:setup": "pnpm run build && node dist/index.js setup",

    "prepare": "husky && pnpm run build",

    "build:update-package-version": "tsx scripts/updatePackageVersion.ts",

    "build:esm": "tsc --project tsconfig.esm.json",

    "build:cjs": "tsc --project tsconfig.cjs.json",

Remediation

Prefer libraries that do not require install-time code execution: - Drop `postinstall`/`preinstall`/`prepare` scripts if the work can happen at runtime or build-time instead. - Ship pre-built native binaries rather than compiling via a custom `cmdclass` or `build_ext` override. - For Dockerfiles: replace `RUN curl … | sh` with a pinned download + checksum verification + explicit `RUN` of a named script. - If the hook is unavoidable, document exactly what it does so downstream reviewers

Evidence

- uses: actions/checkout@v6

        with:

          persist-credentials: false

      - uses: pnpm/action-setup@v5

      - uses: actions/setup-node@v6

        with:

          node-version-file: package.json

Remediation

Pin every `uses:` to a 40-character commit SHA. Trailing comment with the version helps reviewers: `uses: actions/checkout@8e5e7e5ab8b370d6c329ec480221332ada57f0ab # v4.1.1` Automate the migration with `pinact` (https://github.com/suzuki-shunsuke/pinact) or `ratchet` (https://github.com/sethvargo/ratchet). Add a `pinact run --check` pre-commit hook so future PRs stay pinned. Re-pin when the action releases a new version — Dependabot can do this automatically with `version-update-strategy: inc

Evidence

RELEASE_CHANNEL: ${{ steps.npm-tag.outputs.RELEASE_CHANNEL }}

    steps:

      - uses: GitHubSecurityLab/actions-permissions/monitor@v1

      - uses: actions/checkout@v6

        with:

          fetch-depth: 0

      - name: Get version

Remediation

Pin every `uses:` to a 40-character commit SHA. Trailing comment with the version helps reviewers: `uses: actions/checkout@8e5e7e5ab8b370d6c329ec480221332ada57f0ab # v4.1.1` Automate the migration with `pinact` (https://github.com/suzuki-shunsuke/pinact) or `ratchet` (https://github.com/sethvargo/ratchet). Add a `pinact run --check` pre-commit hook so future PRs stay pinned. Re-pin when the action releases a new version — Dependabot can do this automatically with `version-update-strategy: inc

Evidence

with:

          set-host: true

      - uses: pnpm/action-setup@v5

      - uses: actions/setup-node@v6

        with:

          node-version-file: package.json

          cache: "pnpm"

Remediation

Pin every `uses:` to a 40-character commit SHA. Trailing comment with the version helps reviewers: `uses: actions/checkout@8e5e7e5ab8b370d6c329ec480221332ada57f0ab # v4.1.1` Automate the migration with `pinact` (https://github.com/suzuki-shunsuke/pinact) or `ratchet` (https://github.com/sethvargo/ratchet). Add a `pinact run --check` pre-commit hook so future PRs stay pinned. Re-pin when the action releases a new version — Dependabot can do this automatically with `version-update-strategy: inc

Evidence

with:

          config: ${{ vars.PERMISSIONS_CONFIG }}

      - name: Check out code

        uses: actions/checkout@v6

        with:

          persist-credentials: false

      - name: Get date

Remediation

Pin every `uses:` to a 40-character commit SHA. Trailing comment with the version helps reviewers: `uses: actions/checkout@8e5e7e5ab8b370d6c329ec480221332ada57f0ab # v4.1.1` Automate the migration with `pinact` (https://github.com/suzuki-shunsuke/pinact) or `ratchet` (https://github.com/sethvargo/ratchet). Add a `pinact run --check` pre-commit hook so future PRs stay pinned. Re-pin when the action releases a new version — Dependabot can do this automatically with `version-update-strategy: inc