Security & Testing

cryptoleek.com

MCP server for querying CryptoLeek's broker registry to identify known crypto scams, get recent fraud entries, and access country- and pattern-specific recovery guides.

WebMCP1 endpoint5 known toolsFirst detected September 4, 2026Last detected September 4, 2026

ENDPOINT 1

https://cryptoleek.com

No auth detected

MCP server metadata

Name: WebMCP

Capabilities

imperative

Known tools 5

cryptoleek_searchRegistry

Search the CryptoLeek public broker registry for entries matching a name, domain, or alias. Returns up to 20 results with verdict (confirmed-scam, under-investigation, recovery-available, cleared), name, primary domain, and a link to the full investigation page. Use this to help a victim check whether a platform they encountered is documented as fraudulent.

Inferred read-only

cryptoleek_checkBrokerStatus

Given a domain (e.g. "myetherwallet.cam" or "https://example-broker.com"), check whether CryptoLeek has the platform documented in its public registry. Returns the verdict and a URL to the full investigation page if found, or null if the domain is not in the registry. Use this for fast "is this site a known scam" lookups.

Inferred read-only

cryptoleek_recentBrokers

Return the most recently updated entries from the CryptoLeek public broker registry. Useful for surfacing freshly ingested fraud-platform documentation to a user asking "what new scams have been added recently?".

Inferred read-only

cryptoleek_listCountryGuides

List CryptoLeek country-specific recovery guides. Each guide covers regulators, first steps for victims, local scam patterns, and how CryptoLeek operates in that jurisdiction. Use this to surface the right guide for a victim based on their country.

Inferred read-only

cryptoleek_listScamPatterns

List CryptoLeek recovery guides organised by scam pattern (e.g. romance / pig butchering, fake trading platforms, wallet drains, withdrawal-block extortion, recovery scams). Use this to route a victim to the right pattern-specific recovery playbook.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.webmcp]
url = "https://cryptoleek.com"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "webmcp": {
      "type": "http",
      "url": "https://cryptoleek.com"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: webmcp
Remote MCP URL: https://cryptoleek.com

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "webmcp": {
      "url": "https://cryptoleek.com"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "webmcp": {
      "type": "http",
      "url": "https://cryptoleek.com"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "webmcp",
  "transport": "streamable-http",
  "url": "https://cryptoleek.com"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.