Dragons Eye Ransomware Claims

Name: Dragons Eye Ransomware Claims
Author: com.ransomware-tracker.api

MCP serverMCP

Ransomware claim lookups, IOC and CVE intel, group intel, bulk checks and watch alerts (x402 USDC).

by com.ransomware-tracker.apihomepage ↗v1.5.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"dragons-eye-ransomware-claims","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability44/44 checks ok

when	check	result	http	latency	detail
1 h ago	mcp initialize	ok	200	45 ms	server dragonseye 1.5.0 · protocol 2025-06-18 · 16 tools
8 h ago	mcp initialize	ok	200	55 ms	server dragonseye 1.5.0 · protocol 2025-06-18 · 16 tools
14 h ago	mcp initialize	ok	200	174 ms	server dragonseye 1.5.0 · protocol 2025-06-18 · 16 tools
21 h ago	mcp initialize	ok	200	133 ms	server dragonseye 1.5.0 · protocol 2025-06-18 · 16 tools
28 h ago	mcp initialize	ok	200	70 ms	server dragonseye 1.5.0 · protocol 2025-06-18 · 16 tools
35 h ago	mcp initialize	ok	200	84 ms	server dragonseye 1.5.0 · protocol 2025-06-18 · 16 tools
2 d ago	mcp initialize	ok	200	73 ms	server dragonseye 1.5.0 · protocol 2025-06-18 · 16 tools
2 d ago	mcp initialize	ok	200	69 ms	server dragonseye 1.5.0 · protocol 2025-06-18 · 16 tools
2 d ago	mcp initialize	ok	200	76 ms	server dragonseye 1.5.0 · protocol 2025-06-18 · 16 tools
3 d ago	mcp initialize	ok	200	96 ms	server dragonseye 1.5.0 · protocol 2025-06-18 · 16 tools

Tools observed via MCP handshake

validate_query — Free. Check and normalize a company name or domain before calling lookup_victim; tells you whether it will be searched as a domain or a name. Offline: no networ
pricing — Free. Return the price of every paid tool, the payment network (Base) and address, the licensed data sources, and the 'unverified claim' label every result carr
lookup_victim — Search ransomware leak-site claims for one company name or domain: has a group claimed it? Returns matching claims with group, claimed date, first-observed date
recent_claims — List the newest ransomware leak-site claims (1-10), optionally filtered to one group such as akira or qilin. Use it to watch recent activity; use lookup_victim
group_profile — Get a profile of one ransomware group: aliases, when RansomLook first observed it, and a sample of its newest claims. Use it to understand who a group is; use r
batch_exposure_check — Check up to 25 vendor or supplier domains in one call for ransomware leak-site claims, for third-party-risk reviews. Returns one result per domain (found, claim
vendor_risk_report — Build a third-party ransomware risk report for up to 100 vendors (domains or company names). For each vendor: matching leak-site claims (group, claimed and firs
bulk_vendor_check — Check up to 100 vendors (domains or company names) for ransomware leak-site claims in one call: per vendor, matching claims (group, dates, sources), claim count
indicator_check — Check one domain (or its parent domains) or IPv4 address against ThreatCluster's high-confidence 30-day IOC feed: is it listed as attacker infrastructure (C2, p
indicator_batch_check — Same as indicator_check for up to 100 domains or IPv4 addresses in one call (one flat price). Costs $0.25 USDC per call via x402 (payment goes in _meta["x402/pa
cve_status — Free. CISA KEV status (date added, due date, known ransomware campaign use, required action), EPSS when known, and whether paid cve_intel detail is cached for t
cve_intel — Everything an agent needs to prioritize one CVE: CVSS, affected vendors/products, vendor advisories, CISA KEV status and known ransomware use, EPSS, recorded pu
cve_batch_intel — cve_intel for up to 50 CVEs in one call. Charged only if every CVE is cached; otherwise an error lists the ids with no data and the covered ids to retry with (n
group_intel — Threat-hunting profile of one active ransomware group: total and recent leak-site listings with a momentum status, reported tools, malware, campaigns, ATT&CK te
coverage — Free. Indicator-feed freshness and the CVE ids and ransomware groups currently cached for cve_intel and group_intel.
watch_status — Free. Status of a paid vendor watch (created with HTTP POST /v1/watch): items, expiry, last check, last webhook delivery.

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.ransomware-tracker.api/dragonseye

first seen 12 d ago · fetched 2 d agoopen ↗

Field history (12 recent events)

6 d ago · declared · summary → "Ransomware claim lookups, IOC and CVE intel, group intel, bulk checks and watch alerts (x402 USDC)."
6 d ago · declared · version → "1.5.0"
6 d ago · declared · description → "Ransomware claim lookups, IOC and CVE intel, group intel, bulk checks and watch alerts (x402 USDC)."
9 d ago · declared · summary → "Ransomware leak-site claim lookups, group profiles and a $3 vendor risk report (x402 USDC)."
9 d ago · declared · description → "Ransomware leak-site claim lookups, group profiles and a $3 vendor risk report (x402 USDC)."
9 d ago · declared · version → "1.3.0"
12 d ago · declared · summary → "Pay-per-call ransomware leak-site claim lookups, recent claims and group profiles (x402 USDC)."
12 d ago · declared · publisherName → "com.ransomware-tracker.api"
12 d ago · declared · description → "Pay-per-call ransomware leak-site claim lookups, recent claims and group profiles (x402 USDC)."
12 d ago · declared · homepageUrl → "https://api.ransomware-tracker.com/llms.txt"
12 d ago · declared · version → "1.0.0"
12 d ago · declared · protocols → ["mcp"]

Dragons Eye Ransomware Claims

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from