Base64 Codec API MCP Server
io.github.Br0ski777/base64-codec
answering
Base64 Codec API is answering right now. Last checked 1 min ago. It exposes 1 tools. Last commit 18 Jul 2026.
Encode/decode base64 and URL-safe base64. x402 micropayment.
Uptime history
39 hours of history
39 hours agonow
100.0%
Uptime 24h
92 of 92 checks
1
Tools
read from the server
25 ms
Response time
average over 24h
0
Stars
last commit 18 Jul 2026
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.
run in your terminal
claude mcp add base64-codec --transport http https://base64-codec.api.klymax402.com/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"base64-codec": {
"url": "https://base64-codec.api.klymax402.com/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.base64-codec]
url = "https://base64-codec.api.klymax402.com/mcp".cursor/mcp.json
{
"mcpServers": {
"base64-codec": {
"url": "https://base64-codec.api.klymax402.com/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"base64-codec": {
"url": "https://base64-codec.api.klymax402.com/mcp"
}
}
}Available tools 1
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
utility
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.
1. result -- the encoded or decoded string
2. action -- whether encode or decode was performed
3. inputLength -- character count of the input
4. outputLength -- character count of the output
5. urlSafe -- boolean indicating if URL-safe variant was used
Example output: {"result":"SGVsbG8gV29ybGQ=","action":"encode","inputLength":11,"outputLength":16,"urlSafe":false}
Use this FOR 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.
Do NOT use for hashing -- use crypto_generate_hash instead. Do NOT use for JWT decoding -- use security_decode_jwt instead. Do NOT use for URL slug creation -- use text_generate_slug instead.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://base64-codec.api.klymax402.com/mcp | sse | answering | 22 ms | 1 min ago |
Base64 Codec API — questions
Answers built from our own checks of this server.
What can Base64 Codec API do?
It exposes 1 tools, read directly from the server on our last check. Among them: utility_encode_base64. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Base64 Codec API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 25 ms. The bar chart above shows every period we have measured.
How do I connect Base64 Codec API?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Base64 Codec API need an API key?
No. Base64 Codec API completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Base64 Codec API?
It answers our handshake in 25 ms on average, which is faster than 99% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Base64 Codec API open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.