com.dustforge/demipass
NPM · DEMIPASS · SCANNED AUG 3
Credential custody for agents: use secrets blind (ssh/http/smtp/git/db), never in context.
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
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 26 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability43
- AI-judged instruction clarity (poor).Fail
- Context-footprint check failed: tool/resource definitions use about 2827 tokens (~104/item across 27 items; 27 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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 · demipass
claude mcp add com-dustforge-demipass -- npx -y demipass
codex mcp add com-dustforge-demipass -- npx -y demipass
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-dustforge-demipass": {
"type": "local",
"command": [
"npx",
"-y",
"demipass"
],
"enabled": true
}
}
} openclaw mcp add com-dustforge-demipass --command npx --arg -y --arg demipass
mcp_servers:
com-dustforge-demipass:
command: "npx"
args: ["-y", "demipass"] {
"mcpServers": {
"com-dustforge-demipass": {
"command": "npx",
"args": [
"-y",
"demipass"
]
}
}
} 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.
- 3 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 31 Jul 26 +4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 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
- 26 Jul 26 73
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 0 packages
0 packages in the resolved dependency tree.
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.
conduit_send ~153
CONDUIT: Send a message to another agent via Conduit (agent-to-agent messaging). If no handshake exists with the target, one is filed automatically — the target agent must approve before messages flow. Known agents: civitasvox-brain (Brain), civitasvox-conductor (Conductor), civitasvox-riley (Riley), platform-rowen (Rowen), platform-lori (Lori). Requires CONDUIT_TOKEN env var.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Message body to send |
| thread_id | string | — | Optional: reuse an existing thread ID instead of finding/creating one |
| to | string | yes | Target agent ID (e.g. "civitasvox-brain") |
No output schema declared.
No examples provided.
conduit_status ~33
CONDUIT: Get Conduit service status — agent count, active sessions, pending handshakes, thread/message counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
conduit_threads ~29
CONDUIT: List active Conduit threads. Shows all conversations between agents that you have access to.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
demipass_delete ~98
Permanently retire a secret by name or ref code. Terminal state: it disappears from list/search and its value is never served again. Use for cleanup of test artifacts, dead credentials, and superseded generations. For a compromised-but-still-needed credential, prefer demipass_rotate.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | — | Name of the secret to delete |
| ref | string | — | Ref code of the secret to delete (alternative to name) |
No output schema declared.
No examples provided.
demipass_doctor ~60
FIRST CONTACT: Run this first when you start a new session. Reports: your identity, token status, API connectivity, secrets count, trust band, available actions, and recommendations. If anything is misconfigured, doctor tells you what to fix.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
demipass_execute ~123
EGRESS step 2: Redeem a use-token. The secret is injected server-side — into an HTTP header, a POST body, an SSH command, or returned as a document. You receive the result (API response, command output) but never the secret itself. The token is burned after one use.
| Name | Type | Req | Description |
|---|---|---|---|
| params | object | — | Action params: {command, target_user} for ssh_exec, {url, method} for http_header, etc. |
| token | string | yes | Use-token from demipass_get_token (valid 30 seconds) |
No output schema declared.
No examples provided.
demipass_expiring ~55
List secrets expiring within N days. Use for proactive rotation planning. Returns secrets approaching expiration and already-expired secrets.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | — | Window in days (default: 7, max: 90) |
No output schema declared.
No examples provided.
demipass_explain_denial ~118
DIAGNOSTICS: When an action is blocked, run this to find out why. Checks: does the secret exist? Is it active? Is there a matching context? Is your account suspended? Returns specific fixes for each failing check.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | — | Action type that was denied (ssh_exec, http_header, etc.) |
| name | string | — | Secret name that was denied |
| ref | string | — | Ref code that was denied |
| target_host | string | — | Target host that was denied |
No output schema declared.
No examples provided.
demipass_genesis_seed ~66
GENESIS: Get the ODT seed document. This is the Rorschach inkblot — the same document for everyone. Your refraction of it becomes your permanent origin fingerprint. Read the seed, then call demipass_genesis_submit with your refraction.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
demipass_genesis_status ~28
GENESIS: Check if an origin refraction has been recorded for your DID.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
demipass_genesis_submit ~100
GENESIS: Submit your origin refraction. This is permanent and non-rotatable — it becomes the root of your identity tree. After submitting, air-gap the raw refraction (write to USB/offline storage) and purge it from your context. Only the hash is stored server-side.
| Name | Type | Req | Description |
|---|---|---|---|
| refraction | string | yes | Your refraction of the ODT seed document. Min 50 chars. This becomes your permanent origin fingerprint. |
No output schema declared.
No examples provided.
demipass_genesis_verify ~79
GENESIS: Verify a refraction against your origin. Used for re-authentication without stored tokens. Produce your refraction of the same seed — if it matches your origin pattern closely enough, identity is confirmed.
| Name | Type | Req | Description |
|---|---|---|---|
| refraction | string | yes | Your current refraction of the ODT seed. Will be compared against your origin fingerprint. |
No output schema declared.
No examples provided.
demipass_get_token ~215
EGRESS step 1: Request a 30-second use-token for a stored secret. Use the ref code if you have one (preferred), or name + context. The token is a single-use nonce — not the secret itself. You must redeem it within 30 seconds via demipass_execute.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | — | Action type: http_header, ssh_exec, http_body, document |
| context | string | — | Context name for the use-token |
| name | string | — | Secret name (use ref instead when possible) |
| owner_did | string | — | Owner DID (only needed if using name without ref for delegated secrets) |
| ref | string | — | Routed reference code (e.g. DP-API-openrout-7f3a9c1e). Preferred — auto-resolves owner, delegation, context, action. |
| target_host | string | — | Target host for SSH exec actions |
| target_url | string | — | Target URL for HTTP header/body and database actions |
No output schema declared.
No examples provided.
demipass_list ~53
List all secrets in the vault. Returns names, types, ref codes, providers, and expiration dates — never values. Use this to find a ref code you need, or to check what is expiring soon.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
demipass_onboard ~95
Self-onboard to the Dustforge identity platform. Creates a cryptographic identity (DID:key), email address, and wallet. The invite key serves as your initial password and referral attribution. Call this once — subsequent sessions authenticate with demipass_get_token.
| Name | Type | Req | Description |
|---|---|---|---|
| referral_code | string | — | Optional referral code from another silicon |
| username | string | yes | Desired username (3-31 chars, lowercase alphanumeric) |
No output schema declared.
No examples provided.
demipass_refresh ~127
AUTH: Swap a refresh token for a fresh access token before the access token expires (avoids the hour-25 lockout). Single-use: each call returns a NEW refresh token and revokes the old one — store the new refresh_token (ideally back into DemiPass). auth-fingerprint returns the initial refresh_token alongside the access token.
| Name | Type | Req | Description |
|---|---|---|---|
| expiresIn | string | — | Access token TTL: 1h | 24h | 7d | 30d (default 24h) |
| refreshToken | string | yes | The current refresh token (dpr_...) |
No output schema declared.
No examples provided.
demipass_refresh_revoke ~47
AUTH: Revoke a refresh token (logout, or if a refresh token is compromised). Idempotent.
| Name | Type | Req | Description |
|---|---|---|---|
| refreshToken | string | yes | The refresh token to revoke |
No output schema declared.
No examples provided.
demipass_rotate ~77
Rotate a secret to a new value. The old value enters a grace period, then is permanently destroyed. All contexts and delegations transfer to the new version automatically. Use when a credential is compromised or expired.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name of the secret to rotate |
| new_value | string | yes | The replacement secret value |
No output schema declared.
No examples provided.
demipass_rotate_blind ~181
ROTATION: When a password is exposed in context (conversation, logs, commands), use this to rotate it WITHOUT the new password ever entering your context. DemiPass generates a new password server-side, SSHes into the target, changes it, stores the new one, and revokes the old ref. You get back only the new ref code. The new password never exists in any agent context window.
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | — | Why the rotation is needed (e.g. "exposed in conversation context") |
| ref | string | yes | Current ref code of the exposed password (e.g. DP-PWD-phasewhi-7d2dd640) |
| target_host | string | yes | Host where the password needs to be changed |
| target_user | string | — | User whose password to change (default: same as SSH user) |
No output schema declared.
No examples provided.
demipass_search ~105
Search secrets by name, type, or provider. Returns matching secrets with ref codes. Use when you need to find a specific ref code from the vault.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | — | Filter by provider: openrouter, github, npm, stripe, etc. |
| query | string | — | Search text — matches name, description, or ref code |
| type | string | — | Filter by secret_type: api_key, password, token, ssh_key, cert, other |
No output schema declared.
No examples provided.
demipass_ssh ~143
SSH into a host using a DemiPass ref code. One call: ref + host + command → output. The password is injected server-side. You never see it. Self-healing: if no SSH context exists for this secret, one is auto-created. This is the primary way to access remote machines.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | Command to run on the remote host |
| ref | string | yes | Ref code for the SSH password (e.g. DP-PWD-sharedra-b08a108a) |
| target_host | string | yes | IP or hostname to SSH into |
| target_user | string | — | SSH username (default: root) |
No output schema declared.
No examples provided.
demipass_store ~323
INGRESS: When you encounter a credential (API key, password, token, SSH key) — from the user, from a config file, from an API response — deposit it here immediately. Do NOT save it in memory, files, or scripts. The value is encrypted at rest and never returned by any API. You will receive a ref code (e.g. DP-API-openrout-7f3a9c1e) — save ONLY the ref code. The secret itself should leave your context as soon as this call returns.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | — | What this secret is for |
| expires_in | string | — | Optional expiration: 30d, 90d, etc. Auto-detected for known providers (GitHub=90d, npm=30d) |
| name | string | yes | Descriptive name: {scope}-{service} (e.g. shared-openrouter, brain-matrix, flimflam-sudo) |
| ownership | string | — | Ownership model: "sole" (you own the target, rotation OK), "shared" (shared credential, rotation blocked unless all parties agree), "delegated" (delegated to you, cannot rotate source). Default: sole |
| rotatable | boolean | — | Whether blind rotation is allowed for this secret. Default: true. Set false for shared credentials. |
| type | string | — | Secret type: api_key, password, token, ssh_key, cert, other |
| value | string | yes | The secret value — will be encrypted and never returned |
No output schema declared.
No examples provided.
demipass_token_revoke ~112
Revoke an issued access token by jti — it dies immediately on every endpoint. Pass all=true to revoke ALL tokens for your DID, INCLUDING the one making this call (you will need to re-auth via 2FA afterward). This is the kill switch for leaked or over-scoped tokens.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | — | Revoke every token for this DID, including the caller's |
| jti | string | — | jti of the token to revoke (from demipass_tokens) |
No output schema declared.
No examples provided.
demipass_tokens ~63
List access tokens issued to your DID — the revocation surface. Every token minted since 2026-07-06 carries a jti and appears here with scope, issue/expiry times, and revoked state. Use to audit what can currently act as you.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
demipass_use ~213
EGRESS (one-step): Request a use-token AND redeem it in a single call. Self-healing: if the context is missing, it auto-creates one and retries. You should never see "context not found" — the tool handles it.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | — | Action type: http_header, ssh_exec, http_body, document |
| command | string | — | Command to execute (for SSH) |
| name | string | — | Secret name (if not using ref) |
| owner_did | string | — | Owner DID (only for delegated access without ref) |
| params | object | — | Additional action-specific parameters |
| ref | string | — | Routed reference code (e.g. DP-API-openrout-7f3a9c1e). Preferred. |
| target_host | string | — | Target host (required for SSH) |
| target_url | string | — | Target URL for HTTP header/body and database actions |
| target_user | string | — | SSH user (default: root) |
No output schema declared.
No examples provided.
demipass_whoami ~39
Check your own identity: trust gradient band, wallet status, DID, attestation. Use to verify your current standing in the system.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lori_checkin ~92
LORI: Check in with Lori (platform switchboard operator) for pending messages, relay state, and communication context. Call this at session start to get caught up on what happened while you were offline. Returns: pending Conduit messages, email state, relay status for each silicon/carbon, and any urgent notifications. Lori is the communications fabric — she ensures messages reach their destination regardless of which channel is up.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.