Skip to main content
Glama
jspassgen-mcp

jspassgen-mcp

Official

Contents

Getting started

  • Install: from a clone today; npm after the first suite release

  • Requirements: Node.js floor, platforms

  • Quick Start: register the server with an MCP client

The jspassgen ecosystem

Library reference

Operational


Related MCP server: password-mcp

Install

As a JavaScript library

git clone https://github.com/sebastienrousseau/jspassgen-mcp.git
cd jspassgen-mcp
npm ci

jspassgen-mcp is a planned member of the jspassgen suite and is not on npm yet: package.json is marked private until the first suite release, planned as 0.0.22. Until then, run it from a clone as above. Once published, it will install with npm install @sebastienrousseau/jspassgen-mcp.


Requirements

  • Node.js 22 or newer (engines in package.json; CI tests 22 and 24).

  • Any platform Node.js supports. Randomness comes from Node.js crypto through jspassgen's NodeCryptoRandom adapter.

  • An MCP client that can start a local server over stdio.

  • No network access at run time.


Quick Start

{
  "mcpServers": {
    "jspassgen": {
      "command": "node",
      "args": ["/absolute/path/to/jspassgen-mcp/bin/jspassgen-mcp.js"]
    }
  }
}

Add this entry to your MCP client's server configuration, with the path of your clone. The client starts the server as a child process and talks to it over stdin and stdout; ask it for a password and it calls generate_password. To try it without a client: node examples/generate-password.mjs 24.


The jspassgen ecosystem

jspassgen is one suite of repositories that release the same version (ADR 0001, inventory in docs/ecosystem.json). Only the core is released today; every other member, this one included, is planned.

Component

Purpose

Use case

jspassgen

The zero-dependency core, Node.js library, web UI and workers (released)

Generate passwords in JavaScript

jspassgen-cli

Command-line generator on the core (planned)

Generate passwords in a terminal

jspassgen-mcp

This server: the core as MCP tools over stdio (planned)

Let an AI assistant generate a password locally

jspassgen-lsp

Language server flagging weak literal secrets (planned)

Catch weak secrets in configuration files

jspassgen-sdk-python, -rust, -java, -dotnet, -cpp

Native ports of the core, proven by a conformance kit (planned)

The same rules outside JavaScript

jspassgen.github.io

jspassgen.com (planned as a suite member)

Product site


Capabilities at a glance

Area

Capability

Status

Tools

generate_password: a base64-alphabet password of 1 to 1024 characters

Available

Tools

Passphrase generation

Not available yet

Tools

Entropy estimate for a configuration

Not available yet (the entropy of a generated password is returned)

Tools

Strength analysis of an existing password

Not available yet

Transport

stdio, local

Available

Transport

HTTP or any remote transport

Not planned


Ecosystem comparison

No comparison is published yet. A comparison with other MCP password tools will be added only with evidence behind each claim.


Benchmarks

Not measured yet. Generation time is jspassgen's; this server adds one MCP round trip over stdio.


Features

  • One tool, generate_password. Input: length, an integer from 1 to 1024, optional (jspassgen's default of 16 applies when it is omitted). The bounds are read from jspassgen's PASSWORD_TYPE_METADATA, so they cannot drift from the core, and are advertised in the tool's JSON Schema. Output: the password as text, and structured content with password, length, entropyBits and securityLevel as jspassgen computes them.

  • No generation logic of its own. Every password comes from @sebastienrousseau/jspassgen 0.0.20 (pinned exactly), type strong, drawn from Node.js crypto.

  • Invalid input is refused, not corrected: a non-integer, zero, negative or over-limit length returns a tool error naming length.

  • Tool annotations tell clients the tool is read-only, non-destructive and closed-world.


Configuration

There is nothing to configure yet: no environment variables, flags or files. The server reads nothing and writes nothing outside the MCP messages on stdin and stdout.


Examples

Example

What it shows

Run

examples/generate-password.mjs

An MCP client that starts the server over stdio, lists its tools and calls generate_password

node examples/generate-password.mjs [length]

CI runs the example on every push.


When not to use jspassgen

  • You need a password manager. The server generates; it does not store, sync or fill anything.

  • You need a remote or shared server. It speaks stdio only, to the one client that started it. There is no HTTP transport.

  • You need passphrases, entropy estimates for a configuration or strength analysis today. The ADR plans those tools; only generate_password exists so far.

  • You need it from npm today. It is not published until the first suite release.

  • You do not want the password in the AI conversation. The password is returned to the MCP client, which shows it to the model and may keep it in the conversation history. That is inherent to calling a tool; generate locally with jspassgen instead.


Development

mise install     # Node.js 24 (mise.toml)
make install     # npm ci
make check       # ESLint, Prettier, Halstead, tests at 100% coverage, the example, the README check
make audit       # npm audit

DEVELOPMENT.md lists every CI gate and its local command; CONTRIBUTING.md the rules for a change.


Security

  • Local only. stdio transport, no listening socket, no network call, no telemetry.

  • Nothing logged. The process writes the MCP protocol to stdout and nothing to stderr; a test fails if anything else appears on either. A generated password goes to the calling client only.

  • CSPRNG. Randomness comes from Node.js crypto through jspassgen; this server adds none of its own.

  • Supply chain. Dependencies are locked in package-lock.json, the runtime ones pinned exactly; npm audit, CodeQL, OpenSSF Scorecard and Dependabot run in CI, and every workflow action is pinned by commit SHA.

Report vulnerabilities according to SECURITY.md.


Documentation


Stability guarantees

  • Version axis. 0.0.x, moving by exactly 0.0.1 in lockstep with the jspassgen suite. Before 1.0 any release may break; breaking changes are called out in CHANGELOG.md.

  • Output stability. A change to a tool's name, input schema or output fields is a breaking change, even when no JavaScript API moves.

  • Minimum toolchain. Node.js 22, enforced by engines and tested in CI. Raising it is a breaking change, made only in a release whose CHANGELOG states the new floor and the reason.


License

Dual-licensed under either the Apache License, Version 2.0 or the MIT license, at your option. Unless you state otherwise, any contribution you submit is dual-licensed the same way, without additional terms.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Generates secure random passwords and memorable passphrases with customizable options including length, character types, emojis, and automatic strength evaluation using zxcvbn scoring.
      -
    • A
      license
      A
      quality
      D
      maintenance
      Generates strong passwords and evaluates password strength using zxcvbn, with uniform random sampling via Node's crypto.
      2
      9 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables to generate cryptographically-random passwords and PINs with control over character sets and length. Returns the password(s) and their entropy in bits.
      84 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to analyze a password's strength entirely offline — character-set entropy, a strength rating, estimated crack times for offline and throttled online attackers, and specific weaknesses like short length, missing character classes, sequences, repeats, or common-password matches. The password is never transmitted or stored, as the heuristic analysis runs in-process.
      80 npm
      MIT