dev.1pass/logi
NPM · @1PASS/MCP · SCANNED AUG 17
logi (1pass) IdP — manage your OAuth apps, redirect URIs, passkeys, login history and docs.
Available components
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 →
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
- 30 of 96 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 9 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 Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @1pass/mcp
claude mcp add dev-1pass-logi -- npx -y @1pass/mcp
codex mcp add dev-1pass-logi -- npx -y @1pass/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-1pass-logi": {
"type": "local",
"command": [
"npx",
"-y",
"@1pass/mcp"
],
"enabled": true
}
}
} openclaw mcp add dev-1pass-logi --command npx --arg -y --arg @1pass/mcp
mcp_servers:
dev-1pass-logi:
command: "npx"
args: ["-y", "@1pass/mcp"] {
"mcpServers": {
"dev-1pass-logi": {
"command": "npx",
"args": [
"-y",
"@1pass/mcp"
]
}
}
} 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 Aug 26 +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.
- 16 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 8 Aug 26 +28
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- 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 functional
- 7 Aug 26 38
First indexed and scored.
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 17 Aug 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 |
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
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.
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.