postman-mcp@3.0.1
VERIFIED· not startedPublisher claims: "An MCP server for Claude Code that generates and updates Postman requests from your API code, with a diff before every write." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
POSTMAN_API_KEY- Where it talks to
- getpostman.com (its own)
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard. It asks for POSTMAN_API_KEY and talks to getpostman.com. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-15 and scored it 86/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
subprocess.run(args, cwd=project, env=run_env, capture_output=True, check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# postman/config.json and postman/sync/ are meant to be committed and reviewed;Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.Each ``examples/<app>/expected-output/*.item.json`` is the real parser + engine outputFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.``subprocess.run(..., capture_output=True, timeout=X)`` is not reliably boundedFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.proc = subprocess.Popen(cmd, cwd=str(cwd), stdout=out_f, stderr=err_f)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run(args, cwd=cwd, check=True, capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.raise RuntimeError("simulated kill right after the first checkpoint")Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.The bug this guards against: subprocess.run(..., capture_output=True,Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for postman-mcp@3.0.1 as of 2 h ago. This is the package itself, not its dependencies.