1password (kefapps) MCP Server
mcp-1password
npm
v0.2.0
Published by kefapps — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Neutral MCP server for 1Password desktop app integrations with opaque-by-default secret handling.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
high Shell/command execution in server code (dist/op-runner.js)MTC-SRC-002
In the server's implementation (`dist/op-runner.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: rt { spawn } from "node:child_process"; import { constants, readFileSync, realpathSync } from "node:fs"; import { access
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/op-runner.js
Tools 30
Each tool and what it can reach — statically extracted from the published source.
environment_get_variableno sensitive capabilityenvironment_get_variablesno sensitive capabilityenvironment_reveal_variableno sensitive capabilitygroup_getno sensitive capabilityitem_archiveno sensitive capabilityitem_createno sensitive capabilityitem_deleteno sensitive capabilityitem_get_metadatano sensitive capabilityitem_searchno sensitive capabilityitem_updateno sensitive capability
Show 20 more tools ↓
op_script_listno sensitive capabilityop_script_runno sensitive capabilityop_session_resetno sensitive capabilityop_session_statusno sensitive capabilitypassword_createno sensitive capabilitypassword_generateno sensitive capabilitypassword_generate_memorableno sensitive capabilitypassword_readno sensitive capabilitypassword_updateno sensitive capabilitysdk_capabilitiesno sensitive capabilitysecret_revealno sensitive capabilityvault_createno sensitive capabilityvault_deleteno sensitive capabilityvault_getno sensitive capabilityvault_listno sensitive capabilityvault_permissions_getno sensitive capabilityvault_permissions_grant_groupno sensitive capabilityvault_permissions_revoke_groupno sensitive capabilityvault_permissions_update_groupno sensitive capabilityvault_updateno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (30 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.2.0 latest |
A 93/100 | 1 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan mcp-1password --onlineOther implementations of 1password 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Security & Testing
The Stripe Agent Toolkit enables popular agent frameworks including LangChain and Vercel's AI SDK to integrate with Stripe APIs through function calling.
MCP (Model Context Protocol) server for AgentGate. Enables Claude and other MCP-compatible AI assistants to request approvals.
Scan any website for AI agent readiness, payment protocols, and discovery endpoints
MCP server for aigently security guardrails — reads static catalog-data JSON, zero API dependency
Governed threat modeling, code threat verification, traceability & compliance, as MCP tools.
Governed threat modeling, code threat verification, traceability & compliance, as MCP tools.