password_generator20
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@password_generator20Generate a 16-char password with 2 special chars and 3 numbers."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Password Generator20 MCP Server
🚀 使用 EMCP 平台快速体验
EMCP 是一个强大的 MCP 服务器管理平台,让您无需手动配置即可快速使用各种 MCP 服务器!
快速开始:
🌐 访问 EMCP 平台
📝 注册并登录账号
🎯 进入 MCP 广场,浏览所有可用的 MCP 服务器
🔍 搜索或找到本服务器(
bach-password_generator20)🎉 点击 "安装 MCP" 按钮
✅ 完成!即可在您的应用中使用
EMCP 平台优势:
✨ 零配置:无需手动编辑配置文件
🎨 可视化管理:图形界面轻松管理所有 MCP 服务器
🔐 安全可靠:统一管理 API 密钥和认证信息
🚀 一键安装:MCP 广场提供丰富的服务器选择
📊 使用统计:实时查看服务调用情况
立即访问 EMCP 平台 开始您的 MCP 之旅!
Related MCP server: MCP Password Generator
简介
这是一个 MCP 服务器,用于访问 Password Generator20 API。
PyPI 包名:
bach-password_generator20版本: 2.0.0
传输协议: stdio
安装
从 PyPI 安装:
pip install bach-password_generator20从源码安装:
pip install -e .运行
方式 1: 使用 uvx(推荐,无需安装)
# 运行(uvx 会自动安装并运行)
uvx --from bach-password_generator20 bach_password_generator20
# 或指定版本
uvx --from bach-password_generator20@latest bach_password_generator20方式 2: 直接运行(开发模式)
python server.py方式 3: 安装后作为命令运行
# 安装
pip install bach-password_generator20
# 运行(命令名使用下划线)
bach_password_generator20配置
API 认证
此 API 需要认证。请设置环境变量:
export API_KEY="your_api_key_here"环境变量
变量名 | 说明 | 必需 |
| API 密钥 | 是 |
| 不适用 | 否 |
| 不适用 | 否 |
在 Claude Desktop 中使用
编辑 Claude Desktop 配置文件 claude_desktop_config.json:
{
"mcpServers": {
"password_generator20": {
"command": "uvx",
"args": ["--from", "bach-password_generator20", "bach_password_generator20"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}注意: 请将 E:\path\to\password_generator20\server.py 替换为实际的服务器文件路径。
可用工具
此服务器提供以下工具:
password
Generates a password with standard settings - length = 10 - 1 special char - 2 numbers
端点: GET /password
参数:
length(string): Creates a password with the given length, max length is 32 charsspchar(string): Number of special characters to be usednumbers(string): Number of digits to be usedumlauts(string): Example value:quantity(string): Number of passwords issued, max is 10 per call.
技术栈
传输协议: stdio
HTTP 客户端: httpx
开发
此服务器由 API-to-MCP 工具自动生成。
版本: 2.0.0
Available Tools
1 toolpasswordC
Generates a password with standard settings - length = 10 - 1 special char - 2 numbers
| Name | Required | Description | Default |
|---|---|---|---|
| length | No | Creates a password with the given length, max length is 32 chars | 10 |
| spchar | No | Number of special characters to be used | 2 |
| numbers | No | Number of digits to be used | 2 |
| umlauts | No | Example value: | |
| quantity | No | Number of passwords issued, max is 10 per call. | 10 |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure, but it only states that passwords are generated with certain settings. It does not disclose randomness, character set, output format, or any side effects, leaving the agent without critical behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence and is front-loaded, but the inclusion of an incorrect default value makes it less valuable than a purely accurate statement would be. It is short but not perfectly reliable.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no annotations, the description is expected to provide richer context about return values, constraints, and edge cases. It lacks any such detail, making it incomplete for a tool with five parameters and multiple configuration options.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
While the schema provides 100% parameter coverage, the description adds a misleading 'standard settings' claim that contradicts the schema default for spchar (1 vs 2). This actively harms parameter understanding rather than adding value, so a score below the baseline is warranted.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool as a password generator with specific default settings. However, it slightly misstates the default for special characters (says 1, schema says 2), which prevents a perfect score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. Usage is only implied by the tool's name and brief description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v2.0.0- First observed
password
TDQS
Only one tool exists, so there is no possibility of confusion or overlap between tools. The tool's purpose is clearly described.
The tool is named 'password' which is clear and descriptive, though not in a verb_noun format. Since there is only one tool, there is no inconsistency in naming patterns.
With only one tool, the server feels very thin for a password generator, which typically offers customization options like length, character types, and count. One tool is considered too few for a meaningful tool surface.
The tool provides a basic password generation function, but it is locked to fixed settings (length 10, 1 special, 2 numbers) with no options to customize. This limits the usefulness and leaves gaps for common use cases like different lengths or multiple passwords.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
20+ pay-per-use APIs: image gen, crypto data, email verify, SSL check, web scraping, and more.
22 pay-per-call developer, security, network and data utilities using x402 on Base.
Related MCP Servers
- AlicenseCqualityDmaintenanceProvides enhanced access to the randomuser.me API with advanced features like custom formatting, password generation, and weighted nationality distribution.2MIT
- 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.214MIT
- FlicenseAqualityDmaintenanceEnables AI agents to securely access and manage passwords from a gopass store via four tools: list, retrieve, search, and generate passwords.4-
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BACH-AI-Tools/password_generator20'
If you have feedback or need assistance with the MCP directory API, please join our Discord server