mcpbeat Sign in

JWT Decoder API MCP Server

not responding

JWT Decoder API is listed as active in the registry but did not answer our last check. It exposes 1 tools. Last commit 2 Sep 2026.

Decode JWT tokens — inspect header, payload, claims, expiry. x402 micropayment.

Uptime history 51 days of history · worst day 0%
51 days agonow
0.0%
Uptime 24h
0 of 92 checks
1
Tools
read from the server
176 ms
Response time
average over 24h
0
Stars
last commit 2 Sep 2026

JWT Decoder API does not always answer

Over the last week it answered 30.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add jwt-decoder --transport http https://jwt-decoder.api.klymax402.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "jwt-decoder": {
      "url": "https://jwt-decoder.api.klymax402.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.jwt-decoder]
url = "https://jwt-decoder.api.klymax402.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "jwt-decoder": {
      "url": "https://jwt-decoder.api.klymax402.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "jwt-decoder": {
      "url": "https://jwt-decoder.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.

security
security_decode_jwt
Use this when you need to decode and inspect a JWT token without verifying its signature. Returns the full header, payload, and expiration status. 1. header -- algorithm (RS256, HS256, etc.) and token type 2. payload -- all claims (sub, iss, aud, iat, exp, custom claims) 3. issuedAt -- human-readable issued date 4. expiresAt -- human-readable expiry date 5. isExpired -- boolean indicating if the token has expired Example output: {"header":{"alg":"RS256","typ":"JWT"},"payload":{"sub":"user123","exp":1720000000},"issuedAt":"2025-01-01T00:00:00Z","expiresAt":"2025-07-03T00:00:00Z","isExpired":false} Use this FOR 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. Do NOT use for hashing data -- use crypto_generate_hash instead. Do NOT use for base64 encoding/decoding -- use utility_encode_base64 instead. Do NOT use for password analysis -- use security_check_password instead.

Endpoints

URLTransportStateLatencyChecked
https://jwt-decoder.api.klymax402.com/mcp sse answering 176 ms 3 min ago

Alternatives to JWT Decoder API

same job, measured the same way
X402lint
by arden-instance

Lint an HTTP endpoint's x402 402 conformance; decode X-PAYMENT blobs; inspect a facilitator.

2 062 installs/wk local only
Bazaar MCP
by opspawn

x402 micropayment-powered developer tools: screenshots, AI analysis, PDFs, code scanning

28 installs/wk local only
x402 Web Extract
by senpi-station

Pay-per-use web extract, token prices, and wallet balances via x402 USDC micropayments.

5 tools answering
X402 MCP
by kwizzlesurp10-ctrl

Pay for HTTP APIs and charge for your own: x402 micropayments in USDC on Base.

19 tools answering
Agent Token Stripper
by goldminex

Autonomous x402 Token Stripper API settling $0.002 USDC micro-payments on Base L2.

local only
DeriveAI x402 APIs
by deriveit33z-ship-it

25 pay-per-request intelligence APIs for AI agents via x402 micropayments (USDC/Base)

25 tools answering
X402 Express
by ihen404

Express.js HTTP 402 payment middleware for AI agent micropayments

local only
Apollo Intelligence
by apolloai

36 tools: intel feeds, DeFi, crypto, OSINT, NLP, scraping, proxy. x402 micropayments.

62 installs/wk local only

JWT Decoder API — questions

Answers built from our own checks of this server.

What can JWT Decoder API do?
It exposes 1 tools, read directly from the server on our last check. Among them: security_decode_jwt. 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 JWT Decoder API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 176 ms. The bar chart above shows every period we have measured.
The registry lists JWT Decoder API as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect JWT Decoder 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 JWT Decoder API need an API key?
No. JWT Decoder 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.
Is JWT Decoder 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.