get_secret

6 registry entries were observed exposing a tool named get_secret — none of them flagged as a privileged capability.

Spelled get_secret, get-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,470 of 26,658 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/mcp
   trust 60/100 · BMCP serverobserved 2026-07-16 · static extraction
   HSM-backed vault secrets for AI agents (JIT fetch) plus prompt-injection and threat scanning.
2. @i4ctime/q-ring
   trust 60/100 · BMCP serverobserved 2026-08-09 · static extraction
   Quantum keyring for AI coding tools — Cursor, Kiro, Claude Code. Secrets, superposition, entanglement, MCP.
3. @keyid/agent-kit
   trust 60/100 · BMCP serverobserved 2026-08-15 · static extraction
   KeyID MCP server for agent email, SMS, OTP/TOTP, and signup verification
4. io.github.AInoAKARI/keymaster-mcp
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   Read-only runtime secret retrieval from HashiCorp Vault via Keymaster for autonomous AI agents.
5. io.github.juanisidoro/securecode
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   Secrets vault for Claude Code with audit logs, access rules, and AES-256 encryption.
6. io.github.KeyID-AI/keyid
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   Signup sessions, browser continuity, email, SMS, and OTP/TOTP infrastructure for AI agents.

All indexed toolsSearch the registry for get_secret