
Password Strength Analyzer API
io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Nov 2, 2026
Password strength scoring with entropy, crack time estimation, common password detection. x402.
Overview
Remote MCP endpoint that scores password strength with entropy, crack-time estimates and common-password checks, paid per call via x402.
- What you can do
- Check a password's strength: returns a 0-100 score, a weak/fair/strong/excellent rating, estimated crack time, entropy bits and improvement suggestions.
- Compare the submitted password against a list of the top 1000 common passwords.
- No other tools are listed; the README points to separate services for hash generation and JSON validation.
- When to use it
- Useful when an assistant needs to evaluate how strong a password is and explain the result, for example in security reviews or user guidance. It is a single-purpose paid endpoint, so it only makes sense if you already have an x402-capable client and wallet.
- Requirements
- A remote MCP endpoint added by URL; no local package, API key or signup. Payment is required per call through the x402 protocol in USDC on Base L2, so an x402-aware client and a funded wallet are needed. Network access to the provider's domain.
Installation
In SourceWeft
- Open Password Strength Analyzer API in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.Br0ski777%2Fpassword-strength/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"password-strength-analyzer-api": {
"type": "sse",
"url": "https://password-strength.api.klymax402.com/mcp"
}
}
}README
Password Strength Analyzer API
[MCP Server] [x402] [License: MIT]
Password strength analyzer with entropy calculation and crack time estimation. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.
Quickstart -- MCP
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
Quickstart -- HTTP (x402)
Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
Tools
security_check_password
Use this when you need to evaluate password strength or security. Returns a score 0-100, strength rating (weak/fair/strong/excellent), estimated crack time, entropy bits, and improvement suggestions. Checks against top 1000 common passwords. Do NOT use for hash generation — use crypto_generate_hash. Do NOT use for input validation — use data_validate_json.
Parameters
Example agent prompts
- "Evaluate password strength or security"
Payment
- Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
- Network: Base L2 (
eip155:8453) - Asset: USDC
- Facilitator: Coinbase CDP (primary), PayAI (fallback)
Part of klymax402
100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
- Catalog: https://klymax402.com/llms.txt
- Full API reference: https://klymax402.com/llms-full.txt
- Live stats: https://klymax402.com/stats
License
MIT
Source: README.md at commit 2cebf1f
Tools
0Version history
1- v1.1.0LatestSep 16, 2026
Score
50% 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 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 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
- License10 pts