Is 1password MCP safe to use?

1password MCP has an HVTrust score of 65.0/100 (Grade B), ranked #230 of 1283 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 65.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 19 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 B Listed Apache-2.0

65.0/100

Rank #230 of 1283

Compare 1password MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-07-30 · 13d ago

Recent change

Rank +1

Is 1password MCP safe? 1password MCP scores 65.0/100 (Grade B), ranked #230 of 1283 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; no OSSF Scorecard result yet; 30% of recent commits are signed; last pushed 2026-07-30. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#67 Grafana MCP Server — 65.1 (B) → #68 Sec Edgar MCP — 65.0 (B) → #70 World Model MCP — 64.9 (C) → #71 Google Workspace MCP — 64.6 (C) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-10

Rank Moved

Rank dropped 16 spots (#212 → #228)

2026-08-08

Newly Listed

First tracked at rank #216

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

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

54.4

Activity sub-score · out of 100

#69

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

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars

Forks

Last Push

2026-07-30

13 days ago

Commits (4 wk)

Downloads (7d)

257

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #229

Analysis

HVTrust Dimensions vs MCP Servers

65.0 / 100 · 100.0% confidence

1password MCP MCP Servers average (761 agents)

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

9.0 / 25

4.0 above avg 5.0

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.7 above avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

in line with avg 8.8

Maintenance60% last-push freshness · 40% commit activity

17.5 / 20

5.1 above avg 12.4

AdoptionLog-scaled stars · package downloads

6.3 / 20

0.5 above avg 5.8

Activity Inputs

54.4 / 100

StarsRepository reach

7.8 / 30

FreshnessLast push recency

23.2 / 25

ActivityRecent commits

19.8 / 25

CommunityFork signal

3.6 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

—

Not available

Signed Commits

30%

of last 100 commits verified

Is 1password MCP safe?

1password MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

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?

No OpenSSF Scorecard data is currently published for 1password MCP. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is 1password MCP actively maintained?

Maintained. Last push was 13 days ago.

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?

30% 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

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

medium 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 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-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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON