dev.1pass/logi
NPM · @1PASS/MCP
logi (1pass) IdP — manage your OAuth apps, redirect URIs, passkeys, login history and docs.
Available components
Last scanned (13 hours ago)
Scores higher than 65% of npm servers
Category Security
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
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 71 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1354 tokens (~90/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "logi_delete_login_log" 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 15 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
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.
- 17 Oct 26 +3
- Stability: 0.83 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 −4
- Stability: pass → 0.77 functional
- 13 Oct 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 11 Oct 26 +2
- Security disclosure: fail → unverified ▼ functional
- 7 Oct 26 −2
No change was recorded against any check on this day. Stability & Change Management went from 93 to 80.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 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.
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 18 Oct 2026 · Analysed npm/@1pass/mcp@0.2.2
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 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
logi_add_redirect_uri ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
| uri | string | yes | – |
No output schema declared.
No examples provided.
logi_delete_login_log ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
logi_delete_passkey ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
logi_fetch_quickstart ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
No output schema declared.
No examples provided.
logi_get_doc ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
logi_list_apps ~104
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
logi_list_connected_apps ~72
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
logi_list_docs ~85
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
logi_list_login_history ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
No output schema declared.
No examples provided.
logi_list_passkeys ~59
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
logi_list_trashed_logs ~61
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
logi_remove_redirect_uri ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
| uri | string | yes | – |
No output schema declared.
No examples provided.
logi_restore_login_log ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
logi_show_app ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
logi_whoami ~76
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the dev.1pass/logi MCP server?
dev.1pass/logi runs locally as an npm package, launched with npx -y @1pass/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 · @1pass/mcp
claude mcp add dev-1pass-logi -- npx -y @1pass/mcp
What is the dev.1pass/logi MCP server?
dev.1pass/logi is an MCP server listed in the public MCP registry as dev.1pass/logi. logi (1pass) IdP, manage your OAuth apps, redirect URIs, passkeys, login history and docs. This page covers its npm package (@1pass/mcp).
Is the dev.1pass/logi MCP server safe to use?
dev.1pass/logi scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 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 dev.1pass/logi MCP server expose?
dev.1pass/logi exposes 15 tools: logi_whoami, logi_list_login_history, logi_delete_login_log, logi_list_trashed_logs, logi_restore_login_log, and 10 more. Their descriptions and schemas cost roughly 1,354 tokens of context every time the server is loaded.
Is the dev.1pass/logi MCP server still maintained?
dev.1pass/logi is still listed as active in the MCP registry. We last reached this channel on 18 October 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 dev.1pass/logi MCP server under?
dev.1pass/logi declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.