detect_base64LABSCO SUMMARY
Detecting the encoded runs is the useful part — decoding base64 was never the hard bit.
Anyone can decode a blob they have already identified. What costs time is noticing that a field in a log line, a JWT segment or a config value is encoded at all, and doing it without mangling the surrounding text. Handling that in place means you read the whole thing once rather than copying fragments back and forth. Note the repository name suggests signing rather than encoding; the README is the accurate description.
What it is
A small utility that scans text for base64-encoded runs, decodes them, and substitutes the result — leaving everything that is not base64 untouched.
What you get
Automatic detection and in-place decoding of base64 within a body of text.
Requirements
Python, run as a module. Documentation is in Chinese.
Setup effort
Build from source — get the source, then follow the steps on this page and add the configuration for your client
USE CASES
01
Reading a log full of encoded fields
Decoded in place, the rest left alone.
02
Opening up a token
See what the encoded segments actually say.
2 tools
Listed in project docs. Your client may show a different list.
decode_base64BEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
python3 on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Get the source, then follow the steps on this page and add the configuration for your client. This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/Forward333/mcp-sigstore
cd mcp-sigstore
pip install -e .MCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"base64-autodecode": {
"command": "python3",
"args": [
"-m",
"mcp_content_integrity.server"
]
}
}
}
