Jwt Tools Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026

Decode and verify JSON Web Tokens locally. No network and no key.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant decode and verify JSON Web Tokens locally, without network access or signing keys.

What you can do
This MCP server provides tools for working with JSON Web Tokens on the local machine. It can decode a JWT so its header and payload claims are readable, and it can verify a token's signature. According to the registry description, it works entirely offline and does not require a key.
When to use it
Useful when an assistant needs to inspect a JWT's contents or check whether a token's signature is valid during debugging, development, or troubleshooting. It is meant for local, offline token inspection rather than issuing or managing tokens.
Requirements
Runs as a local process on the user's machine, installed from the npm package jwt-tools-mcp over stdio. No environment variables, headers, accounts, or API keys are declared. Desktop only; not available as a web executable.
Before you install
The registry description states it needs no network and no key, so it should not be given secrets or signing keys. Tokens themselves can contain sensitive claims, so be careful about which tokens you paste in and where the decoded output is stored or shared.

Installation

In SourceWeft

  1. Open Jwt Tools Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.