Jwt Decode

Security REST API MCP

Decode a JWT header + payload. Does NOT verify the signature — validation must happen at the token source.

This page documents the MCP tool findutils:jwt_decode. See the REST reference →

Call it over MCP

Tool name findutils:jwt_decode · no API keys · 120 requests/min per IP

Claude Code

claude mcp add findutils --transport http https://mcp.findutils.com/

Claude Desktop — claude_desktop_config.json

{
  "mcpServers": {
    "findutils": {
      "url": "https://mcp.findutils.com/"
    }
  }
}

Raw JSON-RPC (any MCP client) — verified example

curl -X POST https://mcp.findutils.com/ \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "jwt_decode",
      "arguments": {
        "token": "eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJ4In0.sig"
      }
    }
  }'

Input schema

Argument Type Required Description
token string yes JWT token (3 dot-separated base64url segments).

Example arguments (verified)

{
  "token": "eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJ4In0.sig"
}

Also a REST endpoint

The same tool answers plain HTTP at POST /api/tools/jwt-decode/execute — no key, 60 requests/min.

Open the REST reference for Jwt Decode →

More Security tools