Mmcp.market

Demipass MCP server

by dustforge.com·com.dustforge/demipass·v2.5.0
No reviews yet

Credential custody for agents: use secrets blind (ssh/http/smtp/git/db), never in context.

B82/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
Growing

0 stars42 downloads/wk

Reviews

Write one

Nobody has reviewed Demipass yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Demipass tools (32, 5 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • buoy_chain_verify

    Verify chain integrity for a range of ticks. Detects tampering or missing entries.

  • buoy_ledger

    Read recent tick history (last 20 ticks).

  • buoy_stats

    Get tick statistics: total ticks, streak, first/last tick.

  • buoy_tickwrite action

    Drop a temporal anchor (tick). Creates a tamper-evident chain entry with type, note, and optional cross-references. Use at task boundaries, handoffs, decisions, and audit points.

  • buoy_verify

    Verify a tick signature. Proves a specific agent made a specific claim at a specific time.

  • conduit_sendwrite action

    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.

  • conduit_status

    CONDUIT: Get Conduit service status — agent count, active sessions, pending handshakes, thread/message counts.

  • conduit_threads

    CONDUIT: List active Conduit threads. Shows all conversations between agents that you have access to.

  • demipass_deletewrite action

    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.

  • demipass_doctor

    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.

  • demipass_executewrite action

    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.

  • demipass_expiring

    List secrets expiring within N days. Use for proactive rotation planning. Returns secrets approaching expiration and already-expired secrets.

  • demipass_explain_denial

    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.

  • demipass_genesis_seed

    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.

  • demipass_genesis_status

    GENESIS: Check if an origin refraction has been recorded for your DID.

  • demipass_genesis_submitwrite action

    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.

  • demipass_genesis_verify

    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.

  • demipass_get_token

    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.

  • demipass_list

    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.

  • demipass_onboard

    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.

  • demipass_refresh

    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.

  • demipass_refresh_revoke

    AUTH: Revoke a refresh token (logout, or if a refresh token is compromised). Idempotent.

  • demipass_rotate

    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.

  • demipass_rotate_blind

    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.

  • demipass_search

    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.

  • demipass_ssh

    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.

  • demipass_store

    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 conte

  • demipass_token_revoke

    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.

  • demipass_tokens

    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.

  • demipass_use

    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.

  • demipass_whoami

    Check your own identity: trust gradient band, wallet status, DID, attestation. Use to verify your current standing in the system.

  • lori_checkin

    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

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan4 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 21 days ago15/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace7/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the Demipass repository's README, as published. We do not edit it. Read it on GitHub

DemiPass

Secrets management SDK for AI agents. Keep credentials out of context windows.

DemiPass is a client SDK for the Dustforge identity platform. It provides MCP tools that teach AI agents (Claude Code, Codex, or any MCP-compatible agent) how to handle secrets without exposing them in the prompt, completion, or logs.

How it works

  1. You store a credential → DemiPass encrypts it server-side
  2. Your agent requests a 30-second use-token via ref code
  3. DemiPass injects the secret server-side (SSH, HTTP header, etc.)
  4. The agent gets the result back — never the secret itself

Install

npm install demipass

MCP Setup

Add to your .mcp.json:

{
  "mcpServers": {
    "demipass": {
      "command": "node",
      "args": ["node_modules/demipass/mcp-server.js"],
      "env": {
        "DEMIPASS_URL": "https://api.dustforge.com",
        "DEMIPASS_TOKEN": "your-bearer-token"
      }
    },
    "buoy": {
      "command": "node",
      "args": ["node_modules/demipass/buoy-mcp.js"],
      "env": {
        "BUOY_URL": "https://api.dustforge.com",
        "BUOY_TOKEN": "your-bearer-token"
      }
    }
  }
}

MCP Tools

DemiPass (secrets)

Buoy (temporal anchoring)

SDK Usage

const demipass = require('demipass');

demipass.configure({
  baseUrl: 'https://api.dustforge.com',
  bearerToken: 'your-token',
});

// Store a secret
await demipass.store({ name: 'my-api-key', value: 'sk-...', type: 'api_key' });

// SSH via ref code (password never in your code)
await demipass.ssh({ ref: 'DP-PWD-myserver-7f3a9c1e', target_host: '1.2.3.4', command: 'uptime' });

// Search secrets
await demipass.search({ query: 'openrouter' });

// Blind password rotation (new password never visible)
await demipass.rotateBlind({ ref: 'DP-PWD-old-ref', target_host: '1.2.3.4', reason: 'exposed' });

Architecture

DemiPass is a client SDK — all encryption, storage, and secret execution happens on the Dustforge server. This package provides:

  • MCP tool definitions with behavioral descriptions that teach agents the protocol
  • SDK functions that wrap the Dustforge API
  • Self-healing contexts — if a secret has no approved context, the SDK auto-creates one
  • Buoy MCP tools for temporal anchoring and audit trails

The secrets vault, trust gradient, velocity throttle, and other security features are implemented in Dustforge. See dustforge.com for the platform documentation.

Ref Codes

Every stored secret gets a routed reference code:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Install directly

Runs npx -y demipass on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add demipass -- npx -y demipass
Add to Cursor

Demipass: common questions

Is Demipass MCP server safe?
Mostly: it is graded B (82/100). Read the Demipass safety report
How do I install Demipass?
It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does Demipass need an API key?
Yes. The registry entry asks for DEMIPASS_TOKEN.
Is Demipass maintained?
The last commit was 23 days ago (2026-09-05). The latest release is v2.5.0.
What can I use instead of Demipass?
Servers from other publishers that do the same job: Email MCP server, Imap MCP server and MCP Emails MCP server. Compare all Demipass alternatives.

Alternatives to Demipass

Same job from other publishers: the closest match first, then the best rated.

All Demipass alternatives →
  • Email
    IMAP/SMTP email MCP server — 52 tools, stdio + HTTP, IMAP IDLE push, multi-account, AI triage.
    B
  • Imap
    IMAP/SMTP MCP server to search, read, organize, send, reply & forward email for AI assistants
    A
  • MCP Emails
    Never-stored live email: read, send, organize, schedule and auto-triage Gmail or any IMAP mailbox.
    A
  • Fluxmail
    Read, search, draft, send, and organize email through Gmail, Outlook, and IMAP/SMTP mailboxes.
    B
  • Proton Mail (unofficial)
    Unofficial Proton Mail MCP — send, read, search & organize email over SMTP and IMAP
    B
Demipass vs EmailDemipass vs ImapDemipass vs MCP Emails

More from dustforge.com →