DarkWeb-Breach

io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 24, 2026

OSINT dark web database search tool detecting credential leaks.

VerifiedSSEWeb executableSecurity & Monitoring

Overview

AI-generated overview

A remote MCP endpoint for searching an OSINT dark web database to detect leaked credentials.

What you can do
Search an OSINT dark web database for exposed or leaked credentials, based on the registry description. The manifest lists no individual tools, so the exact search operations are not documented. Premium settlement is referenced through a payment signature header, suggesting some results or features are paid.
When to use it
Consider it when you want an assistant to check whether credentials tied to an account or organization appear in dark web leak data as part of security or exposure review.
Requirements
A remote SSE endpoint at the provider's hosted address; no local runtime or package is needed. No authentication is declared, but a payment-signature header is listed as a secret and is described as required for premium settlement.
Before you install
The payment-signature header is a secret and is tied to premium settlement, so using it may involve spending money; treat the value as sensitive. Search queries and results pass through a third-party hosted service. The tool set is undocumented, so confirm what data is sent and returned before relying on it.

Installation

In SourceWeft

  1. Open DarkWeb-Breach in the dashboard and add it to a workspace.
  2. 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.Evozim%2Fdarkweb-breach/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "darkweb-breach": {
      "type": "sse",
      "url": "https://darkweb-breach-mcp.vercel.app/api/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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
  • Auth declaredRequired10 pts
  • Tools listedRequired15 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.