# Rösti Threat Intel (remote · mcp.rosti.dev)

Look up IOCs and search threat-intel reports, YARA rules, MITRE ATT&CK ids and CVEs from rosti.dev

- Trust score: 79/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.rosti.dev`: 79/100 (this document), [markdown](https://verifymcp.io/servers/dev-rosti-rosti/mcp.md), [page](https://verifymcp.io/servers/dev-rosti-rosti/mcp)

## Channel facts

- Endpoint: `https://mcp.rosti.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.1`

## 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-11-21.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1992 tokens (~181/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 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 Rösti Threat Intel MCP server?

Rösti Threat Intel is a hosted endpoint at https://mcp.rosti.dev/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 dev-rosti-rosti 'https://mcp.rosti.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-rosti-rosti": {
      "url": "https://mcp.rosti.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-rosti-rosti": {
      "type": "http",
      "url": "https://mcp.rosti.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-rosti-rosti]
url = "https://mcp.rosti.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-rosti-rosti": {
      "type": "remote",
      "url": "https://mcp.rosti.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-rosti-rosti --url 'https://mcp.rosti.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-rosti-rosti:
    url: "https://mcp.rosti.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-rosti-rosti": {
      "Transport": "http",
      "Url": "https://mcp.rosti.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-rosti-rosti -t streamable-http -u 'https://mcp.rosti.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-rosti-rosti": {
      "type": "http",
      "url": "https://mcp.rosti.dev/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-11-21 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-08 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-06 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (11)

### `lookup_iocs` (~296 tokens)

Look up IOCs

Check many IOCs (indicators of compromise) at once against Rösti's
threat-intelligence reports.

Defanged values (hxxps://evil[.]com, 1.2.3[.]4, user[at]evil[.]com) are
refanged before the lookup; `refanged` shows which. Matching is exact, with a
case-insensitive fallback. For each value that is found, returns the reports
it appears in (newest first) with the IOC's type, category, tags, IDS flag,
comment and false-positive risk. Values that are not found are listed in
\`not_found`. Every value is also checked against the Rösti False Positive
Warninglist (popular domains, public DNS resolvers, ...): found values carry
\`false_positive_verdict`, not-found values appear in `false_positive_verdicts`;
values without a verdict are left out. Use lookup_ioc for all matches of a
single value.

Input parameters:

- `max_matches_per_value` (integer): Maximum number of reports listed per found value
- `values` (array, required): IOC values such as IP addresses, domains, URLs, file hashes (MD5, SHA-1, SHA-256) or e-mail addresses, plain or defanged (e.g. hxxps://evil[.]com). Surrounding whitespace and duplicates are ignored.…

Output parameters:

- `false_positive_verdicts` (object): Rösti False Positive Warninglist verdicts for values in not_found, by value; values without a verdict are left out. Found values carry theirs in results.
- `not_found` (array): Values that were not found
- `refanged` (object): Defanged inputs and the value searched for each, e.g. {'evil[.]com': 'evil.com'}
- `results` (array): Values that were found, in request order
- `summary` (object)

### `lookup_ioc` (~234 tokens)

Look up an IOC

Check whether one IOC (indicator of compromise) appears in Rösti's
threat-intelligence reports.

A defanged value (hxxps://evil[.]com, 1.2.3[.]4) is refanged before the
lookup; `input` then shows the value as given. Matching is exact, with a
case-insensitive fallback. Returns every report the value appears in (newest
first, up to max_matches) with the IOC's type, category, tags, IDS flag,
comment and false-positive risk. Also checks the value against the Rösti
False Positive Warninglist (popular domains, public DNS resolvers, ...) and
returns its verdict in `false_positive_verdict`, also when Rösti does not
know the value; null when the warninglist has no verdict.

Input parameters:

- `max_matches` (integer): Maximum number of reports listed
- `value` (string, required): One IOC value, e.g. an IP address, domain, URL, file hash or e-mail address, plain or defanged (e.g. hxxps://evil[.]com)

Output parameters:

- `false_positive_verdict`: Verdict of the Rösti False Positive Warninglist; null when it has none
- `found` (boolean)
- `input`: The value as given, when it was defanged and refanged before the lookup
- `match_count` (integer): Number of reports the value appears in
- `matches` (array): Matches, newest report first
- `matches_omitted` (integer): Matches not included because of the max_matches limit
- `value` (string): The looked-up value (trimmed, refanged)

### `search_iocs` (~262 tokens)

Search IOCs

Search IOCs across all Rösti reports by text, type, tag, category and
creation time. Without filters, lists IOCs from all reports.

Each IOC carries its report id (use get_report for the report), type,
category, tags, IDS flag, comment and false-positive risk. Use lookup_ioc
or lookup_iocs to check whether specific values are known.

Input parameters:

- `categories`: IOC categories, e.g. network_activity (see describe_taxonomy)
- `cursor`: next_cursor from a previous call, to get the next page
- `exact` (boolean): Require the value or comment to equal the query instead of containing it
- `limit` (integer): IOCs per page
- `query`: Text to find in IOC values or comments, e.g. 'mcrosoft' or 'C2 server'. Defanged values are refanged.
- `since`: Only IOCs created or updated after this date (YYYY-MM-DD) or timestamp (YYYY-MM-DDTHH:MM:SSZ)
- `tags`: IOC tags, e.g. c2, phishing (see describe_taxonomy)
- `types`: IOC types, e.g. domain, ip-dst, sha256 (see describe_taxonomy)

Output parameters:

- `iocs` (array)
- `next_cursor`: Pass as cursor to get the next page; null if there are no more
- `total`: Total number of matching IOCs

### `search_reports` (~245 tokens)

Search reports

Search Rösti's threat-intelligence reports by text, source, CVE, MITRE
ATT&CK id and publication date.

Returns report summaries: title, date, source, authors, tags, counts of IOCs,
YARA rules and MITRE ids, and links to the original report and rosti.dev.
Use get_report for the details of one report.

Input parameters:

- `cursor`: next_cursor from a previous call, to get the next page
- `cves`: Reports referencing any of these CVEs, e.g. CVE-2021-44228
- `limit` (integer): Reports per page
- `mitre_ids`: Reports referencing any of these MITRE ATT&CK ids, e.g. T1566.001
- `published_after`: Reports published on or after this date (YYYY-MM-DD)
- `published_before`: Reports published on or before this date (YYYY-MM-DD)
- `query`: Text to find in report titles or authors, e.g. 'lumma'
- `sort` (string): Sort order
- `sources`: Source ids, e.g. asec, crowdstrike (see list_sources)

Output parameters:

- `next_cursor`: Pass as cursor to get the next page; null if there are no more
- `reports` (array)
- `total`: Total number of matching reports

### `get_report` (~89 tokens)

Get a report

Get one Rösti report: metadata, MITRE ATT&CK ids, CVEs, available export
formats, and how many of its IOCs there are per type and per tag.

Use list_report_iocs for the IOCs themselves and get_yara_rules for its
YARA rules.

Input parameters:

- `report_id` (string, required): Rösti report id, e.g. dq13KaQv

Output parameters:

- `authors` (array)
- `cves` (array): CVEs referenced in the report
- `date`: Publication date (YYYY-MM-DD)
- `export_formats` (array): Available downloads
- `id` (string): Rösti report id
- `ioc_breakdown_complete` (boolean): False if ioc_types/ioc_tags were counted from the first 1000 IOCs only
- `ioc_count`
- `ioc_tags` (object): Number of IOCs per tag
- `ioc_types` (object): Number of IOCs per IOC type
- `last_updated`: When Rösti last updated the report
- `mitre` (array): MITRE ATT&CK ids referenced in the report
- `mitre_id_count`
- `rosti_url`: The report on rosti.dev
- `source_id`
- `source_name`
- `tags` (array)
- `title` (string): Report title (third-party text)
- `url` (string): URL of the original report
- `yara_rule_count`
- `yara_rules_hidden` (boolean): True if the report's YARA rules are hidden at the publisher's request

### `list_report_iocs` (~180 tokens)

List a report's IOCs

List the IOCs of one Rösti report, optionally filtered by type, tag,
category or text.

IOCs with the same entity_ref belong together, e.g. the MD5, SHA-1 and
SHA-256 of one file. Each IOC carries its IDS flag and false-positive risk.

Input parameters:

- `categories`: IOC categories, e.g. network_activity
- `cursor`: next_cursor from a previous call, to get the next page
- `limit` (integer): IOCs per page
- `query`: Text to find in IOC values or comments
- `report_id` (string, required): Rösti report id, e.g. dq13KaQv
- `tags`: IOC tags, e.g. c2, phishing
- `types`: IOC types, e.g. domain, ip-dst, sha256

Output parameters:

- `iocs` (array)
- `next_cursor`: Pass as cursor to get the next page; null if there are no more
- `total`: Total number of matching IOCs

### `get_yara_rules` (~48 tokens)

Get YARA rules

Get the YARA rules published with one Rösti report, with their full source.

Input parameters:

- `report_id` (string, required): Rösti report id, e.g. dq13KaQv

Output parameters:

- `hidden` (boolean): True if the rules are hidden at the publisher's request
- `note`
- `report_id` (string)
- `rules` (array)

### `find_related_reports` (~67 tokens)

Find related reports

Find other Rösti reports that share IOCs with one report, most shared
IOCs first, with the shared values.

Input parameters:

- `limit` (integer): Maximum number of related reports
- `report_id` (string, required): Rösti report id, e.g. dq13KaQv

Output parameters:

- `complete` (boolean): False if the report has more than 1000 correlations and only the first 1000 were used
- `related` (array): Most shared IOCs first
- `related_total` (integer): Number of related reports found
- `report_id` (string)

### `get_export_link` (~101 tokens)

Get an export link

Get a download link for one report export, e.g. CSV or MISP.

The link is signed and expires after 15 minutes; it is meant to be opened by
the user, not downloaded here.

Input parameters:

- `format` (string, required): Export format id, e.g. csv or misp; get_report lists the formats available for a report
- `report_id` (string, required): Rösti report id, e.g. dq13KaQv

Output parameters:

- `expires_in_minutes` (integer)
- `format` (string)
- `report_id` (string)
- `url` (string): Signed download URL

### `list_sources` (~101 tokens)

List sources

List the publishers whose reports Rösti collects (vendor blogs, CERTs,
researchers), with report counts, the newest report date and whether the
source is still active. Source ids work as the sources filter of
search_reports.

Input parameters:

- `cursor`: next_cursor from a previous call, to get the next page
- `limit` (integer): Sources per page
- `query`: Text to find in source names, e.g. 'crowdstrike'

Output parameters:

- `next_cursor`
- `sources` (array)
- `total`

### `describe_taxonomy` (~53 tokens)

Describe the taxonomy

List the values Rösti uses for IOC types, IOC tags (with descriptions),
IOC categories and export formats, and explain the false-positive risk
scale. Use these values for the filters of the search and list tools.

Output parameters:

- `categories` (array): Values for IOC category filters
- `export_formats` (array): Export and feed file formats
- `false_positive_risk` (string)
- `ioc_tags` (array): Values for IOC tag filters
- `ioc_types` (array): Values for IOC type filters

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-rosti-rosti/mcp#diagnostics

## Score history

- 2026-11-21: 79
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 76
- 2026-11-15: 76
- 2026-11-14: 75
- 2026-11-13: 75
- 2026-11-12: 75
- 2026-11-11: 74
- 2026-11-10: 74
- 2026-11-09: 73
- 2026-11-08: 73
- 2026-11-07: 72
- 2026-11-06: 72
- 2026-11-05: 71
- 2026-11-04: 71

## Common questions

### What is the Rösti Threat Intel MCP server?

Rösti Threat Intel is an MCP server listed in the public MCP registry as dev.rosti/rosti. Look up IOCs and search threat-intel reports, YARA rules, MITRE ATT&CK ids and CVEs from rosti.dev. This page covers its hosted endpoint (https://mcp.rosti.dev/mcp).

### Is the Rösti Threat Intel MCP server safe to use?

Rösti Threat Intel scores 79 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 Rösti Threat Intel MCP server expose?

Rösti Threat Intel exposes 11 tools: lookup_iocs, lookup_ioc, search_iocs, search_reports, get_report, and 6 more. Their descriptions and schemas cost roughly 1,676 tokens of context every time the server is loaded.

### Does the Rösti Threat Intel MCP server require authentication?

No. We connected to Rösti Threat Intel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Rösti Threat Intel MCP server still maintained?

Rösti Threat Intel is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Rösti Threat Intel MCP server?

VerifyMCP ran 13 checks on Rösti Threat Intel, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.rosti.dev/mcp
- Website: https://rosti.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/dev-rosti-rosti/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-rosti-rosti/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-rosti-rosti/mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-rosti-rosti/mcp
