Servidor MCP de Dragons Eye Ransomware Tracker

• Nombre en el registrocom.ransomware-tracker.api/dragonseyeverificado en el registro MCP

El nombre en el registro está bajo ransomware-tracker.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-27
• Herramientas16
• El servidor se llamadragonseye
• Versión del servidor1.5.0
• Versión del protocolo2025-06-18

El 2026-10-27 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 230 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 1 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 1 hasta ahora
• Respondiómidiendo1 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta279 ms
• Espacio en el contexto del agente≈ 2900 tokenslas definiciones de todas sus herramientas (16), que el agente lleva en cada turno
• Definiciones de herramientasA · 100 de 100
• Resultados tipados0 de 16 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Todas las herramientas pasan las seis comprobaciones.

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• 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.

• 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.

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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, phishing, malware delivery) in recent threat reporting? Returns…

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

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

• 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 public exploit repositories, an AI-generated attack flow with ATT&CK technique…

• 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 (not charged). Costs $0.50 USDC per call via x402 (payment goes in…

• 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 techniques and CVEs co-mentioned in public reporting (co-mention, not…

• 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.