Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Recent critical change

CVE-2026-33937 affects this package (2 Aug 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security66
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
  • Runs a script at install time (preinstall) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does. View diagnostics → Partial
  • 111 of 226 dependencies flagged as unhealthy (4 deprecated). View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to postmanlabs/postman-mcp-server). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 10 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the Postman MCP Server server?

Postman MCP Server runs locally as an npm package, launched with npx -y @postman/postman-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @postman/postman-mcp-server

# add to Claude Code
claude mcp add com-postman-postman-mcp-server -- npx -y @postman/postman-mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "com-postman-postman-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@postman/postman-mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-postman-postman-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@postman/postman-mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-postman-postman-mcp-server -- npx -y @postman/postman-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-postman-postman-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@postman/postman-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-postman-postman-mcp-server --command npx --arg -y --arg @postman/postman-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  com-postman-postman-mcp-server:
    command: "npx"
    args: ["-y", "@postman/postman-mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-postman-postman-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@postman/postman-mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-postman-postman-mcp-server -t stdio -c npx -a -y @postman/postman-mcp-server
// mcp.json
{
  "mcpServers": {
    "com-postman-postman-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@postman/postman-mcp-server"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 10 Sept 26 0
    • Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan. security
    • Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake. functional
    • Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess. functional
    • Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess. functional
  • 9 Sept 26 0
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 2.12.2 → 2.12.3 functional
  • 8 Sept 26 0
    • Package version: 2.12.0 → 2.12.2 functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 20 Aug 26 0
    • Security disclosure: fail → pass functional
  • 18 Aug 26 0
    • Package version: 2.11.2 → 2.12.0 functional
  • 12 Aug 26 0
    • Security disclosure: unverified → fail functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/@postman/postman-mcp-server@2.12.3

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo postmanlabs/postman-mcp-server
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/postmanlabs/postman-mcp-server/.github/workflows/pkg-release.yml@refs/tags/v2.12.3
Rekor log index 2766421102
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:7b57a285afaecff2425befd8c1f1e97f68136316553b2544932cbaa6beb3bf077fde9819bf9615ab336cb9afb7e02a6f8addc68e128c27d93f7e080a4

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
preinstall unreviewed npx only-allow pnpm

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 29 findings
ID CVE Severity Vector Fix available
GHSA-qxc2-j82w-r537 CVE-2026-73231 high CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H yes
GHSA-8cw4-87c7-c6xx CVE-2026-85063 medium yes
GHSA-25h7-pfq9-p65f CVE-2026-32141 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-rf6f-7fwh-wjgh CVE-2026-33228 high yes
GHSA-2qvq-rjwj-gvw9 CVE-2026-33916 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N yes
GHSA-2w6w-674q-4c4q CVE-2026-33937 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-3mfm-83xf-c92r CVE-2026-33938 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-442j-39wm-28r2 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N yes
GHSA-7rx3-28cr-v5wh medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-9cx6-37pm-9jff CVE-2026-33939 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-xhpv-hc6g-r9c6 CVE-2026-33940 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-xjpj-3mr7-gcpf CVE-2026-33941 high CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H yes
GHSA-hhhv-q57g-882q CVE-2024-28176 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-f23m-r3pf-42rh CVE-2025-13465 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-r5fr-rjxr-66jc CVE-2021-23337 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-xxjr-mmjv-4gpg CVE-2025-13465 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-2328-f5f3-gj25 CVE-2026-33896 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-554w-wpv2-vw27 CVE-2025-66031 high yes
GHSA-5gfm-wpxj-wjgq CVE-2025-12816 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N yes
GHSA-5m6q-g25r-mvwx CVE-2026-33891 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-65ch-62r8-g69g CVE-2025-66030 medium yes
GHSA-ppp5-5v6c-4jwp CVE-2026-33894 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-q67f-28xg-22rw CVE-2026-33895 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-4mjr-xmp4-gh2g CVE-2026-82417 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-q8mj-m7cp-5q26 CVE-2026-8723 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-x5fp-wj9c-mxmx CVE-2026-82562 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-6rw7-vpxm-498p CVE-2025-15284 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-qpx9-hpmf-5gmw CVE-2026-27601 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 226 packages
Packages resolved 226
Deprecated 4
Stale 108
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the Postman MCP Server server?

Postman MCP Server is listed in the public MCP registry as com.postman/postman-mcp-server. Give your AI agents trusted access to the full Postman platform. This page covers its npm package (@postman/postman-mcp-server).

Is the Postman MCP Server server still maintained?

Postman MCP Server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Postman MCP Server server under?

Postman MCP Server declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.