Postman MCP Server

Postman MCP Server — connect AI agents (Claude Code, Cursor, VS Code Copilot, Gemini CLI) to your Postman collections, OpenAPI specs, and environments via Model Context Protocol (MCP)

MCP Servers TypeScript Listed Apache-2.0

Is Postman MCP Server safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.0 / 10
Provenance Attested
Signed commits 34%
Last push 4d ago
Compare Postman MCP Server
Suggest a correction

In detail: Postman MCP Server scores 78.7/100 (Grade B), ranked #161 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.0/10; 34% of recent commits are signed; last pushed 2026-09-22. Every point is earned from checkable signals — never paid placement. How scoring works →

How Postman MCP Server compares in MCP Servers

  1. #85 Godot MCP Runtime 78.8 +0.1
  2. #86 Anki MCP Server 78.7 ±0
  3. #87 Postman MCP Server 78.7 this agent
  4. #88 Ckan MCP Server 78.7 ±0
  5. #89 build123d MCP 78.5 −0.2

Bars show each HVTrust score; the tick marks Postman MCP Server’s 78.7.

Where the 78.7 comes from

HVTrust dimensions vs the MCP Servers average

78.7 / 100 · 100.0% confidence

Postman MCP Server MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
15.5 / 25
5.2 above avg 10.3
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
0.6 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
16.5 / 20
4.4 above avg 12.1
AdoptionLog-scaled stars · package downloads
10.9 / 20
3.7 above avg 7.2

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → B
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.0/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
63.7
Activity sub-score · out of 100
#87

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed 4 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
317
Forks
88
Last Push
2026-09-22
4 days ago
Commits (4 wk)
15
Downloads (7d)
4,331
npm
HN mentions (30d)
—
Open Issues
4
Rank Change
▼1
was #160

Analysis

Activity Inputs

63.7 / 100
StarsRepository reach
15.0 / 30
FreshnessLast push recency
24.4 / 25
ActivityRecent commits
15.0 / 25
CommunityFork signal
9.1 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
5.0 / 10
OpenSSF Scorecard · scanned Sep 24, 2026
Signed Commits
34%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 3
SAST 0
Security-Policy 10
Signed-Releases 0
Token-Permissions 9
Vulnerabilities 0

Common questions about Postman MCP Server

Public supply-chain signals for Postman MCP Server are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Postman MCP Server carries less obvious unverified-evidence risk than projects with thin signals.
Does Postman MCP Server publish package provenance?
Yes. Postman MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Postman MCP Server have an OpenSSF Scorecard?
Postman MCP Server has an OpenSSF Scorecard score of 5.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Postman MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 4 day(s).
What license does Postman MCP Server use?
Postman MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Postman MCP Server's commits signed?
34% of the last 100 commits to Postman MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Postman MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Postman MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Postman MCP Server?

For maintainers

HVTrust scores Postman MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 17HVTrust 4Listed 2Grade 2Scorecard 1Score 1Delisted 1Provenance 1MCP 1
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 618 spots (#773 → #155)
2026-09-23
HVTrust Changed
HVTrust up 49.5pts (29.5 → 79.0)
2026-09-22
Newly Listed
First tracked at rank #773
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank dropped 10 spots (#153 → #163)
2026-09-17
Rank Moved
Rank rose 11 spots (#161 → #150)
2026-09-08
Rank Moved
Rank rose 79 spots (#237 → #158)
2026-09-08
HVTrust Changed
HVTrust up 4.8pts (73.5 → 78.3)
2026-09-08
Activity Score Changed
Activity score up 8pts (54 → 63)
2026-09-07
Rank Moved
Rank dropped 23 spots (#214 → #237)
2026-09-05
Rank Moved
Rank dropped 54 spots (#161 → #215)
2026-09-03
Grade Changed
Trust grade D → B
2026-09-03
Rank Moved
Rank rose 635 spots (#791 → #156)
2026-09-03
HVTrust Changed
HVTrust up 27.1pts (47.0 → 74.1)
2026-09-02
Rank Moved
Rank dropped 45 spots (#746 → #791)
2026-09-01
Rank Moved
Rank dropped 27 spots (#719 → #746)
2026-08-31
Rank Moved
Rank dropped 33 spots (#686 → #719)
2026-08-30
Rank Moved
Rank dropped 23 spots (#663 → #686)
2026-08-29
Scorecard Added
OSSF Scorecard: 4.6/10
2026-08-29
Rank Moved
Rank rose 102 spots (#765 → #663)
2026-08-29
HVTrust Changed
HVTrust up 6.4pts (40.8 → 47.2)
2026-08-28
Rank Moved
Rank dropped 28 spots (#737 → #765)
2026-08-27
Rank Moved
Rank dropped 23 spots (#714 → #737)
2026-08-26
Rank Moved
Rank dropped 98 spots (#616 → #714)
2026-08-16
Rank Moved
Rank dropped 11 spots (#601 → #612)
2026-08-10
Rank Moved
Rank dropped 22 spots (#576 → #598)
2026-08-08
Newly Listed
First tracked at rank #576

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 78.7 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/postman-mcp-server.svg)](https://hvtracker.net/agents/postman-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/postman-mcp-server"><img src="https://hvtracker.net/badge/postman-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON