# dev.1pass/logi (npm · @1pass/mcp)

logi (1pass) IdP — manage your OAuth apps, redirect URIs, passkeys, login history and docs.

- Trust score: 71/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-17

## Components

- npm · `@1pass/mcp`: 71/100 (this document), [markdown](https://verifymcp.io/servers/dev-1pass-logi/1pass-mcp.md), [page](https://verifymcp.io/servers/dev-1pass-logi/1pass-mcp)

## Channel facts

- Registry: `npm`
- Package: `@1pass/mcp`
- Version: `0.2.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-17.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1354 tokens (~90/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add dev-1pass-logi -- npx -y @1pass/mcp
```

### Codex

```bash
codex mcp add dev-1pass-logi -- npx -y @1pass/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-1pass-logi": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@1pass/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-1pass-logi --command npx --arg -y --arg @1pass/mcp
```

### Hermes

```yaml
mcp_servers:
  dev-1pass-logi:
    command: "npx"
    args: ["-y", "@1pass/mcp"]
```

### Other

```json
{
  "mcpServers": {
    "dev-1pass-logi": {
      "command": "npx",
      "args": [
        "-y",
        "@1pass/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-17 (score 71, +1)

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

### 2026-08-16 (score 70, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-08-11 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-08 (score 66, +28)

- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Tool coverage: 0
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Schema quality: pass

### 2026-08-07 (score 38)

First indexed and scored.

## MCP tools (15)

### `logi_whoami` (~76 tokens)

Use when the user asks 'am I logged in?', 'which logi account is this?', or whenever you need to verify the configured PAK is valid before another tool call. Read-only. Returns the email + scopes of the current PAK. Do NOT use to list login history — use logi_list_login_history.

### `logi_list_login_history` (~86 tokens)

Use when the user asks about recent sign-ins, suspicious access, login locations, or wants to audit account activity. Read-only. Returns the latest N (default 30, max 100) login events with country, IP, and a suspicious flag. Each row carries an `id` you can pass to logi_delete_login_log.

Input parameters:

- `limit` (number)

### `logi_delete_login_log` (~84 tokens)

Use when the user wants to remove a specific login record from view (e.g. 'delete that suspicious entry'). Soft-delete only — recoverable for 90 days. Requires the row `id` from logi_list_login_history. Do NOT use this to revoke a session or block future logins; that's a different scope.

Input parameters:

- `id` (number, required)

### `logi_list_trashed_logs` (~61 tokens)

Use when the user asks 'what did I delete?' or wants to review/restore previously soft-deleted login records. Read-only. Returns rows still within the 90-day grace window. Pair with logi_restore_login_log to undo.

### `logi_restore_login_log` (~68 tokens)

Use when the user wants to undo a deletion ('restore that log', 'I deleted the wrong one'). Takes an `id` from logi_list_trashed_logs. Idempotent — restoring an already-restored row is a no-op.

Input parameters:

- `id` (number, required)

### `logi_list_passkeys` (~59 tokens)

Use when the user wants to see their registered Passkeys (Face ID / Touch ID / hardware key) — typically before deleting a stale one or auditing devices. Read-only. Returns name, created_at, last_used_at per passkey.

### `logi_delete_passkey` (~66 tokens)

Use when the user explicitly asks to remove a specific passkey (e.g. lost device, old laptop). Destructive and irreversible — confirm with the user before calling. Takes the passkey `id` from logi_list_passkeys.

Input parameters:

- `id` (number, required)

### `logi_list_connected_apps` (~72 tokens)

Use when the user asks 'which apps can see my data?', 'what have I authorized?', or wants to revoke third-party access. Read-only. Returns OAuth applications with active consent + the specific claims (email, phone, etc.) shared with each. Pair with the developer portal to revoke individual grants.

### `logi_list_apps` (~104 tokens)

Use when the user (as a developer) asks 'what OAuth apps do I own?', 'list my RPs', or needs the app id before adding/removing a redirect_uri. Read-only. Returns id, name, client_id, status, and current redirect_uris for every app the PAK owner can manage. Requires PAK scope apps:read or apps:manage. Do NOT use to list end-user authorized apps — that's logi_list_connected_apps.

### `logi_show_app` (~81 tokens)

Use when the user wants the full RP record for one app (all fields: redirect_uris, app_link_url, allowed_scopes, client_type, webhook_url, status, etc.). Read-only. Takes the `id` from logi_list_apps. Requires PAK scope apps:read or apps:manage.

Input parameters:

- `id` (number, required)

### `logi_add_redirect_uri` (~145 tokens)

Use when the user (RP owner) wants to register a new OAuth callback URL — for example after deploying to a new domain (easybracket.org), adding an iOS scheme, or staging environment. Idempotent: no-op if the URI is already registered. Server-side validators run (URI shape, sandbox host whitelist, app_link host match) and the change is recorded in developer_audit_logs. Requires PAK scope apps:manage. Confirm with the user before calling — adding the wrong URI widens the attack surface for token interception. Pair with logi_show_app afterward to verify.

Input parameters:

- `id` (number, required)
- `uri` (string, required)

### `logi_remove_redirect_uri` (~98 tokens)

Use when the user (RP owner) wants to deregister an old/unused OAuth callback URL — for example a historical onrender.com host that's been migrated to a custom domain. Refuses to remove the last remaining URI (would disable OAuth entirely). Server-side validators + audit log apply. Requires PAK scope apps:manage. Confirm with the user before calling.

Input parameters:

- `id` (number, required)
- `uri` (string, required)

### `logi_fetch_quickstart` (~123 tokens)

Use when the user (or an agent) needs the logi/1pass agent quickstart guide — typical triggers: 'logi 어떻게 통합해?', 'how do I integrate 1pass?', 'logi 시작 가이드', or before generating RP integration code. Read-only, no auth required (fetches public docs.1pass.dev/llms/guide/agent-quickstart.md). Default lang=ko; pass lang=en for English. Prefer this over web search for logi onboarding docs.

Input parameters:

- `lang` (string)

### `logi_get_doc` (~146 tokens)

Use when the user asks about a specific logi/1pass topic (OAuth scopes, PKCE, redirect URI rules, CLI commands, security model, panopticon, agent approval, etc.) and you need the canonical doc text. Read-only, no auth required (fetches public docs.1pass.dev/llms/{path}). Path must be like 'oauth/scopes.md', 'guide/security.md', 'cli/overview.md'. Allowed prefixes: guide/, oauth/, integrations/, tracks/, cli/, reference/, security/, operations/, panopticon/, agent-approval/, compare/. Discover available paths via logi_list_docs first.

Input parameters:

- `path` (string, required)

### `logi_list_docs` (~85 tokens)

Use when you (or the user) need to discover what logi/1pass docs exist — typically as a first step before logi_get_doc, or when the user asks 'what docs are available?'. Read-only, no auth required (fetches public docs.1pass.dev/llms.txt sitemap). Returns the canonical list of doc paths with brief titles.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/dev-1pass-logi/1pass-mcp#diagnostics

## Score history

- 2026-08-17: 71
- 2026-08-16: 70
- 2026-08-15: 66
- 2026-08-14: 66
- 2026-08-13: 66
- 2026-08-12: 66
- 2026-08-11: 66
- 2026-08-10: 66
- 2026-08-09: 66
- 2026-08-08: 66
- 2026-08-07: 38

## Links

- npm package: https://www.npmjs.com/package/@1pass/mcp
- Socket report: https://socket.dev/npm/package/@1pass/mcp
- Repository: https://github.com/dcode-co/logi-plugins
- Website: https://docs.1pass.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-1pass-logi/1pass-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-1pass-logi/1pass-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-1pass-logi/1pass-mcp