url_encode

2 registry entries were observed exposing a tool named url_encode — 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. trust 60/100 · BMCP serverobserved · static extraction
    36 local developer utilities for AI agents. Hash, encoding, UUID, JWT, JSON, network, text.
  2. trust 60/100 · BMCP serverobserved · static extraction
    23 developer utilities — base64, JWT, UUID, hash, QR, regex, timestamps. No API keys.

All indexed toolsSearch the registry for url_encode