# Password Strength Analyzer API [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/Br0ski777/password-strength-x402  
**GitHub Stars:** 0  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/password-strength-analyzer-api

## Description
Password strength scoring with entropy, crack time estimation, common password detection. x402.

## Tools
Capabilities this server exposes over MCP:

- **security_check_password** — Check password strength with entropy and crack time
- **password** — The password to analyze

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "password-strength-analyzer-api": {
    "url": "https://password-strength.api.klymax402.com/mcp"
  }
}
```

## Documentation

## What Password Strength Analyzer API MCP server does

Password Strength Analyzer API MCP server checks an individual password for security characteristics. The `security_check_password` operation accepts one required string, `password`, and produces a score from 0 to 100, a strength category, estimated time to crack, entropy measured in bits, and recommendations for improvement. Its strength labels are weak, fair, strong, and excellent.

The service also compares the supplied value with the top 1,000 common passwords. That makes it suitable for password guidance and basic password-risk checks. It is not presented as a password hash generator or as a general JSON validation service; those tasks should use other tools referenced by the source documentation.

## How it works

The MCP endpoint is available at `https://password-strength.api.klymax402.com/mcp`. An MCP-compatible client connects to that URL and invokes `security_check_password` with the password to analyze. The service performs the analysis remotely and returns the resulting security details to the client.

Each call uses x402 pay-per-request billing. The listed price is $0.003 per check, paid in USDC on Base L2, identified as `eip155:8453`. The payment flow begins with an HTTP 402 response containing an x402 challenge when using the direct HTTP API. x402-aware clients can sign the payment and retry the request automatically. The documented payment facilitators are Coinbase CDP as the primary option and PayAI as the fallback.

## Setup and configuration

Add the remote MCP URL to the MCP client configuration. A minimal entry uses the server name `password-strength` and the URL shown above. The README specifically lists Claude Desktop and Cursor as supported configuration targets, and also mentions ElizaOS.

No API key, account signup, or server environment variable is documented as required. The caller does need access to an x402-compatible payment flow and a wallet or payment setup capable of sending USDC on Base L2. For direct HTTP use, send a POST request with `Content-Type: application/json` to `/api/check` and provide a JSON body containing the password. An x402-aware HTTP client can handle the payment challenge and retry sequence.

## Tools and capabilities

- `security_check_password`: evaluates one password for strength and security.
- Required input: `password`, a string containing the value to analyze.
- Returned analysis: 0–100 score, weak/fair/strong/excellent rating, entropy bits, estimated crack time, common-password detection, and improvement suggestions.
- HTTP route: `POST /api/check`.
- Listed call price: $0.003.

Password Strength Analyzer API MCP server is intended for analysis only. The source specifically says not to use this operation for hash generation or input validation.

## Limitations and notes

The supplied material documents one MCP tool and one password input. It does not describe batch analysis, password storage, hashing, account management, rate limits, or custom scoring settings. Because the endpoint is paid per call, applications should account for x402 payment handling before invoking it. The common-password check is described as covering the top 1,000 common passwords, so that check should not be treated as a complete password corpus.

The project is licensed under MIT. Its payment model removes the need for an API key and signup, but it still requires payment in USDC on Base L2 for each request.

_Full upstream README: https://allmcps.com/mcp/password-strength-analyzer-api/readme_