set_api_key

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

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. @oktopeak/intakeq-mcp
   trust 60/100 · BMCP serverobserved 2026-08-12 · static extraction
   IntakeQ/PracticeQ MCP connector with HIPAA §164.312(b) audit logging on every PHI read/write
2. io.github.ClawCall-Dev/clawcall
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   MCP server for ClawCall — AI-powered US phone calling.
3. io.github.donovanh/mcp-server
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   MCP server for Lightning Tools — pay-per-call AI tools via Bitcoin Lightning
4. z-zero-mcp-server
   trust 60/100 · BMCP serverobserved 2026-07-23 · static extraction
   Payments for AI agents: gasless USDC on Base + JIT single-use virtual cards, PAN never in context.

All indexed toolsSearch the registry for set_api_key