What it does
The server exposes one tool, utility_encode_base64, which takes a data string and an action of either 'encode' or 'decode' (encode by default). It returns the result string together with encoding metadata. It supports standard and URL-safe base64 variants.
The publisher's documentation points to three uses: embedding binary data in JSON, preparing email attachments (MIME), and decoding base64 tokens returned by APIs. It recommends using the tool before sending data through channels that accept only ASCII. For hashing, JWT decoding and URL slug creation, the documentation directs users to other tools.
Setup means adding the server to an MCP client configuration; the documentation lists Claude Desktop, Cursor and ElizaOS as examples. Each call is priced at $0.003 and paid in USDC on Base L2 via the x402 protocol, using a client that handles the HTTP 402 payment cycle, such as @x402/fetch or x402-agent-tools. No API key or signup is required. The license is MIT.
Limitations and requirements
Each call costs $0.003 in USDC on Base L2, so the client needs a wallet holding USDC on that network. The client must be x402-aware to handle the payment cycle. The tool covers only encoding and decoding and is not intended for hashing, JWT decoding or slug generation.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
Base64 Codec API
Encode/decode base64 and URL-safe base64. x402 micropayment.
v1.1.0As shown on registry.modelcontextprotocol.io when we last read it