updated 2026-10-11 12:08 UTC

Stripe Agent Toolkit

Repository Website

One-stop shop for building AI-powered products and businesses with Stripe.

MCP Servers TypeScript Listed MIT

Is Stripe Agent Toolkit safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.1 / 10
Provenance Attested
Signed commits 29%
Last push today
Advisories None known
Compare Stripe Agent Toolkit

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Stripe Agent Toolkit scores 84.6/100 (Grade A), ranked #95 of 1371 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 6.1/10; 29% of recent commits are signed; no published advisory affects its latest release (@stripe/agent-toolkit); last pushed 2026-10-11. Every point is earned from checkable signals — never paid placement. How scoring works →

How Stripe Agent Toolkit 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 Stripe Agent Toolkit 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/stripe/ai, MIT, last pushed 2026-10-11. 29% 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 6.1/10 (scanned Oct 3, 2026). The checks that decide who can get a change released:

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

  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: @stripe/agent-toolkit 0.9.0. No published advisory affects it (OSV, checked 2026-10-11).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Stripe Agent Toolkit.

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 Stripe Agent Toolkit’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 Stripe Agent Toolkit compares in MCP Servers

  1. #32 Firecrawl MCP Server 84.8 +0.2
  2. #33 Coolify MCP 84.7 +0.1
  3. #34 Stripe Agent Toolkit 84.6 this agent
  4. #35 Google Flights MCP (fli) 84.5 −0.1
  5. #36 Gongio MCP 84.4 −0.2

Bars show each HVTrust score; the tick marks Stripe Agent Toolkit’s 84.6.

Where the 84.6 comes from

HVTrust dimensions vs the MCP Servers average

84.6 / 100 · 100.0% confidence

Stripe Agent Toolkit MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
16.6 / 25
6.2 above avg 10.4
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.5 above avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
13.7 / 17
1.5 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
18.1 / 20
5.9 above avg 12.2
AdoptionLog-scaled stars · package downloads
13.5 / 20
6.1 above avg 7.4

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-09-23
Rank Moved
Rank dropped 31 spots (#57 → #88)
2026-09-21
Rank Moved
Rank rose 31 spots (#88 → #57)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.1/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.
Compare with another agent Get email alerts for Stripe Agent Toolkit View MCP Servers Report missing data
75.4
Activity sub-score · out of 100
#34
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 A 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-11 12:08 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
1.9k
Forks
353
Last Push
2026-10-11
today
Commits (4 wk)
32
Downloads (7d)
18,421
npm
HN mentions (30d)
—
Open Issues
32
Rank Change
▲3
was #98

Analysis

Activity Inputs

75.4 / 100
StarsRepository reach
19.6 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
18.9 / 25
CommunityFork signal
11.9 / 20

Common questions about Stripe Agent Toolkit

Public supply-chain signals for Stripe Agent Toolkit are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Stripe Agent Toolkit carries less obvious unverified-evidence risk than projects with thin signals.
Does Stripe Agent Toolkit publish package provenance?
Yes. Stripe Agent Toolkit's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Stripe Agent Toolkit have an OpenSSF Scorecard?
Stripe Agent Toolkit has an OpenSSF Scorecard score of 6.1/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 Stripe Agent Toolkit actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Stripe Agent Toolkit use?
Stripe Agent Toolkit ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Stripe Agent Toolkit's commits signed?
28% of the last 100 commits to Stripe Agent Toolkit 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
Stripe Agent Toolkit appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration 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

Maintain Stripe Agent Toolkit?

For maintainers

HVTrust scores Stripe Agent Toolkit 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 3
2026-09-23
Rank Moved
Rank dropped 31 spots (#57 → #88)
2026-09-21
Rank Moved
Rank rose 31 spots (#88 → #57)
2026-09-05
Rank Moved
Rank dropped 13 spots (#60 → #73)
GitHub → Website → npm: @stripe/agent-toolkit

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 84.6 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/stripe-agent-toolkit.svg)](https://hvtracker.net/agents/stripe-agent-toolkit)
HTML:
<a href="https://hvtracker.net/agents/stripe-agent-toolkit"><img src="https://hvtracker.net/badge/stripe-agent-toolkit.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