# JWT Tools (oci · ghcr.io/basitalisandhu/mcp-jwt-tools)

Decode JWTs without verifying, flag risky algorithms and claims, verify HS256 or RS256 with a key.

- Trust score: 49/100 (low)
- Change this week: +29
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-16

## Components

- oci · `ghcr.io/basitalisandhu/mcp-jwt-tools`: 49/100 (this document), [markdown](https://verifymcp.io/servers/basitalisandhu-mcp-jwt-tools/ghcr-io-basitalisandhu-mcp-jwt-tools.md), [page](https://verifymcp.io/servers/basitalisandhu-mcp-jwt-tools/ghcr-io-basitalisandhu-mcp-jwt-tools)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/basitalisandhu/mcp-jwt-tools`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-16.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to basitalisandhu/dev-mcp-servers).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 709 tokens (~236/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 2 categories.** Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the JWT Tools MCP server?

JWT Tools runs locally as a container image, launched with docker run --rm -i ghcr.io/basitalisandhu/mcp-jwt-tools:0.2.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add basitalisandhu-mcp-jwt-tools -- docker run --rm -i ghcr.io/basitalisandhu/mcp-jwt-tools:0.2.1
```

### Cursor

```json
{
  "mcpServers": {
    "basitalisandhu-mcp-jwt-tools": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/basitalisandhu/mcp-jwt-tools:0.2.1"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "basitalisandhu-mcp-jwt-tools": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/basitalisandhu/mcp-jwt-tools:0.2.1"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add basitalisandhu-mcp-jwt-tools -- docker run --rm -i ghcr.io/basitalisandhu/mcp-jwt-tools:0.2.1
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "basitalisandhu-mcp-jwt-tools": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/basitalisandhu/mcp-jwt-tools:0.2.1"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  basitalisandhu-mcp-jwt-tools:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/basitalisandhu/mcp-jwt-tools:0.2.1"]
```

### Netclaw

```json
{
  "McpServers": {
    "basitalisandhu-mcp-jwt-tools": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/basitalisandhu/mcp-jwt-tools:0.2.1"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "basitalisandhu-mcp-jwt-tools": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/basitalisandhu/mcp-jwt-tools:0.2.1"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-14 (score 49, +29)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 80

### 2026-10-13 (score 20, 0)

- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-12 (score 20, 0)

- [functional] Package version: 0.1.1 → 0.2.0

### 2026-10-07 (score 20)

First indexed and scored.

## MCP tools (3)

### `decode_jwt` (~203 tokens)

Decode a JWT without verifying it

Base64url-decode the header and payload of a JWS compact token and report findings. The signature is NOT verified; the output says so and the claims must be treated as unverified. Findings cover: alg none or missing, empty signature, jku/x5u/jwk in the header, expired, not yet valid, missing exp/iat/aud/iss/sub/jti, lifetime above max_ttl_hours (default 24), timestamps given in milliseconds, and claims whose names suggest secrets. Timestamps are also returned as ISO 8601. JWE (encrypted, five-part) tokens are rejected.

Input parameters:

- `max_ttl_hours` (number): Lifetime threshold for the long-ttl finding, in hours. Default 24.
- `now` (integer): Unix seconds to evaluate exp and nbf against. Default: current time.
- `token` (string, required): Compact JWS token (header.payload.signature). A leading 'Bearer ' is ignored.

### `verify_jwt` (~242 tokens)

Verify a JWT signature and claims

Verify the signature of a JWS compact token with the supplied key for exactly the given algorithm, then check exp (required), nbf, and optionally aud and iss. HS256/HS384/HS512 take the shared secret as key; RS256/RS384/RS512 take a PEM public key, certificate or private key. A token whose header alg differs from algorithm fails without any cryptographic check, which blocks algorithm-confusion attacks. Returns valid (both signature and claims), signature_valid, claims_valid and the reasons.

Input parameters:

- `algorithm` (string, required): The one algorithm the verifier accepts.
- `audience` (string): Required aud value (matches a string aud or one element of an array aud).
- `clock_tolerance_seconds` (integer): Leeway for exp and nbf. Default 0.
- `issuer` (string): Required iss value.
- `key` (string, required): Shared secret (HS*) or PEM-encoded key (RS*).
- `now` (integer): Unix seconds for time checks. Default: current time.
- `token` (string, required): Compact JWS token (header.payload.signature). A leading 'Bearer ' is ignored.

### `sign_test_jwt` (~147 tokens)

Sign a JWT for test fixtures

Create a signed JWS compact token from a claims object for use in tests and local development. iat is set to now unless the payload supplies one; exp is set from expires_in_seconds when given. HS* algorithms use key as the shared secret; RS* algorithms need a PEM private key. Returns the token and the final header and claims.

Input parameters:

- `algorithm` (string, required)
- `expires_in_seconds` (integer)
- `key` (string, required)
- `now` (integer): Unix seconds used for iat and exp. Default: current time.
- `payload` (object, required): Claims to sign, for example {"sub":"user-1","aud":"api"}.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/basitalisandhu-mcp-jwt-tools/ghcr-io-basitalisandhu-mcp-jwt-tools#diagnostics

## Score history

- 2026-10-16: 49
- 2026-10-15: 49
- 2026-10-14: 49
- 2026-10-13: 20
- 2026-10-12: 20
- 2026-10-07: 20

## Common questions

### What is the JWT Tools MCP server?

JWT Tools is an MCP server listed in the public MCP registry as io.github.basitalisandhu/mcp-jwt-tools. Decode JWTs without verifying, flag risky algorithms and claims, verify HS256 or RS256 with a key. This page covers its container image (ghcr.io/basitalisandhu/mcp-jwt-tools).

### Is the JWT Tools MCP server safe to use?

JWT Tools scores 49 out of 100 on VerifyMCP. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the JWT Tools MCP server expose?

JWT Tools exposes 3 tools: decode_jwt, verify_jwt, sign_test_jwt. Their descriptions and schemas cost roughly 592 tokens of context every time the server is loaded.

### Is the JWT Tools MCP server still maintained?

JWT Tools is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the JWT Tools MCP server under?

JWT Tools declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- GitHub Container Registry: https://ghcr.io/basitalisandhu/mcp-jwt-tools
- Repository: https://github.com/basitalisandhu/dev-mcp-servers
- Website: https://basitalisandhu.github.io/dev-mcp-servers/
- Changelog RSS feed: https://verifymcp.io/servers/basitalisandhu-mcp-jwt-tools/ghcr-io-basitalisandhu-mcp-jwt-tools.xml
- Changelog JSON feed: https://verifymcp.io/servers/basitalisandhu-mcp-jwt-tools/ghcr-io-basitalisandhu-mcp-jwt-tools.json
- HTML version of this page: https://verifymcp.io/servers/basitalisandhu-mcp-jwt-tools/ghcr-io-basitalisandhu-mcp-jwt-tools