Regex Mcp

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

Test, describe, and validate regular expressions locally. No network and no key.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server for testing, describing and validating regular expressions, letting an assistant help with regex work.

What you can do
Test regular expressions: let the assistant match and validate patterns locally. Describe regular expressions: help explain what a pattern means and how it behaves. Validate regular expressions: check whether a pattern is valid. Everything runs locally with no network access or API key.
When to use it
Use it when you want the assistant to quickly test, explain or validate a regular expression during development without opening a separate tool or pasting patterns into an online service. Suited to local, offline regex work.
Requirements
Runs as a local process from an npm package, so it needs a Node.js runtime; desktop only and not executable in a browser. No network access, API key or environment variables required.

Installation

In SourceWeft

  1. Open Regex 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.