jspassgen-mcp
OfficialThis server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
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
The jspassgen ecosystem: the core, its tools, SDKs and site
Library reference
Capabilities at a glance: what the server exposes today
Ecosystem comparison: not published yet
Benchmarks: not measured yet
Features: the tool and its guarantees
Configuration: none yet
Examples: runnable example index
Operational
When not to use jspassgen: limitations
Development: make targets, CI
Security: guarantees and reporting
Documentation: all reference docs
Stability guarantees: version axis, output stability, toolchain discipline
Related MCP server: password-mcp
Install
As a JavaScript library
git clone https://github.com/sebastienrousseau/jspassgen-mcp.git
cd jspassgen-mcp
npm cijspassgen-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 (
enginesinpackage.json; CI tests 22 and 24).Any platform Node.js supports. Randomness comes from Node.js
cryptothrough jspassgen'sNodeCryptoRandomadapter.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 |
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 |
| 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'sPASSWORD_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 withpassword,length,entropyBitsandsecurityLevelas jspassgen computes them.No generation logic of its own. Every password comes from
@sebastienrousseau/jspassgen0.0.20 (pinned exactly), typestrong, drawn from Node.jscrypto.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 |
An MCP client that starts the server over stdio, lists its tools and calls |
|
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_passwordexists 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 auditDEVELOPMENT.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
cryptothrough 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
User manual: not written yet; this README is the reference until it is.
API reference:
src/index.jsand its JSDoc.Developer docs: DEVELOPMENT.md.
Ecosystem map: jspassgen ADR 0001.
Stability guarantees
Version axis.
0.0.x, moving by exactly0.0.1in lockstep with the jspassgen suite. Before1.0any 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
enginesand 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…
This server cannot be deployed
Maintenance
Related MCP Connectors
Password vault for AI agents with scoped, user-approved access
Persistent memory, hybrid search and a goal graph for AI agents, over stdio or remote HTTP.
Command your AI agents: verifiable passports, credential injection, full audit, revoke in 60s.
Aurocrypt Connect: AI access to your services, under approvals you set, without sharing passwords.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceGenerates secure random passwords and memorable passphrases with customizable options including length, character types, emojis, and automatic strength evaluation using zxcvbn scoring.-
- AlicenseAqualityDmaintenanceGenerates strong passwords and evaluates password strength using zxcvbn, with uniform random sampling via Node's crypto.29 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables to generate cryptographically-random passwords and PINs with control over character sets and length. Returns the password(s) and their entropy in bits.84 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables 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 npmMIT