base64_decode

6 registry entries were observed exposing a tool named base64_decode — 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. app.toolsnap/toolsnap-mcp
   trust 60/100 · BMCP serverobserved 2026-08-10 · static extraction
   Deterministic AI agent microtools, no accounts/API keys. fetch_extract: 98% token cut. 38 tools.
2. devutils-mcp-server
   trust 60/100 · BMCP serverobserved 2026-08-14 · static extraction
   36 local developer utilities for AI agents. Hash, encoding, UUID, JWT, JSON, network, text.
3. io.github.kira-autonoma/devtools
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   23 developer utilities — base64, JWT, UUID, hash, QR, regex, timestamps. No API keys.
4. io.github.ofershap/devutils
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   Developer utilities MCP: base64, UUID, hash, JWT decode, cron, timestamps.
5. io.github.pipeworx-io/base64
   trust 60/100 · BMCP serverobserved 2026-08-12 · static extraction
   Encoding MCP — Base64 / Base64URL / Base32 / Hex.
6. io.github.pipeworx-io/httpbin
   trust 60/100 · BMCP serverobserved 2026-06-14 · static extraction
   httpbin echo: GET/POST inspection, status codes, delay, UUID, base64. Debug aid.

All indexed toolsSearch the registry for base64_decode