# Dragons Eye Ransomware Claims (remote · api.ransomware-tracker.com)

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

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `api.ransomware-tracker.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-ransomware-tracker-api-dragonseye/api.md), [page](https://verifymcp.io/servers/com-ransomware-tracker-api-dragonseye/api)

## Channel facts

- Endpoint: `https://api.ransomware-tracker.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.5.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2405 tokens (~150/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Dragons Eye Ransomware Claims MCP server?

Dragons Eye Ransomware Claims is a hosted endpoint at https://api.ransomware-tracker.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-ransomware-tracker-api-dragonseye 'https://api.ransomware-tracker.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-ransomware-tracker-api-dragonseye": {
      "url": "https://api.ransomware-tracker.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-ransomware-tracker-api-dragonseye": {
      "type": "http",
      "url": "https://api.ransomware-tracker.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-ransomware-tracker-api-dragonseye]
url = "https://api.ransomware-tracker.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-ransomware-tracker-api-dragonseye": {
      "type": "remote",
      "url": "https://api.ransomware-tracker.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-ransomware-tracker-api-dragonseye --url 'https://api.ransomware-tracker.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-ransomware-tracker-api-dragonseye:
    url: "https://api.ransomware-tracker.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-ransomware-tracker-api-dragonseye": {
      "Transport": "http",
      "Url": "https://api.ransomware-tracker.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-ransomware-tracker-api-dragonseye -t streamable-http -u 'https://api.ransomware-tracker.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-ransomware-tracker-api-dragonseye": {
      "type": "http",
      "url": "https://api.ransomware-tracker.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-18 (score 69, 0)

- [security] Tool “cve_batch_intel” rewrote its description, which is the text the model reads

### 2026-10-17 (score 69, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 1485 → 2396
- [functional] Server version: 1.4.0 → 1.5.0
- [functional] New tool “coverage”
- [functional] New tool “cve_batch_intel”
- [functional] New tool “cve_intel”
- [functional] New tool “cve_status”
- [functional] New tool “group_intel”
- [functional] New tool “indicator_batch_check”
- [functional] New tool “indicator_check”

### 2026-10-15 (score 68, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 1196 → 1485
- [functional] Server version: 1.3.0 → 1.4.0
- [functional] New tool “bulk_vendor_check”
- [functional] New tool “watch_status”

### 2026-10-14 (score 67, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 941 → 1196
- [functional] Server version: 1.2.0 → 1.3.0
- [functional] New tool “vendor_risk_report”

### 2026-10-13 (score 67, +8)

- [security improvement] Authorization: unverified → partial
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “group_profile” rewrote its description, which is the text the model reads
- [security] Tool “lookup_victim” rewrote its description, which is the text the model reads
- [security] Tool “pricing” rewrote its description, which is the text the model reads
- [security] Tool “recent_claims” rewrote its description, which is the text the model reads
- [security] Tool “validate_query” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 80% → 100%
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → excellent
- [functional] Server version: 1.0.0 → 1.2.0
- [functional] New tool “batch_exposure_check”
- [cosmetic] “validate_query” reworded the description of “q”

### 2026-10-12 (score 59)

First indexed and scored.

## MCP tools (16)

### `validate_query` (~73 tokens)

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.

Input parameters:

- `q` (string, required): Company name or domain to normalize, e.g. 'Acme Corp' or acme.com

### `pricing` (~53 tokens)

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.

### `lookup_victim` (~189 tokens)

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.

Input parameters:

- `q` (string, required): Company name or domain, e.g. 'Acme Corp' or acme.com (3-120 chars)

### `recent_claims` (~165 tokens)

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.

Input parameters:

- `group` (string): Ransomware group name, e.g. akira, qilin
- `limit` (integer): Max claims to return (1-10, default 10)

### `group_profile` (~144 tokens)

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.

Input parameters:

- `group` (string, required): Ransomware group name or alias, e.g. akira

### `batch_exposure_check` (~185 tokens)

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.

Input parameters:

- `domains` (array, required): Vendor/supplier domains to check, 1-25, e.g. ["acme.com", "example.org"]

### `vendor_risk_report` (~236 tokens)

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.

Input parameters:

- `vendors` (array, required): Vendor domains or company names, 1-100, e.g. ["acme.com", "Example Corp"]

### `bulk_vendor_check` (~180 tokens)

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.

Input parameters:

- `vendors` (array, required): Vendor domains or company names, 1-100, e.g. ["acme.com", "Example Corp"]

### `indicator_check` (~174 tokens)

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, phishing, malware delivery) in recent threat reporting? Returns listed/not_listed, match type, reason, linked reports and clusters. Use it before opening a link, in email triage or SOC enrichment. Not listed is not proof of safety. Served from an hourly cache; a stale feed returns an error and is not charged. 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.

Input parameters:

- `q` (string, required): Domain, URL or IPv4, e.g. evil.example or 203.0.113.7

### `indicator_batch_check` (~85 tokens)

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/payment"]); invalid input or an upstream failure returns an error and is not charged.

Input parameters:

- `items` (array, required): Domains or IPv4 addresses, 1-100

### `cve_status` (~73 tokens)

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 this CVE.

Input parameters:

- `id` (string, required): CVE id, e.g. CVE-2026-0257

### `cve_intel` (~161 tokens)

Everything an agent needs to prioritize one CVE: CVSS, affected vendors/products, vendor advisories, CISA KEV status and known ransomware use, EPSS, recorded public exploit repositories, an AI-generated attack flow with ATT&CK technique ids (flagged as AI-generated) and suggested MITRE D3FEND countermeasures. CVEs not cached yet return an error (queued, not charged); check cve_status (free) first. Costs $0.03 USDC per call via x402 (payment goes in _meta["x402/payment"]); invalid input or an upstream failure returns an error and is not charged.

Input parameters:

- `id` (string, required): CVE id, e.g. CVE-2026-0257

### `cve_batch_intel` (~108 tokens)

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 (not charged). 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.

Input parameters:

- `ids` (array, required): CVE ids, 1-50

### `group_intel` (~144 tokens)

Threat-hunting profile of one active ransomware group: total and recent leak-site listings with a momentum status, reported tools, malware, campaigns, ATT&CK techniques and CVEs co-mentioned in public reporting (co-mention, not attribution), recent headlines and suggested D3FEND countermeasures. Use group_profile for its claim sample. Uncached groups return an error (queued, not charged). 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.

Input parameters:

- `name` (string, required): Group name, e.g. akira, qilin

### `coverage` (~32 tokens)

Free. Indicator-feed freshness and the CVE ids and ransomware groups currently cached for cve_intel and group_intel.

### `watch_status` (~55 tokens)

Free. Status of a paid vendor watch (created with HTTP POST /v1/watch): items, expiry, last check, last webhook delivery.

Input parameters:

- `watch_id` (string, required): Watch id, e.g. dew_abcdefghijklmnop

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-ransomware-tracker-api-dragonseye/api#diagnostics

## Score history

- 2026-10-18: 69
- 2026-10-17: 69
- 2026-10-16: 68
- 2026-10-15: 68
- 2026-10-14: 67
- 2026-10-13: 67
- 2026-10-12: 59

## Common questions

### What is the Dragons Eye Ransomware Claims MCP server?

Dragons Eye Ransomware Claims is an MCP server listed in the public MCP registry as com.ransomware-tracker.api/dragonseye. Ransomware claim lookups, IOC and CVE intel, group intel, bulk checks and watch alerts (x402 USDC). This page covers its hosted endpoint (https://api.ransomware-tracker.com/mcp).

### Is the Dragons Eye Ransomware Claims MCP server safe to use?

Dragons Eye Ransomware Claims scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Dragons Eye Ransomware Claims MCP server expose?

Dragons Eye Ransomware Claims exposes 16 tools: validate_query, pricing, lookup_victim, recent_claims, group_profile, and 11 more. Their descriptions and schemas cost roughly 2,057 tokens of context every time the server is loaded.

### Does the Dragons Eye Ransomware Claims MCP server require authentication?

No. We connected to Dragons Eye Ransomware Claims without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Dragons Eye Ransomware Claims MCP server still maintained?

Dragons Eye Ransomware Claims is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.ransomware-tracker.com/mcp
- Website: https://api.ransomware-tracker.com/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/com-ransomware-tracker-api-dragonseye/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-ransomware-tracker-api-dragonseye/api.json
- HTML version of this page: https://verifymcp.io/servers/com-ransomware-tracker-api-dragonseye/api