Have I Been Pwned MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_emailB | Check if an email address has been found in data breaches |
| check_passwordB | Check if a password has been exposed in data breaches (using k-anonymity) |
| get_breach_detailsC | Get details about a specific data breach |
| list_all_breachesC | List all breaches in the system |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: checking email breaches, checking password exposures, getting details on a specific breach, and listing all breaches. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern (e.g., check_email, check_password, get_breach_details, list_all_breaches). The naming is uniform and predictable, using clear verbs that describe the action and nouns that specify the target.
With 4 tools, the server is well-scoped for its purpose of breach checking and information retrieval. Each tool serves a distinct and necessary function, covering the core operations of the Have I Been Pwned service without being overly sparse or bloated.
The tool set provides complete coverage for the domain: it allows checking for email and password exposures, retrieving details on specific breaches, and listing all breaches. There are no obvious gaps, as these tools cover the primary use cases of the service effectively.