Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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

Available components

+4 this week 79 Trust /100

Last scanned (14 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security77
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 15 Nov 26 +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.

  • 12 Nov 26 +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.

  • 10 Nov 26 +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.

  • 8 Nov 26 +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.

  • 6 Nov 26 +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.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.rosti.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=rosti.dev CN=YE2,O=Let's Encrypt,C=US 11 Nov 2026 9 Feb 2027 ECDSA 256 ECDSA-SHA384 5059dd40498df8d09d90422dca865e2aadf
SANs: *.rosti.dev, rosti.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.rosti.dev. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
rosti.dev. DS published 2371 13 Verified
mcp.rosti.dev. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.rosti.dev/mcp Verified 200
http (plaintext) http://mcp.rosti.dev/mcp HTTPS enforced 301 https://mcp.rosti.dev/mcp
MCP tools · 11 exposed · ~1,676 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
describe_taxonomy ~53

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
categoriesarrayyesValues for IOC category filters
export_formatsarrayyesExport and feed file formats
false_positive_riskstring––
ioc_tagsarrayyesValues for IOC tag filters
ioc_typesarrayyesValues for IOC type filters

No examples provided.

find_related_reports ~67

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

NameTypeReqDescription
limitinteger–Maximum number of related reports
report_idstringyesRösti report id, e.g. dq13KaQv
NameTypeReqDescription
completebooleanyesFalse if the report has more than 1000 correlations and only the first 1000 were used
relatedarrayyesMost shared IOCs first
related_totalintegeryesNumber of related reports found
report_idstringyes–

No examples provided.

get_export_link ~101

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.

NameTypeReqDescription
formatstringyesExport format id, e.g. csv or misp; get_report lists the formats available for a report
report_idstringyesRösti report id, e.g. dq13KaQv
NameTypeReqDescription
expires_in_minutesinteger––
formatstringyes–
report_idstringyes–
urlstringyesSigned download URL

No examples provided.

get_report ~89

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.

NameTypeReqDescription
report_idstringyesRösti report id, e.g. dq13KaQv
NameTypeReqDescription
authorsarray––
cvesarray–CVEs referenced in the report
date––Publication date (YYYY-MM-DD)
export_formatsarray–Available downloads
idstringyesRösti report id
ioc_breakdown_completeboolean–False if ioc_types/ioc_tags were counted from the first 1000 IOCs only
ioc_count–––
ioc_tagsobject–Number of IOCs per tag
ioc_typesobject–Number of IOCs per IOC type
last_updated––When Rösti last updated the report
mitrearray–MITRE ATT&CK ids referenced in the report
mitre_id_count–––
rosti_url––The report on rosti.dev
source_id–––
source_name–––
tagsarray––
titlestringyesReport title (third-party text)
urlstringyesURL of the original report
yara_rule_count–––
yara_rules_hiddenboolean–True if the report's YARA rules are hidden at the publisher's request

No examples provided.

get_yara_rules ~48

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

NameTypeReqDescription
report_idstringyesRösti report id, e.g. dq13KaQv
NameTypeReqDescription
hiddenboolean–True if the rules are hidden at the publisher's request
note–––
report_idstringyes–
rulesarrayyes–

No examples provided.

list_report_iocs ~180

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.

NameTypeReqDescription
categories––IOC categories, e.g. network_activity
cursor––next_cursor from a previous call, to get the next page
limitinteger–IOCs per page
query––Text to find in IOC values or comments
report_idstringyesRösti report id, e.g. dq13KaQv
tags––IOC tags, e.g. c2, phishing
types––IOC types, e.g. domain, ip-dst, sha256
NameTypeReqDescription
iocsarrayyes–
next_cursor––Pass as cursor to get the next page; null if there are no more
total––Total number of matching IOCs

No examples provided.

list_sources ~101

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.

NameTypeReqDescription
cursor––next_cursor from a previous call, to get the next page
limitinteger–Sources per page
query––Text to find in source names, e.g. 'crowdstrike'
NameTypeReqDescription
next_cursor–––
sourcesarrayyes–
total–––

No examples provided.

lookup_ioc ~234

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.

NameTypeReqDescription
max_matchesinteger–Maximum number of reports listed
valuestringyesOne IOC value, e.g. an IP address, domain, URL, file hash or e-mail address, plain or defanged (e.g. hxxps://evil[.]com)
NameTypeReqDescription
false_positive_verdict––Verdict of the Rösti False Positive Warninglist; null when it has none
foundbooleanyes–
input––The value as given, when it was defanged and refanged before the lookup
match_countintegeryesNumber of reports the value appears in
matchesarrayyesMatches, newest report first
matches_omittedinteger–Matches not included because of the max_matches limit
valuestringyesThe looked-up value (trimmed, refanged)

No examples provided.

lookup_iocs ~296

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.

NameTypeReqDescription
max_matches_per_valueinteger–Maximum number of reports listed per found value
valuesarrayyesIOC 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.…
NameTypeReqDescription
false_positive_verdictsobject–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_foundarrayyesValues that were not found
refangedobject–Defanged inputs and the value searched for each, e.g. {'evil[.]com': 'evil.com'}
resultsarrayyesValues that were found, in request order
summaryobjectyes–

No examples provided.

search_iocs ~262

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.

NameTypeReqDescription
categories––IOC categories, e.g. network_activity (see describe_taxonomy)
cursor––next_cursor from a previous call, to get the next page
exactboolean–Require the value or comment to equal the query instead of containing it
limitinteger–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)
NameTypeReqDescription
iocsarrayyes–
next_cursor––Pass as cursor to get the next page; null if there are no more
total––Total number of matching IOCs

No examples provided.

search_reports ~245

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.

NameTypeReqDescription
cursor––next_cursor from a previous call, to get the next page
cves––Reports referencing any of these CVEs, e.g. CVE-2021-44228
limitinteger–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'
sortstring–Sort order
sources––Source ids, e.g. asec, crowdstrike (see list_sources)
NameTypeReqDescription
next_cursor––Pass as cursor to get the next page; null if there are no more
reportsarrayyes–
total––Total number of matching reports

No examples provided.

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.

remote · mcp.rosti.dev

# add to Claude Code
claude mcp add --transport http dev-rosti-rosti 'https://mcp.rosti.dev/mcp'
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.