Server data from the Official MCP Registry
Decode JWT tokens — inspect header, payload, claims, expiry. x402 micropayment.
Decode JWT tokens — inspect header, payload, claims, expiry. x402 micropayment.
Remote endpoints: sse: https://jwt-decoder.api.klymax402.com/mcp
Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. Trust signals: trusted author (135/139 approved); 6 highly-trusted packages.
1 tool verified · Open access · No issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"io-github-br0ski777-jwt-decoder": {
"url": "https://jwt-decoder.api.klymax402.com/mcp"
}
}
}From the project's GitHub README.
Decode and inspect JWT tokens without verification. Extracts header, payload, claims, expiry, and signature algorithm. 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.
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"jwt-decoder": {
"url": "https://jwt-decoder.api.klymax402.com/mcp"
}
}
}
curl -X POST "https://jwt-decoder.api.klymax402.com/api/decode" \
-H "Content-Type: application/json" \
-d '{"token":"..."}'
# -> 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.
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
security_decode_jwt | POST | /api/decode | $0.001 | Decode a JWT token without signature verification |
security_decode_jwtUse this when you need to decode and inspect a JWT token without verifying its signature. Returns the full header, payload, and expiration status.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
token | string | yes | The JWT token to decode (format: header.payload.signature) |
Example response:
{"header":{"alg":"RS256","typ":"JWT"},"payload":{"sub":"user123","exp":1720000000},"issuedAt":"2025-01-01T00:00:00Z","expiresAt":"2025-07-03T00:00:00Z","isExpired":false}
When to use: debugging authentication issues, inspecting token claims before API calls, or verifying token expiry. Use this BEFORE making authenticated requests to check if a token needs refreshing.
Not for: hashing data (use crypto_generate_hash), base64 encoding/decoding (use utility_encode_base64), password analysis (use security_check_password).
eip155:8453)100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
MIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.