execute_action

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

Spelled execute_action, execute-action 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. @peekdev/mcpprivilegedverified
    trust 85/100 · AMCP serverobserved · static extraction
    local-first browser-session forensics + repro for AI coding agents. peek's native messaging host + stdio MCP server — owns ~/.peek/sessions.
  2. dev.forgesworn/brayprivilegedverified
    trust 85/100 · AMCP serverobserved · static extraction
    Trust-aware Nostr for AI agents -- 235 tools covering social, DMs, zaps, trust, and identity
  3. trust 85/100 · AMCP serverobserved · static extraction
    Full Odoo access for AI agents via MCP: CRUD, website, translations, attachments, workflows.
  4. trust 60/100 · BMCP serverobserved · static extraction
    Let your AI send invoices and take payment — card or ACH. Free.

All indexed toolsSearch the registry for execute_action