Password Strength Mcp

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

Score password strength locally with the zxcvbn algorithm. No network and no key.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

A local MCP server that scores password strength with the zxcvbn algorithm, letting an assistant evaluate candidate passwords offline.

What you can do
  • Score a password's strength using the zxcvbn algorithm.
  • Run entirely on the local machine, with no network calls and no API key.
  • No individual tools are documented in the manifest, so the exact operations are not listed.
When to use it
Useful when an assistant needs to judge how strong a password or passphrase is, for example while drafting password policies, reviewing example credentials, or explaining why a password is weak.
Requirements
Runs as a local stdio process installed from the npm package password-strength-mcp, so Node.js and an MCP client that supports local servers are needed. Desktop only; no authentication, environment variables or headers are declared.
Before you install
Passwords given to the assistant are passed to this local process for scoring; avoid submitting real credentials you want to keep secret. No network access or credentials are declared, so nothing is sent to third parties.

Installation

In SourceWeft

  1. Open Password Strength 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.