mcpField
B
Base64 Codec X402

Base64 Codec X402

Remote
github.comDeveloper Tools0Updated 8w ago

About Base64 Codec X402

Base64 Codec X402 is an API and MCP server for encoding text as Base64 or decoding Base64 to text, with standard and URL-safe variants and metadata. Calls use x402 micropayments in USDC on Base L2, without an API key or signup.

Key features

  1. 01Encode and decode Base64
  2. 02Standard and URL-safe variants
  3. 03Return encoding metadata
  4. 04x402 pay-per-call access

Use cases

  1. 01Embed binary data in JSON
  2. 02Prepare email attachments in MIME
  3. 03Decode Base64 tokens from APIs

MCP support

Provides the `utility_encode_base64` tool to MCP clients for encoding or decoding data and returning metadata. The remote endpoint is configured in the MCP client.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://base64-codec.api.klymax402.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

Base64 Codec API

MCP Server x402 License: MIT

Encode text to base64 or decode base64 to text. Supports standard and URL-safe variants with metadata. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

{
  "mcpServers": {
    "base64-codec": {
      "url": "https://base64-codec.api.klymax402.com/mcp"
    }
  }
}

Quickstart -- HTTP (x402)

curl -X POST "https://base64-codec.api.klymax402.com/api/encode" \
  -H "Content-Type: application/json" \
  -d '{"data":"..."}'
# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
utility_encode_base64POST/api/encode$0.003Encode or decode base64 data
utility_encode_base64

Use this when you need to encode text to base64 or decode base64 back to plaintext. Returns the result string with encoding metadata.

Parameters

NameTypeRequiredDescription
datastringyesThe data to encode or decode
actionstringnoAction: 'encode' or 'decode' (default: encode)

Example response:

{"result":"SGVsbG8gV29ybGQ=","action":"encode","inputLength":11,"outputLength":16,"urlSafe":false}

When to use: embedding binary data in JSON, preparing email attachments (MIME), or decoding base64 tokens from APIs. Use this BEFORE sending data through channels that only support ASCII.

Not for: hashing (use crypto_generate_hash), JWT decoding (use security_decode_jwt), URL slug creation (use text_generate_slug).

Example agent prompts

  • "Encode text to base64 or decode base64 back to plaintext"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.