Is Zapier safe to use?

Zapier has an HVTrust score of 48.9/100 (Grade D), ranked #967 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Zapier?

Zapier scores 48.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 419 GitHub stars and is categorized under MCP Servers.

Zapier

zapier/zapier-mcp

Official plugin distribution for the hosted Zapier MCP server. Install it in your AI client and connect to thousands of apps.

MCP Servers Listed MIT

Is Zapier safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.8 / 10

Provenance None

Signed commits 78%

Last push 59d ago

Compare Zapier

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Zapier scores 48.9/100 (Grade D), ranked #967 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.8/10; 78% of recent commits are signed; last pushed 2026-07-29. Every point is earned from checkable signals — never paid placement. How scoring works →

How Zapier compares in MCP Servers

Bars show each HVTrust score; the tick marks Zapier’s 48.9.

Where the 48.9 comes from

HVTrust dimensions vs the MCP Servers average

48.9 / 100 · 100.0% confidence

Zapier MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

9.9 / 25

in line with avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.6 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

8.1 / 20

4.0 below avg 12.1

AdoptionLog-scaled stars · package downloads

6.3 / 20

0.9 below avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-25

Rank Moved

Rank dropped 11 spots (#956 → #967)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.8/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 59 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Zapier View MCP Servers Report missing data

41.1

Activity sub-score · out of 100

#559

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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

419

Forks

Last Push

2026-07-29

59 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #967

Analysis

Activity Inputs

41.1 / 100

StarsRepository reach

15.7 / 30

FreshnessLast push recency

16.8 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

8.5 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.8 / 10

OpenSSF Scorecard · scanned Sep 11, 2026 (refresh pending)

Signed Commits

78%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 6

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 10

Common questions about Zapier

Public trust evidence for Zapier 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 Zapier publish package provenance?

No published build provenance is currently detected for Zapier. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Zapier have an OpenSSF Scorecard?

Zapier has an OpenSSF Scorecard score of 4.8/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 Zapier actively maintained?

Slowing down. Last push was 59 days ago — keep an eye on whether activity resumes.

What license does Zapier use?

Zapier ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Zapier's commits signed?

78% of the last 100 commits to Zapier 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

Zapier appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 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

N/A

No package source configured

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 Zapier'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

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Zapier?

For maintainers

HVTrust scores Zapier 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

2026-09-25

Rank Moved

Rank dropped 11 spots (#956 → #967)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank dropped 380 spots (#573 → #953)

2026-09-23

HVTrust Changed

HVTrust up 13.6pts (35.5 → 49.1)

2026-09-22

Newly Listed

First tracked at rank #573

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 10 spots (#934 → #944)

2026-09-10

Grade Changed

Trust grade C → D

2026-09-09

Rank Moved

Rank dropped 21 spots (#893 → #914)

2026-09-07

Rank Moved

Rank dropped 40 spots (#848 → #888)

2026-09-06

Rank Moved

Rank dropped 15 spots (#833 → #848)

2026-09-05

Rank Moved

Rank dropped 61 spots (#772 → #833)

2026-09-04

Rank Moved

Rank dropped 27 spots (#745 → #772)

2026-09-03

Rank Moved

Rank dropped 49 spots (#696 → #745)

2026-09-02

Rank Moved

Rank dropped 33 spots (#663 → #696)

2026-09-01

Rank Moved

Rank dropped 26 spots (#637 → #663)

2026-08-31

Rank Moved

Rank dropped 36 spots (#601 → #637)

2026-08-29

Rank Moved

Rank dropped 39 spots (#555 → #594)

2026-08-28

Rank Moved

Rank dropped 42 spots (#513 → #555)

2026-08-28

Activity Score Changed

Activity score down 8pts (52 → 45)

2026-08-27

Scorecard Added

OSSF Scorecard: 4.8/10

2026-08-27

Grade Changed

Trust grade D → C

2026-08-27

Rank Moved

Rank rose 525 spots (#1038 → #513)

2026-08-27

HVTrust Changed

HVTrust up 30.8pts (22.4 → 53.2)

2026-08-26

Rank Moved

Rank dropped 82 spots (#956 → #1038)

2026-08-24

Rank Moved

Rank dropped 12 spots (#942 → #954)

2026-08-17

Rank Moved

Rank rose 12 spots (#958 → #946)

2026-08-16

Rank Moved

Rank dropped 42 spots (#916 → #958)

2026-08-13

Rank Moved

Rank dropped 19 spots (#884 → #903)

2026-08-10

Rank Moved

Rank dropped 49 spots (#833 → #882)

2026-08-08

Newly Listed

First tracked at rank #822

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/zapier.svg)](https://hvtracker.net/agents/zapier)
            
HTML:
            <a href="https://hvtracker.net/agents/zapier"><img src="https://hvtracker.net/badge/zapier.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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