How to Use the Deterministic JWT Inspector MCP in Claude Code

Q: How do I add the Deterministic JWT Inspector MCP Server to my Claude Code CLI?

Run claude mcp add --transport http deterministic-jwt-inspector -- in your terminal. This adds the server to your /.claude.json configuration file instantly.

Q: Can I use this tool to inspect tokens with missing expiration claims?

Yes, the tool decodes the entire payload even if the exp claim is missing. It will simply report that expiration metadata is unavailable while still showing all other claims.

Decode JWT claims and check expiration directly from your terminal using Claude Code and standard UNIX pipes.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Deterministic JWT Inspector MCP to Claude Code

Create your Vinkius account to connect Deterministic JWT Inspector to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Deterministic JWT Inspector with Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Terminal-Fast Token Decoding

The `inspect_jwt` tool decodes JWT headers and payloads from raw stdin or command arguments. This MCP server decodes JWT headers and payloads instantly so your Claude Code agent can inspect token structures without leaving the terminal interface. This eliminates the need to pipe tokens to insecure web decoders or write custom node scripts. The CLI agent gets clean JSON output containing the exact payload claims and header parameters.

Scriptable Expiry Checks via Claude Code

The `inspect_jwt` tool calculates token lifetime metrics by analyzing the `exp` claim. It outputs the remaining active duration in seconds, allowing your agent to diagnose expired credentials in your shell. Claude Code uses this to automate CI/CD pipeline troubleshooting. When a deployment script fails due to an auth error, the agent inspects the environment token and reports the exact expiration status.

Keyless Diagnostics for DevOps

The `inspect_jwt` tool requires zero public keys or cryptographic secrets to parse token contents. It isolates the decoding step, making it a safe choice for inspecting tokens of unknown origin. This allows your terminal agent to inspect tokens during incident response without hunting for JWKS endpoints. It reads the token anatomy safely, letting you debug configuration drift in production environments.

Setup guide

Set up Deterministic JWT Inspector MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see deterministic-jwt-inspector-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Deterministic JWT Inspector transactions." It will automatically discover and invoke the available Deterministic JWT Inspector tools.

Terminal

claude mcp add --transport http deterministic-jwt-inspector-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Deterministic JWT Inspector MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

{
  "mcpServers": {
    "deterministic-jwt-inspector-mcp": {
      "type": "url",
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by jwt-inspector. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Deterministic JWT Inspector now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Deterministic JWT Inspector MCP in Claude Code

You can feed raw token strings directly to Claude Code in your terminal. The agent will automatically invoke the `inspect_jwt` tool to decode the claims and print the formatted JSON.

No, this MCP server intentionally skips signature verification to allow rapid debugging without keys. Do not use it to authenticate users or authorize terminal commands.

Run `claude mcp add --transport http deterministic-jwt-inspector -- ` in your terminal. This adds the server to your ~/.claude.json configuration file instantly.

Yes, the tool decodes the entire payload even if the `exp` claim is missing. It will simply report that expiration metadata is unavailable while still showing all other claims.

The server processes token strings locally within an isolated, ephemeral V8 sandbox. No token data is logged, cached, or transmitted externally, ensuring your sensitive auth claims remain strictly within your local terminal session.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript