ransomware-live-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RANSOMWARE_LIVE_API_KEY | Yes | Required. PRO API key | |
| RANSOMWARE_LIVE_TIMEOUT | No | Per-request timeout, seconds | 30 |
| RANSOMWARE_LIVE_BASE_URL | No | API base | https://api-pro.ransomware.live |
| RANSOMWARE_LIVE_CACHE_TTL | No | Cache lifetime, seconds (0 disables) | 300 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_api_keyA | Check that the configured RANSOMWARE_LIVE_API_KEY is valid and active. Returns the client identifier tied to the key. Run this first when any other tool reports an authentication failure. |
| get_statsA | Get platform-wide totals: victim count, tracked group count, press entry count, and the timestamp of the most recently discovered victim. Useful as a cheap freshness check before running larger queries. |
| list_groupsA | List all tracked ransomware groups alphabetically with victim counts. Each entry has |
| get_groupA | Get a full intelligence profile for one ransomware group. Includes background description, first/last seen dates, victim count, known leak-site URLs (Tor and clearweb), MITRE ATT&CK TTPs, exploited CVEs with CVSS scores, tools and malware used, and flags for whether negotiation chats and ransom notes are on file. Args: group_name: Group name, case-insensitive (e.g. "lockbit3", "blackcat", "clop"). |
| list_sectorsA | List every victim sector/industry value with a victim count per sector. The |
| get_recent_victimsA | Get the 100 most recent active ransomware victims. Args:
order: "discovered" (when ransomware.live first saw the leak-site
listing) or "attacked" (estimated attack date).
limit: Max records to return (1-200).
offset: Skip this many records; use |
| search_victimsA | Free-text search across victim organisation names and website domains.
Args:
q: Keyword, e.g. "hospital", "university", "acme".
group: Exact group name, case-insensitive (see |
| filter_victimsA | Filter the full victim database by group, sector, country and date. At least one filter is required, and all filters combine with AND logic.
Args:
group: Exact group name, case-insensitive (see |
| get_victimA | Get the full enriched record for one victim by its Base64 ID. The ID is Base64 of "victim_name@group_name" and appears as the Args:
victim_id: Base64-encoded victim ID from a listing's |
| build_victim_idA | Construct the Base64 victim ID for Offline helper; makes no API call. The names must match the API's values
exactly, so prefer reusing an Args:
victim_name: Victim organisation name as listed (the |
| decode_victim_identifierA | Decode a Base64 victim ID back into its victim and group names. Offline helper; makes no API call. Args: victim_id: Base64-encoded victim ID. |
| list_ioc_groupsA | List ransomware groups that have IOCs on file, with per-type counts. Common IOC types: md5, sha256, ip, domain, email, btc, url. Args: ioc_type: Only return groups holding this IOC type, e.g. "ip". |
| get_group_iocsA | Get indicators of compromise for one ransomware group, grouped by type. Args: group: Group name, e.g. "lockbit3". ioc_type: Return only this type (md5, sha256, ip, domain, email, btc, url) to keep the response small. |
| list_yara_groupsA | List ransomware groups that have YARA detection rules, with rule counts. |
| get_yara_rulesA | Get every YARA rule for a group, each with The returned content is ready to feed to a YARA scanner. Args: group: Group name, e.g. "lockbit3", "blackcat". |
| list_ransomnote_groupsA | List ransomware groups that have ransom notes on file, with note counts. |
| list_group_ransomnotesA | List the ransom note identifiers available for one group. Pass a returned name to Args: group: Group name, e.g. "lockbit3", "clop". |
| get_ransomnoteA | Get the full text of one ransom note. Args:
group: Group name, e.g. "lockbit3".
note_name: Note identifier from |
| list_negotiation_groupsA | List ransomware groups with leaked negotiation chat logs, and chat counts. |
| list_group_negotiationsA | List negotiation chats for a group with ransom and outcome metadata. Each entry carries Args: group: Group name, e.g. "lockbit3". |
| get_negotiationA | Get the full message thread and ransom metadata for one negotiation chat. These threads can be long. Prefer Args:
group: Group name, e.g. "lockbit3".
chat_id: Chat ID from |
| get_recent_pressA | Get the 100 most recent tracked cyberattack press entries. Entries are enriched with infostealer data and linked to a ransomware victim record where the domain matches. Args:
country: ISO 3166-1 alpha-2 country code to narrow before taking the top 100.
limit: Max records to return (1-200).
offset: Skip this many records; use |
| search_pressA | Search all tracked cyberattack press entries by year, month and country. Results are sorted newest first. Args:
year: 4-digit year, e.g. "2024".
month: 2-digit month, e.g. "03". Requires |
| get_sec_8k_filingsA | Get SEC Form 8-K filings disclosing cybersecurity incidents. Covers Item 1.05 (Material Cybersecurity Incidents, mandatory since Dec 2023) and Item 8.01 (Other Events, used for such disclosures before that). Args:
ticker: Stock ticker, uppercase, e.g. "MSFT".
cik: SEC CIK code, e.g. "0001234567".
year: 4-digit filing year, e.g. "2025".
month: 2-digit filing month, e.g. "06". Requires |
| get_csirt_contactsA | Get national CSIRT/CERT incident-response contacts for a country. Sourced from ENISA (EU) and FIRST (global). Use this to find who to notify when triaging a confirmed incident. Args: country: ISO 3166-1 country code, alpha-2 ("FR") or alpha-3 ("FRA"). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 25 tools
Each tool targets a distinct resource and action, with clear list/get navigation pairs for victims, IOCs, YARA rules, ransom notes, and negotiations. A couple of names are near-permutations (list_ransomnote_groups vs list_group_ransomnotes; list_negotiation_groups vs list_group_negotiations), so an agent could misselect without reading the descriptions.
All tool names are verb-first snake_case (validate, get, list, search, filter, build, decode), giving a predictable overall style. Minor deviations include 'id' vs 'identifier' between build_victim_id and decode_victim_identifier, and the swapped noun order in the list_<type>_groups / list_group_<type> pairs.
25 tools is at the heavy end, but the server spans many distinct intelligence domains (victims, groups, IOCs, YARA, ransom notes, negotiations, press, SEC filings, CSIRT contacts), so the count is justified. It feels slightly over-packed rather than redundant.
The tool surface gives complete read-only coverage of the exposed domain: every artifact type has listing plus retrieval, with navigation helpers (build/decode victim ID, sector/group enumerations) that avoid dead ends. Since this is an intelligence/retrieval API, write operations are not an expected part of the lifecycle.