# Jwt Decode — MCP tool `findutils:jwt_decode`

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

- Category: security
- MCP server: https://mcp.findutils.com/ (Streamable HTTP, no API keys, 120 req/min per IP)
- REST endpoint: POST https://api.findutils.com/api/tools/jwt-decode/execute (no API keys, 60 req/min per IP)
- Reference page: https://findutils.com/mcp/jwt-decode/
- Same tool on the other surface: https://findutils.com/api/jwt-decode/

## Connect

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

Claude Desktop (`claude_desktop_config.json`):

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

## Call the tool (verified example)

```bash
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):

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

## Also a REST endpoint

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

# Parameter schema
curl https://api.findutils.com/api/tools/jwt-decode
```

Full REST reference: https://findutils.com/api/jwt-decode/ · OpenAPI 3.1 spec: https://findutils.com/api/openapi.json

---
Full catalog: POST https://mcp.findutils.com/ with method `tools/list` · https://findutils.com/mcp/ · https://findutils.com/llms.txt