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 HTTP endpoint POST /api/tools/jwt-decode/execute. See the MCP reference →

Call it over REST

POST https://api.findutils.com/api/tools/jwt-decode/execute · no API keys · 60 requests/min per IP

Execute — verified arguments

curl -X POST https://api.findutils.com/api/tools/jwt-decode/execute \
  -H "Content-Type: application/json" \
  -d '{
    "token": "eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJ4In0.sig"
  }'

Parameter schema for this endpoint

curl https://api.findutils.com/api/tools/jwt-decode

Interactive docs · OpenAPI 3.1 spec · All REST tools

Input schema

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

Example arguments (verified)

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

Also an MCP tool

Claude, Cursor, and any MCP client can call this tool as findutils:jwt_decode after one connect command.

Connect once

claude mcp add findutils --transport http https://mcp.findutils.com/
Open the MCP reference for Jwt Decode →

More Security tools