Is 1password MCP safe to use?

1password MCP has an HVTrust score of 44.3/100 (Grade D), ranked #936 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for 1password MCP?

1password MCP scores 44.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 20 GitHub stars and is categorized under MCP Servers.

1password MCP

CakeRepository/1Password-MCP

1Password MCP server used for storing passwords create separate vault please

MCP Servers TypeScript Grade D Listed Apache-2.0

44.3/100

Rank #936 of 1320

Compare 1password MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-31 · 4d ago

Recent change

Rank +15

Is 1password MCP safe? 1password MCP scores 44.3/100 (Grade D), ranked #936 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.8/10; 31% of recent commits are signed; last pushed 2026-08-31. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#511 Propresenter MCP — 44.4 (D) → #512 Astravue MCP — 44.3 (D) → #514 Sentry MCP — 44.2 (D) → #515 Excel MCP Server — 44.1 (D) →

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-04

Rank Moved

Rank dropped 24 spots (#912 → #936)

2026-09-03

Rank Moved

Rank dropped 55 spots (#857 → #912)

2026-09-02

Grade Changed

Trust grade B → D

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.8/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 1password MCP View MCP Servers Report missing data

39.7

Activity sub-score · out of 100

#513

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-04

Activity & Reach

Stars

Forks

Last Push

2026-08-31

4 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼24

was #912

Analysis

HVTrust Dimensions vs MCP Servers

44.3 / 100 · 67.0% confidence

1password MCP MCP Servers average (778 agents)

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

13.8 / 25

4.2 above avg 9.6

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.7 / 17

in line with avg 11.8

Maintenance60% last-push freshness · 40% commit activity

12.3 / 20

in line with avg 12.2

AdoptionLog-scaled stars · package downloads

3.2 / 20

3.1 below avg 6.3

Activity Inputs

39.7 / 100

StarsRepository reach

7.9 / 30

FreshnessLast push recency

24.4 / 25

ActivityRecent commits

3.8 / 25

CommunityFork signal

3.6 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

3.8 / 10

OpenSSF Scorecard · scanned Sep 3, 2026

Signed Commits

31%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 2

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is 1password MCP safe?

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

Yes. 1password MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does 1password MCP have an OpenSSF Scorecard?

1password MCP has an OpenSSF Scorecard score of 3.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 1password MCP actively maintained?

Actively maintained. The repository was pushed to within the last 4 day(s).

What license does 1password MCP use?

1password MCP ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are 1password MCP's commits signed?

31% of the last 100 commits to 1password MCP 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

1password MCP 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 1password MCP'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-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

Maintain 1password MCP?

For maintainers

HVTrust scores 1password MCP 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-04

Rank Moved

Rank dropped 24 spots (#912 → #936)

2026-09-03

Rank Moved

Rank dropped 55 spots (#857 → #912)

2026-09-02

Grade Changed

Trust grade B → D

2026-09-02

Rank Moved

Rank dropped 615 spots (#242 → #857)

2026-09-02

HVTrust Changed

HVTrust down 23.2pts (67.7 → 44.5)

2026-08-31

Grade Changed

Trust grade D → B

2026-08-31

Rank Moved

Rank rose 568 spots (#804 → #236)

2026-08-31

HVTrust Changed

HVTrust up 25.1pts (42.7 → 67.8)

2026-08-31

Activity Score Changed

Activity score up 8pts (32 → 40)

2026-08-30

Grade Changed

Trust grade B → D

2026-08-30

Rank Moved

Rank dropped 535 spots (#269 → #804)

2026-08-30

HVTrust Changed

HVTrust down 22.5pts (65.2 → 42.7)

2026-08-29

Scorecard Added

OSSF Scorecard: 3.8/10

2026-08-29

Grade Changed

Trust grade C → B

2026-08-29

Rank Moved

Rank rose 34 spots (#303 → #269)

2026-08-29

Activity Score Changed

Activity score down 20pts (52 → 32)

2026-08-26

Rank Moved

Rank dropped 28 spots (#266 → #294)

2026-08-24

Grade Changed

Trust grade D → C

2026-08-24

Rank Moved

Rank rose 331 spots (#597 → #266)

2026-08-24

HVTrust Changed

HVTrust up 21.7pts (41.9 → 63.6)

2026-08-22

Grade Changed

Trust grade C → D

2026-08-22

Rank Moved

Rank dropped 331 spots (#266 → #597)

2026-08-22

HVTrust Changed

HVTrust down 21.8pts (63.7 → 41.9)

2026-08-19

Grade Changed

Trust grade D → C

2026-08-19

Rank Moved

Rank rose 329 spots (#596 → #267)

2026-08-19

HVTrust Changed

HVTrust up 21.7pts (42.1 → 63.8)

2026-08-17

Grade Changed

Trust grade C → D

2026-08-17

Rank Moved

Rank dropped 336 spots (#259 → #595)

2026-08-17

HVTrust Changed

HVTrust down 21.8pts (64.0 → 42.2)

2026-08-13

Grade Changed

Trust grade D → C

2026-08-13

Rank Moved

Rank rose 327 spots (#575 → #248)

2026-08-13

HVTrust Changed

HVTrust up 21.8pts (42.4 → 64.2)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-12

Grade Changed

Trust grade B → D

2026-08-12

Rank Moved

Rank dropped 346 spots (#229 → #575)

2026-08-12

HVTrust Changed

HVTrust down 22.7pts (65.1 → 42.4)

2026-08-10

Rank Moved

Rank dropped 16 spots (#212 → #228)

2026-08-08

Newly Listed

First tracked at rank #216

GitHub → npm: @takescake/1password-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/1password-mcp.svg)](https://hvtracker.net/agents/1password-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/1password-mcp"><img src="https://hvtracker.net/badge/1password-mcp.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