What it does
The server exposes one tool, security_decode_jwt, which decodes a JWT and returns its full header, payload, claims, expiration status and signature algorithm. It does not verify the signature, so the output shows what a token contains but cannot confirm that the token is authentic.
The tool suits debugging authentication problems, inspecting token claims before making authenticated API calls, and checking whether a token has expired and needs refreshing. Base64 encoding, hashing and password analysis are handled by separate tools in the same catalogue.
The tool takes one parameter, token, in header.payload.signature format. Each call is paid over x402 in USDC on Base L2, so no API key or signup is needed, but the client must be x402-aware so it can handle the payment challenge and retry. The server is part of the klymax402 marketplace of 100 x402 micropayment APIs and is released under the MIT licence.
Limitations and requirements
The tool does not verify JWT signatures, so decoded contents are not proof of authenticity. Each call requires an x402-aware client and a wallet able to sign USDC payments on Base L2.
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
JWT Decoder API
Decode JWT tokens — inspect header, payload, claims, expiry. x402 micropayment.
v1.1.0As shown on registry.modelcontextprotocol.io when we last read it