MCP Password Generator

Created By
acidkeyxyza year ago
A Model Context Protocol (MCP) server that generates random passwords with different character sets.
Overview

what is MCP Password Generator?

MCP Password Generator is a server that generates random passwords using different character sets to enhance security.

how to use MCP Password Generator?

To use the MCP Password Generator, clone the repository, install the dependencies, and run the server with the inspector. You can then use the generate-password tool to create passwords.

key features of MCP Password Generator?

  • Generates random passwords with various character sets: all characters, alphanumeric, numbers only, and letters only.
  • Easy installation and setup with Node.js.
  • Ability to specify the number and length of passwords generated.

use cases of MCP Password Generator?

  1. Creating secure passwords for user accounts.
  2. Generating temporary passwords for applications.
  3. Enhancing security protocols in software development.

FAQ from MCP Password Generator?

  • What character sets can I use for password generation?

You can choose from all characters, alphanumeric, numbers only, or letters only.

  • Do I need any special software to run the MCP Password Generator?

Yes, you need Node.js (v16 or higher) and npm installed on your machine.

  • Is the MCP Password Generator free to use?

Yes! The MCP Password Generator is open-source and free to use.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
acidkeyxyz
Star
0
Language
TypeScript
License
-
Category
security

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago