updated 2026-10-18 00:07 UTC

Paypal MCP Server

Repository
MCP Servers JavaScript Listed Apache-2.0

Is Paypal MCP Server safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.3 / 10
Provenance None
Signed commits 56%
Last push 355d ago
Compare Paypal MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Paypal MCP Server scores 38.5/100 (Grade D), ranked #1233 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.3/10; 56% of recent commits are signed; last pushed 2025-10-28. Every point is earned from checkable signals — never paid placement. How scoring works →

How Paypal MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Paypal MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/paypal/paypal-mcp-server, Apache-2.0, last pushed 2025-10-28. 56% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.3/10 (scanned Oct 16, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection6
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions9
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 6
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 0
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 9
    Vulnerabilities 10

  3. Published packages Not linked

    • npm @paypal/mcp No source link declared No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

Changes to this chain

  • 2026-08-31 OSSF Scorecard: 4.3/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Paypal MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Paypal MCP Server compares in MCP Servers

  1. #711 Patsnap Patent & Literature Search 38.9 +0.4
  2. #712 Terminal MCP Server 38.6 +0.1
  3. #713 Paypal MCP Server 38.5 this agent
  4. #714 Langcare MCP Fhir 38.5 ±0
  5. #715 Augments MCP Server 38.5 ±0

Bars show each HVTrust score; the tick marks Paypal MCP Server’s 38.5.

Where the 38.5 comes from

HVTrust dimensions vs the MCP Servers average

38.5 / 100 · 100.0% confidence

Paypal MCP Server MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.2 / 25
2.4 below avg 10.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.8 below avg 13.6
Transparency50% declared license · 50% OSSF Scorecard
12.2 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.2 below avg 12.2
AdoptionLog-scaled stars · package downloads
6.3 / 20
1.1 below avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 62 spots (#1256 → #1194)
2026-09-23
HVTrust Changed
HVTrust up 23.2pts (15.1 → 38.3)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.3/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Refresh maintenance signals The repo was last pushed 355 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Paypal MCP Server View MCP Servers Report missing data
12.9
Activity sub-score · out of 100
#713
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D 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-10-18 00:07 UTC · Repo last pushed 355 days ago — may be stale

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars
13
Forks
19
Last Push
2025-10-28
355 days ago
Commits (4 wk)
0
Downloads (7d)
499
npm
HN mentions (30d)
—
Open Issues
4
Rank Change
▼1
was #1232

Analysis

Activity Inputs

12.9 / 100
StarsRepository reach
6.9 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
6.0 / 20

Common questions about Paypal MCP Server

Public trust evidence for Paypal MCP Server is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Paypal MCP Server publish package provenance?
No published build provenance is currently detected for Paypal MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Paypal MCP Server have an OpenSSF Scorecard?
Paypal MCP Server has an OpenSSF Scorecard score of 4.3/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 Paypal MCP Server actively maintained?
Stale. The repository has not been pushed to in 355 days. Consider whether the project is still being maintained.
What license does Paypal MCP Server use?
Paypal MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Paypal MCP Server's commits signed?
55% of the last 100 commits to Paypal 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
Paypal 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
low confidence
Unknown
Package source metadata is missing or inconclusive
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 Paypal 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

Maintain Paypal MCP Server?

For maintainers

HVTrust scores Paypal 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 14HVTrust 3Listed 2Scorecard 1Delisted 1MCP 1
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 62 spots (#1256 → #1194)
2026-09-23
HVTrust Changed
HVTrust up 23.2pts (15.1 → 38.3)
2026-09-22
Newly Listed
First tracked at rank #1256
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-12
Rank Moved
Rank dropped 11 spots (#1171 → #1182)
2026-09-09
Rank Moved
Rank dropped 14 spots (#1158 → #1172)
2026-09-08
Rank Moved
Rank dropped 11 spots (#1147 → #1158)
2026-09-07
Rank Moved
Rank dropped 16 spots (#1131 → #1147)
2026-09-06
Rank Moved
Rank dropped 13 spots (#1118 → #1131)
2026-09-05
Rank Moved
Rank dropped 36 spots (#1082 → #1118)
2026-09-04
Rank Moved
Rank dropped 23 spots (#1059 → #1082)
2026-09-03
Rank Moved
Rank rose 171 spots (#1230 → #1059)
2026-09-03
HVTrust Changed
HVTrust up 15.0pts (23.6 → 38.6)
2026-09-02
Rank Moved
Rank dropped 36 spots (#1194 → #1230)
2026-09-01
Rank Moved
Rank dropped 38 spots (#1156 → #1194)
2026-08-31
Scorecard Added
OSSF Scorecard: 4.3/10
2026-08-31
Rank Moved
Rank rose 160 spots (#1316 → #1156)
2026-08-31
HVTrust Changed
HVTrust up 12.7pts (10.9 → 23.6)
2026-08-16
Rank Moved
Rank dropped 25 spots (#1280 → #1305)
2026-08-10
Rank Moved
Rank dropped 79 spots (#1201 → #1280)
2026-08-08
Newly Listed
First tracked at rank #1201
GitHub → npm: @paypal/mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 38.5 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/paypal-mcp-server.svg)](https://hvtracker.net/agents/paypal-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/paypal-mcp-server"><img src="https://hvtracker.net/badge/paypal-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.4 · Raw JSON