Postman MCP
Postman (Indian-founded, Bengaluru HQ) is used by 35M+ developers globally. MCP servers exposing API collections, environments, and request execution need visible trust boundaries — especially relevant for Indian dev ecosystem CI pipelines. Already evaluated at Safety Index #94.
N/A
Could not evaluate
Could not establish a plain stdio MCP session for target `postman-india-region`.
Command: npx -y @postman/postman-mcp-server
Diagnosis: The process exited or detached before MCP initialization completed.
Raw error: MCP error -32000: Connection closed
Likely causes:
- The package may expect extra startup arguments or environment variables.
- The package may not behave like a plain local-process stdio target under this invocation.
- The server may be crashing immediately and only leaving clues on stderr.
Next steps:
- Run the command manually and look for usage output, auth prompts, or crash text.
- Check whether the package expects a different transport or an app-oriented startup flow.
- Use the recent stderr lines below before assuming this is a harness bug.
Recent stderr:
- Invalid environment variables for Postman MCP server: { _errors: [], POSTMAN_API_KEY: { _errors: [ 'Required' ] } }
Check Results
0 pass
0 fail
0 partial
3 skipped
tools
Skipped
Skipped because startup failed before the MCP session initialized. See the failure diagnosis.
prompts
Skipped
Skipped because startup failed before the MCP session initialized. See the failure diagnosis.
resources
Skipped
Skipped because startup failed before the MCP session initialized. See the failure diagnosis.