MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

postman-mcp-server

Earlier Revision Publisher unverified Confidence: Good (0.85)

postman-mcp-server is an MCP server published by postman.com, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.

Does postman-mcp-server support the current MCP specification (2026-07-28)?

Not yet confirmed. postman-mcp-server is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.

Is postman-mcp-server a first-party (official) MCP server?

Undetermined. We have not verified the publisher relationship for postman-mcp-server (as of 2026-08-20).

How do I connect to postman-mcp-server?

postman-mcp-server is available via a hosted remote endpoint at https://mcp.postman.com/mcp, the package npm:@postman/postman-mcp-server, the official MCP Registry under com.postman/postman-mcp-server, the source repository at https://github.com/postmanlabs/postman-mcp-server. Authentication: oauth. Transports: streamable-http.

Does postman-mcp-server support MCP revision 2025-11-25?

Yes. postman-mcp-server supports MCP revision 2025-11-25 (checked 2026-08-20).

Does postman-mcp-server support MCP revision 2026-07-28?

No. postman-mcp-server was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).

When were postman-mcp-server's facts last verified?

2026-08-20. Each fact on this page links to the sources used to verify it.

A basic MCP server to operate on the Postman API.

Which MCP spec revisions does postman-mcp-server support?

postman-mcp-server has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.

Spec revision Status Last checked Evidence
MCP 2025-11-25 Supported Source
MCP 2026-07-28 Not supported Source

How widely adopted is postman-mcp-server?

Ranked #48 in The MCP 500 with Adoption Index 61.72 (snapshot , methodology v1).

Measurement Value Source
Official MCP Registry yes API ·
Docker MCP Catalog no API ·
npm downloads (weekly) 13,285 API ·
GitHub stars 314 API ·
GitHub forks 87 API ·
Last push 2026-09-09T07:33:33Z API ·
Repository archived no API ·

Repository and package signals for postman-mcp-server

Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.

Repository as of

Created
Open issues
5
Primary language
TypeScript
License (repository)
Apache-2.0
Continuous integration
Present
Tests
Present
Security policy
Present

Declared topics: agent, ai, ai-agents, api-testing, claude, claude-code, copilot, cursor, gemini, llm, mcp, mcp-server, model-context-protocol, postman, rest-api, vscode — author-declared on the repository, not our taxonomy.

Package (npm) as of

Latest version
2.12.0
Last published
First published
Releases
48
License (package)
Apache-2.0
Maintainers
3
Direct dependencies
6
Unpacked size
614 KB
Registry signature
Signed
Build provenance
Attested

How was this verified, and what are the sources?

Verified · method: sdk-protocol-constant · confidence 0.85 (Good).

  1. Official MCP Registry record for com.postman/postman-mcp-server at version 2.11.2 - lists remote endpoint https://mcp.postman.com/mcp and repository https://github.com/postmanlabs/postman-mcp-server - accessed
  2. Endpoint probe of https://mcp.postman.com/mcp - authorization required (HTTP 401, Bearer resource_metadata="https://mcp.postman.com/.well-know); capability set not observable without credentials - accessed
  3. npm registry metadata for @postman/postman-mcp-server at published version 2.12.0, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
  4. Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed