delete_secret

7 registry entries were observed exposing a tool named delete_secret — 7 of them as a privileged capability (a name matching exec / write / delete keywords).

Spelled delete_secret, delete-secret in the wild — all one tool for the purposes of this page.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 8,491 of 26,663 scannable entries (32%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

  1. @1claw/mcpprivileged
    trust 60/100 · BMCP serverobserved · static extraction
    HSM-backed vault secrets for AI agents (JIT fetch) plus prompt-injection and threat scanning.
  2. @i4ctime/q-ringprivileged
    trust 60/100 · BMCP serverobserved · static extraction
    Quantum keyring for AI coding tools — Cursor, Kiro, Claude Code. Secrets, superposition, entanglement, MCP.
  3. @keyid/agent-kitprivileged
    trust 60/100 · BMCP serverobserved · static extraction
    KeyID MCP server for agent email, SMS, OTP/TOTP, and signup verification
  4. io.github.aarifmms/keyblindprivileged
    trust 60/100 · BMCP serverobserved · static extraction
    Encrypted secrets vault for AI agents — secrets resolved at runtime, never seen by LLMs.
  5. io.github.juanisidoro/securecodeprivileged
    trust 60/100 · BMCP serverobserved · static extraction
    Secrets vault for Claude Code with audit logs, access rules, and AES-256 encryption.
  6. io.github.KeyID-AI/keyidprivileged
    trust 60/100 · BMCP serverobserved · static extraction
    Signup sessions, browser continuity, email, SMS, and OTP/TOTP infrastructure for AI agents.
  7. wisewall-mcpprivileged
    trust 60/100 · BMCP serverobserved · static extraction
    Manage WiseWall sites from an AI coding assistant — deploy, configure DNS, secrets, and plans.

All indexed toolsSearch the registry for delete_secret