
Password Breach Check Mcp
io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026
Check if a password has appeared in known breaches without sending the password. No key required.
The publisher's own server: check.tattoo: tattoo size and placement guide
Overview
A local MCP server that lets an assistant check whether a password has appeared in known data breaches without sending the password itself.
- What you can do
- Check whether a password appears in known breach data without transmitting the password itself, according to the registry description. The manifest lists no tools, so the exact operations are not documented. It runs as a local process over stdio and requires no API key.
- When to use it
- Useful when you want an assistant to help assess whether a password has been exposed in known breaches, for example while reviewing account security, and you prefer a check that does not send the password.
- Requirements
- Runs as a local process on the user's machine, installed from the npm package password-breach-check-mcp over stdio. No authentication, environment variables or headers are declared. Desktop only; not executable on the web.
Installation
In SourceWeft
- Open Password Breach Check Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.0LatestSep 22, 2026
Score
25% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.
Other Check integrations
check.tattoo: tattoo size and placement guide
tattoo.checkOfficial publisher
check.tattoo: tattoo size and placement guide's hosted MCP server, published by check.tattoo; no sign-in required; Streamable HTTP; 5 tools.
iva.pt — EU VAT check (VIES) and Portuguese VAT law
pt.ivaOfficial publisher
Validates EU VAT numbers against VIES and returns Portuguese VAT Code (CIVA) and RITI articles, in Portuguese or English.

U.S. Public Company Check
Published by GitHub account JusticeUA
Remote Apify-hosted MCP server that lets an assistant look up U.S. public company checks by SEC CIK: filing status, bankruptcy 8-K flag, LEI and sanctions.

Taiwan Company Check
Published by GitHub account JusticeUA
Remote MCP server that lets an assistant look up Taiwanese companies by Unified Business Number for tax status, LEI and sanctions checks.

Romania Company Check
Published by GitHub account JusticeUA
Looks up Romanian companies by CUI, returning status, insolvency, LEI and sanctions data from official registers.