Dragons Eye Ransomware Claims is answering right now. Last checked 4 min ago. It exposes 9 tools.
Ransomware claim lookups, a 100-vendor bulk check, webhook watch alerts, vendor risk reports (x402).
Uptime history
7 days of history
7 days agonow
100.0%
Uptime 24h
92 of 92 checks
9
Tools
read from the server
209 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 15
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 12 October 2026. No other catalogue keeps this.
15 Oct
2 tools appeared
bulk_vendor_check, watch_status
15 Oct
a tool changed version
14 Oct
a tool appeared
vendor_risk_report
14 Oct
a tool changed version
13 Oct
6 tool descriptions were rewritten
batch_exposure_check, group_profile, lookup_victim and 3 more
13 Oct
a tool changed the parameters it asks for
validate_query
13 Oct
a tool changed version
12 Oct
a tool appeared
batch_exposure_check
12 Oct
a tool changed version
Nothing serious here today
Today is the operative word: we check Dragons Eye Ransomware Claims every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.
run in your terminal
claude mcp add dragonseye --transport http https://api.ransomware-tracker.com/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"dragonseye": {
"url": "https://api.ransomware-tracker.com/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.dragonseye]
url = "https://api.ransomware-tracker.com/mcp".cursor/mcp.json
{
"mcpServers": {
"dragonseye": {
"url": "https://api.ransomware-tracker.com/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"dragonseye": {
"url": "https://api.ransomware-tracker.com/mcp"
}
}
}Available tools 9
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
batch
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 count, claims with group, dates and sources). Domains only; use lookup_victim for company names. At most 15 claim records are read per batch, so a domain with many matches is marked partial. Every result is an unverified claim from a criminal leak site, not a confirmed breach; found=false is not proof of absence. Read-only; one flat price. Costs $0.05 USDC per call via x402 (payment goes in _meta["x402/payment"]); invalid input or an upstream failure returns an error and is not charged.
bulk
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 and groups. Raw claims only; use vendor_risk_report for risk levels, a summary and actions. Every result is an unverified claim from a criminal leak site, not a confirmed breach; found=false is not proof of absence. Fails (not charged) if the source is down for more than 25% of vendors. Read-only. Costs $0.50 USDC per call via x402 (payment goes in _meta["x402/payment"]); invalid input or an upstream failure returns an error and is not charged.
group
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 recent_claims for a longer list of its latest claims. Unknown groups return an error and are not charged. Every claim is an unverified claim from a criminal leak site, not a confirmed breach. Read-only. Costs $0.02 USDC per call via x402 (payment goes in _meta["x402/payment"]); invalid input or an upstream failure returns an error and is not charged.
lookup
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, country, sector and licensed sources. Use it for a single vendor or target; use batch_exposure_check for a list of up to 25 vendor domains, and recent_claims for the newest claims overall. Every result is an unverified claim from a criminal leak site, not a confirmed breach, and found=false is not proof of absence (only commercially reusable sources are covered). Read-only, live lookup. Costs $0.01 USDC per call via x402 (payment goes in _meta["x402/payment"]); invalid input or an upstream failure returns an error and is not charged.
pricing
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 carries. No input, no network request, no payment.
recent
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 to search for a specific company. Only commercially reusable sources are used, so country and sector are often null. Every result is an unverified claim from a criminal leak site, not a confirmed breach. Read-only. Costs $0.01 USDC per call via x402 (payment goes in _meta["x402/payment"]); invalid input or an upstream failure returns an error and is not charged.
validate
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 network request, no payment.
vendor
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 first-observed dates, sources), a risk level (high = claim in the last 90 days, elevated = last 12 months, historical, none_found, unknown) and follow-up actions; plus a portfolio summary with priority vendors and the groups involved. Use it for vendor reviews and audits; use batch_exposure_check for a cheaper raw check of up to 25 domains. Every result is an unverified claim from a criminal leak site, not a confirmed breach; none_found is not proof of absence. Fails (not charged) if the source is down for more than 25% of vendors. Read-only; one flat price. Costs $3 USDC per call via x402 (payment goes in _meta["x402/payment"]); invalid input or an upstream failure returns an error and is not charged.
watch
watch_status
Free. Status of a paid vendor watch (created with HTTP POST /v1/watch): items, expiry, last check, last webhook delivery.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://api.ransomware-tracker.com/mcp | streamable-http | answering | 211 ms | 4 min ago |
Alternatives to Dragons Eye Ransomware Claims
same job, measured the same wayx402 Checker (AI Nock)
by nock-for-mak
Free check/board/name; paid bid/report 0.05, 1c fx/wx/lookups, news 0.001.
J
JobSlop
by jobslop
Check US job listings for ghost-job warning signs: look up a job link, search jobs, company reports.
Nslookup
by venomseven
DNS lookups, health reports, SSL certs, security scans, GEO scoring, uptime checks
Chainward
by saltxd
Check a Base or BNB Chain address before you pay it: on-chain risk reports, EAS attestations.
AgentPay Domain & Network Lookup
by noah-silver
Pay-per-call DNS, WHOIS/RDAP, IP and domain reports for agents. x402 USDC on Base or Algorand.
Settled
by settled
Check x402 endpoints before your agent pays: payTo, paid test purchases, payee and buyer reports
O
Orcpin
by npraught
Paid x402 facts for AI agents: signed statements, door reports, endpoint checks, chain reads
Game Industry Library
by gameindustrylibrary
Search 300+ game industry reports with hybrid search, claims, charts, and citations.
Dragons Eye Ransomware Claims — questions
Answers built from our own checks of this server.
What can Dragons Eye Ransomware Claims do?
It exposes 9 tools, read directly from the server on our last check. Among them: batch_exposure_check, bulk_vendor_check, group_profile, lookup_victim, pricing, recent_claims and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Dragons Eye Ransomware Claims working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 209 ms. The bar chart above shows every period we have measured.
How do I connect Dragons Eye Ransomware Claims?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Dragons Eye Ransomware Claims need an API key?
No. Dragons Eye Ransomware Claims completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Dragons Eye Ransomware Claims?
It answers our handshake in 209 ms on average, which is faster than 60% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.