Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CakeRepository/1password

NPM · @TAKESCAKE/1PASSWORD-MCP · SCANNED SEP 20

MCP server for 1Password service accounts — tools and resources for vaults and credentials

0 this week 78 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 33 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability87
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1415 tokens (~88/item across 16 items; 13 tools + 3 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "item_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.CakeRepository/1password MCP server?

io.github.CakeRepository/1password runs locally as an npm package, launched with npx -y @takescake/1password-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @takescake/1password-mcp

# add to Claude Code
claude mcp add cakerepository-1password -- npx -y @takescake/1password-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "cakerepository-1password": {
      "command": "npx",
      "args": [
        "-y",
        "@takescake/1password-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "cakerepository-1password": {
      "command": "npx",
      "args": [
        "-y",
        "@takescake/1password-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add cakerepository-1password -- npx -y @takescake/1password-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cakerepository-1password": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@takescake/1password-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cakerepository-1password --command npx --arg -y --arg @takescake/1password-mcp
# ~/.hermes/config.yaml
mcp_servers:
  cakerepository-1password:
    command: "npx"
    args: ["-y", "@takescake/1password-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "cakerepository-1password": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@takescake/1password-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add cakerepository-1password -t stdio -c npx -a -y @takescake/1password-mcp
// mcp.json
{
  "mcpServers": {
    "cakerepository-1password": {
      "command": "npx",
      "args": [
        "-y",
        "@takescake/1password-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 19 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 16 Sept 26 −2
    • Security disclosure: fail → unverified functional
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/@takescake/1password-mcp@2.5.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 98 packages
Packages resolved 98
Stale 31
No linked repository 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~1,356 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
item_archive ~62

Archive an item in a 1Password vault. The item is moved to the archive and hidden from regular views, rather than being permanently deleted.

NameTypeReqDescription
itemIdstringyesItem ID to archive.
vaultIdstringyesVault ID containing the item.

No output schema declared.

No examples provided.

item_delete ~51

Permanently delete an item from a 1Password vault. This action cannot be undone.

NameTypeReqDescription
itemIdstringyesItem ID to delete.
vaultIdstringyesVault ID containing the item.

No output schema declared.

No examples provided.

item_edit ~178

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.

NameTypeReqDescription
fieldsarrayFields to upsert (create or update) by id or title.
itemIdstringyesItem ID to edit.
notesstringFull replacement of the item's notes. Pass an empty string to clear notes.
removeFieldsarrayField ids or titles to remove from the item.
tagsarrayReplacement set of tags (replaces all existing tags).
titlestringNew item title.
urlstringReplacement primary website URL for the item.
vaultIdstringyesVault ID containing the item.

No output schema declared.

No examples provided.

item_get ~159

Retrieve a full 1Password item — title, category, tags, notes, and all fields (id, title, type, section). Concealed field values are hidden unless reveal is true. Accepts a secret reference (op://vault/item/field) or vault ID + item ID.

NameTypeReqDescription
itemIdstringItem ID to retrieve (required if secretReference is not provided).
revealbooleanIf true, include concealed field values in plaintext. Defaults to false for security.
secretReferencestringSecret reference in op://vault/item/field format. If provided, vaultId and itemId are ignored.
vaultIdstringVault ID containing the item (required if secretReference is not provided).

No output schema declared.

No examples provided.

item_list ~52

List all items in a 1Password vault, returning id, title, category, tags, and updatedAt for each. Never returns secret values.

NameTypeReqDescription
vaultIdstringyesVault ID to list items from.

No output schema declared.

No examples provided.

item_lookup ~80

Search for items within a 1Password vault by title substring. Returns item IDs, titles, categories, and vault IDs.

NameTypeReqDescription
limitintegerMaximum number of items to return (default: all).
querystringOptional substring to filter item titles (case-insensitive).
vaultIdstringyesVault ID to search within.

No output schema declared.

No examples provided.

note_create ~96

Create a Secure Note item in a 1Password vault, with optional tags and custom fields.

NameTypeReqDescription
fieldsarrayOptional custom fields to attach to the note.
notesstringyesNote body text. Pass an empty string for an empty note.
tagsarrayOptional tags for organization.
titlestringyesNote title.
vaultIdstringyesVault ID to create the note in.

No output schema declared.

No examples provided.

password_create ~150

Create a new password/login item in a 1Password vault with optional username, URL, tags, and notes.

NameTypeReqDescription
categorystringItem category. Defaults to Login.
notesstringOptional notes.
passwordstringyesPassword to store in the item.
returnSecretbooleanIf true, include the created password in the response. Defaults to false for security.
tagsarrayOptional tags for organization.
titlestringyesItem title.
urlstringOptional website URL to associate.
usernamestringUsername to store in the item.
vaultIdstringyesVault ID to create the item in.

No output schema declared.

No examples provided.

password_generate ~99

Generate a cryptographically secure random password with configurable length and character types. Uses rejection sampling for unbiased randomness.

NameTypeReqDescription
includeNumbersbooleanInclude digits (0-9). Defaults to true.
includeSymbolsbooleanInclude symbols (!@#$%^&*…). Defaults to true.
includeUppercasebooleanInclude uppercase letters. Defaults to true.
lengthintegerLength of the password. Defaults to 20.

No output schema declared.

No examples provided.

password_generate_memorable ~128

Generate a memorable passphrase from random dictionary words with optional number and symbol suffixes. Uses a ~500-word curated list for good entropy.

NameTypeReqDescription
capitalizebooleanCapitalize each word. Defaults to true.
includeNumberbooleanAppend a random number (0-99) at the end. Defaults to true.
includeSymbolbooleanAppend a random symbol at the end. Defaults to true.
separatorstringSeparator between words. Defaults to '-'.
wordCountintegerNumber of words to include. Defaults to 3.

No output schema declared.

No examples provided.

password_read ~153

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.

NameTypeReqDescription
fieldstringField id or title to read. Defaults to 'password'.
itemIdstringItem ID for item lookup (required if secretReference is not provided).
revealbooleanIf false, return metadata only without the secret value. Defaults to true.
secretReferencestringSecret reference in op://vault/item/field format. If provided, vaultId and itemId are ignored.
vaultIdstringVault ID for item lookup (required if secretReference is not provided).

No output schema declared.

No examples provided.

password_update ~116

Update (rotate) a password or concealed field on an existing 1Password item. If the target field does not exist, it will be created.

NameTypeReqDescription
fieldstringField id or title to update. Defaults to 'password'.
itemIdstringyesItem ID to update.
newPasswordstringyesNew password value.
returnSecretbooleanIf true, include the updated password in the response. Defaults to false for security.
vaultIdstringyesVault ID containing the item.

No output schema declared.

No examples provided.

vault_list ~32

List all 1Password vaults accessible to the service account. Returns vault IDs, names, descriptions, and types.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the io.github.CakeRepository/1password MCP server?

io.github.CakeRepository/1password is an MCP server listed in the public MCP registry as io.github.CakeRepository/1password. MCP server for 1Password service accounts, tools and resources for vaults and credentials. This page covers its npm package (@takescake/1password-mcp).

Is the io.github.CakeRepository/1password MCP server safe to use?

io.github.CakeRepository/1password scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.CakeRepository/1password MCP server expose?

io.github.CakeRepository/1password exposes 13 tools: vault_list, item_lookup, item_delete, item_get, item_edit, and 8 more. Their descriptions and schemas cost roughly 1,356 tokens of context every time the server is loaded.

Is the io.github.CakeRepository/1password MCP server still maintained?

io.github.CakeRepository/1password is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.CakeRepository/1password MCP server under?

io.github.CakeRepository/1password declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.