Password Breach Checker Skill

What this skill does

Password Breach Checker tells you whether a password appears in the Pwned Passwords corpus of passwords exposed in data breaches. Send the password or its SHA-1 hash and get a breached flag. Paid plans add how many times it was seen and a risk level. You switch it on with a single toggle — no SDK and no endpoint wiring — and it answers over MCP or REST using the same key as every other skill.

See it work

A real response from the Password Breach Checker Skill — exactly what your agent gets back when it makes the call.

vervekit · passwordbreachtool call

{
  "password": "password123"
}

result

breached: true
breachCount: 2266543
riskLevel: critical
inputType: password
hashPrefix: CBFDA

Run it with your own input. Live calls happen in your dashboard, on your key.

Ways to use it

One toggle, a new capability

Enable Password Breach Checker and your app or agent can check password breach on demand — no SDK, no endpoint wiring. It answers over MCP or REST using the same key as every other skill.

A tool agents call themselves

Over MCP, Password Breach Checker appears to your model as the passwordbreach tool it invokes whenever a task needs it — you don't write the glue, the agent reaches for it.

REST from any backend

Prefer to call it directly? Any language that can send a GET can hit Password Breach Checker to check password breach inline in your own server-side code.

Use it in your app

Once enabled, this skill is reachable two ways — pick whichever fits how you build. Both use the same key.

For AI agentsMCP

It appears to your model as a callable tool. No extra code — the agent invokes it when a task needs it.

passwordbreach

For apps & backendsREST

Call it from your server with one request and your key. Node, Python, Go — anything that can send a GET.

GET /v1/passwordbreach

Ask your agent

“Enable Password Breach Checker and ask your agent to check password breach.”
“Use the Password Breach Checker skill for me.”

Password Breach Checker Skill, answered

How to connect it over MCP or REST.

How do I add Password Breach Checker to my app or agent?

Enable the Password Breach Checker Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the passwordbreach tool) or over REST (call it from any backend). No SDK to install and no endpoint to wire.

MCP or REST — which should I use?

Both work off one key. Use MCP when an AI agent should decide when to check password breach — the skill shows up as a callable tool. Use REST when your own server-side code should call it directly. Many apps use both.

Which agents and frameworks does it work with?

Any MCP client — Claude, Cursor, LangChain, and custom agents all speak the Model Context Protocol, so Password Breach Checker appears as a standard tool with nothing skill-specific to integrate.

How many credits does a Password Breach Checker call cost?

Each call costs 5 credits. Every skill rides the same key and the same connection, so enabling more skills doesn't add more integrations to manage.

Do I need to install anything?

No SDK and no endpoint wiring — enabling the skill is a toggle. You point your agent at the VerveKit MCP endpoint (or call REST) and Password Breach Checker is available immediately.

Where does the data come from, and what shows on my bill?

VerveKit runs on APIVerve, our production data engine; Password Breach Checker is one of 300+ skills on the same key. Invoices and card statements show APIVERVE.

One toggle, a new capability

A tool agents call themselves

REST from any backend

Password Breach Checker Skill, answered

Other ways to use Password Breach Checker

Give your software a way to act on the world.

Scaling in production?