Bragproof

← Reports

@takescake/1password-mcp

Starts with no setup5.1.1npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 0 of 3 tools tried
Contacts while installing and starting: nothing

15tools listed
0hosts contacted
0files written
0.2 sto start
5dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y @takescake/1password-mcp@5.1.1

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

3 tools that take no input and look read-only were called once with nothing. 0 returned a result.

vault_listNo usable answer tool reported an error: Error: Service account token is required. Provide it via --service-account-token, OP_SERVICE_ACCOUNT_TOKEN, or macOS Keychain with OP_KE
item_getNo usable answer tool reported an error: Error: Service account token is required. Provide it via --service-account-token, OP_SERVICE_ACCOUNT_TOKEN, or macOS Keychain with OP_KE
password_readNo usable answer tool reported an error: Error: Service account token is required. Provide it via --service-account-token, OP_SERVICE_ACCOUNT_TOKEN, or macOS Keychain with OP_KE

During the calls it contacted nothing it had not already contacted.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

vault_list
List the 1Password vaults accessible to the service account (limited to the allow-listed vaults when OP_MCP_ALLOWED_VAULTS / --allowed-vaults is configured). Returns vault IDs, names, descriptions, and types.
item_lookup vaultId, query, limit
Search for items within a 1Password vault by title substring. Returns item IDs, titles, categories, and vault IDs.
item_delete vaultId, itemId
Permanently delete an item from a 1Password vault. This action cannot be undone.
item_get secretReference, vaultId, itemId, reveal
Retrieve a full 1Password item — title, category, tags, notes, and all fields (id, title, type, section). Secret-bearing field values (passwords and other concealed fields, SSH private keys, one-time-password seeds, card numbers) are hidden unless reveal is true; only known non-secret types (text, URL, email, phone, date, menu, card type, address, reference) are shown by default. Accepts a secret reference (op://vault/item/field) or vault ID + item ID. Revealing a secret puts it in the model context/transcript — to USE a secret in a command or API call, prefer op_run with op:// references instead.
item_edit vaultId, itemId, title, notes, tags, url, fields, removeFields
Edit an existing 1Password item. Update the title, notes (pass an empty string to clear notes), tags, website URL, upsert fields, or remove fields. Only referenced fields are changed; all others are preserved.
10 more tools
item_list vaultId
List all items in a 1Password vault, returning id, title, category, tags, and updatedAt for each. Never returns secret values.
item_archive vaultId, itemId
Archive an item in a 1Password vault. The item is moved to the archive and hidden from regular views, rather than being permanently deleted.
note_create vaultId, title, notes, tags, fields
Create a Secure Note item in a 1Password vault, with optional tags and custom fields.
password_create vaultId, title, username, password, category, tags, notes, url, returnSecret
Create a new password/login item in a 1Password vault with optional username, URL, tags, and notes.
password_read secretReference, vaultId, itemId, field, reveal
Retrieve a secret from 1Password using either a secret reference (op://vault/item/field) or vault ID + item ID. Supports field selection and optional value reveal (defaults to metadata-only). Revealing a secret puts it in the model context/transcript — to USE a secret in a command or API call, prefer op_run with op:// references instead.
password_update vaultId, itemId, newPassword, field, returnSecret
Update (rotate) a password or concealed field on an existing 1Password item. If the target field does not exist, it will be created.
password_generate length, includeSymbols, includeNumbers, includeUppercase
Generate a cryptographically secure random password with configurable length and character types. Uses rejection sampling for unbiased randomness.
password_generate_memorable wordCount, separator, includeNumber, includeSymbol, capitalize
Generate a memorable passphrase from random dictionary words with optional number and symbol suffixes. Uses a ~500-word curated list for good entropy.
op_run command, argv, cwd, env, shell, timeout_ms, stdin
Run a local shell command with 1Password secrets injected as environment variables. Resolved values go only into the child process environment, are never logged by the server, and are redacted from stdout/stderr on a best-effort basis (including common encodings such as JSON, URL and base64) — a command that deliberately transforms or transmits a secret can still expose it. This is the preferred way to USE a secret in a command, API call, or script: prefer op_run with op://vault/item/field references in `env` over reading a secret with password_read/item_get and pasting it into a command yourself, which would put the plaintext in the model context and transcript.
op_check_ref secretReference
Validate an op://vault/item/field secret reference and return only non-secret metadata (vault name, item title, field label, field type) confirming it resolves — the field VALUE is never returned. Use this to check a reference is correct before using it with op_run; do not use password_read/item_get with reveal just to check a reference exists.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Install facts

LicenseApache-2.0
Needsnode >=20
Sourcegithub.com/CakeRepository/1Password-MCP
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-ZT8/N3/cbUE0n56zuS6vL1m4wSNthlTpABkmwy8r59Nn3FykO7iHCEkbMYyTXL3zRkw/mRsDpjJJcjotGYTDcQ==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/@takescake/1password-mcp.svg)](https://bragproof.smaverk.com/r/%40takescake/1password-mcp)

New version out? Ask for a fresh report.