GenPark Secure Secret Token Redactor

io.github.alphaparkincPublished by GitHub account alphaparkincv1.0.1Updated Nov 7, 2026

High-speed regex and entropy-based scanner redacting API keys, JWT tokens, and credentials

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Local MCP server that scans text with regex and entropy rules to redact API keys, JWT tokens and other credentials before an assistant handles them.

What you can do
  • Scan text for secrets using regex patterns and entropy heuristics.
  • Detect and redact API keys, JWT tokens and credentials.
  • Return text with sensitive values masked so it can be shared or processed further.
  • No tool list is published, so the exact operations are not documented.
When to use it
Useful when you want an assistant to clean logs, config snippets, prompts or pasted text of secrets before storing, sharing or sending them elsewhere. It fits a local, desktop-only workflow where redaction should happen on the user's machine.
Requirements
Runs as a local process on the user's machine, installed from an MCPB package; desktop client only, no web execution. No authentication, environment variables or headers are declared.
Before you install
Redaction is heuristic (regex plus entropy), so it can miss unusual secret formats or over-redact ordinary high-entropy strings; review output before relying on it. The server itself is local and declares no credentials, but any text you pass to it still reaches the assistant and client.

Installation

In SourceWeft

  1. Open GenPark Secure Secret Token Redactor 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 started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

1
  1. v1.0.1LatestOct 24, 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.