Cybersecurity Threat Intelligence MCP
REMOTE · CYBER-INTEL-MCP-PRODUCTION.UP.RAILWAY.APP
CVE search, vulnerability database, EPSS exploit prediction, KEV, IP reputation & threat feed.
Available components
Last scanned (2 months ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 29 Jul 2026.
Category Security
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 502. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety–
Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 19 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 12 Aug 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 −12
- HSTS header: fail → unverified ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- 9 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 7 Aug 26 0
- HSTS header: unverified → fail ▼ security
- Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 502. security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- 1 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
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 19 Aug 2026 · Probed https://cyber-intel-mcp-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 insecure
Validation of cyber-intel-mcp-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 | 502 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cyber-intel-mcp-production.up.railway.app/mcp | HTTP error | 502 | |
| http (plaintext) | http://cyber-intel-mcp-production.up.railway.app/mcp | HTTPS enforced | 301 | https://cyber-intel-mcp-production.up.railway.app/mcp |
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 →
brief_summary ~169
Get the top 5 signals from today's threat brief as structured JSON — a cheap sample of the full daily_brief. Returns the day's highest-priority items (no prose) so an agent can decide whether to buy the full brief. PAID: $0.50 (vs $15 for the full daily_brief). Defaults to today (UTC). On a 402, settle the returned payment request and re-call with the SAME args plus payment_tx=<reference>. An Authorization: Bearer fnet_ key bypasses payment.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | stable id for your agent (scopes the free-tier counter). |
| date | – | – | brief date YYYY-MM-DD (default today, UTC). |
| payment_tx | – | – | payment transaction reference, when re-calling after a 402. |
Structured output declared, but exposes no named fields.
No examples provided.
check_domain ~146
Check domain reputation — threat indicators, OTX pulse associations, and threat classification for a domain. Threat intel from AlienVault OTX. PAID: $0.01 per query after the daily free allowance (25/day). On a 402, settle the returned payment request and re-call with the SAME args plus payment_tx=<reference>. An Authorization: Bearer fnet_ key bypasses it.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | stable id for your agent (scopes the free-tier counter). |
| domain | string | yes | the domain to check, e.g. "example.com". |
| payment_tx | – | – | payment transaction reference, when re-calling after a 402. |
Structured output declared, but exposes no named fields.
No examples provided.
check_ip ~150
Check IP reputation — abuse reports, threat type, confidence, ISP, and OTX pulse associations for an IP. Threat intel combining AbuseIPDB and AlienVault OTX. PAID: $0.01 per query after the daily free allowance (25/day). On a 402, settle the returned payment request and re-call with the SAME args plus payment_tx=<reference>. An Authorization: Bearer fnet_ key bypasses it.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | stable id for your agent (scopes the free-tier counter). |
| ip_address | string | yes | the IPv4 address to check. |
| payment_tx | – | – | payment transaction reference, when re-calling after a 402. |
Structured output declared, but exposes no named fields.
No examples provided.
cve_detail ~109
Get the full record for a single CVE from the vulnerability database — CVSS v3 breakdown (score/severity/vector/attack vector/complexity), EPSS exploit-prediction probability + percentile, CISA KEV status + due date, CWE, affected products, and references. Sources: NVD, EPSS, CISA KEV, GHSA. FREE.
| Name | Type | Req | Description |
|---|---|---|---|
| cve_id | string | yes | e.g. "CVE-2021-44228". |
Structured output declared, but exposes no named fields.
No examples provided.
daily_brief ~275
Get the curated daily threat-intelligence brief — the day's most significant signals in one package: critical CVEs with high EPSS exploit-prediction, new CISA KEV additions, the most-exploitable vulnerabilities, and active threat indicators. Threat intel from NVD, CISA KEV, EPSS, GHSA, AbuseIPDB, and OTX. Each brief carries verifiable provenance so a buyer can confirm it was produced by this server, unaltered. PAID: $15 per brief. Defaults to today (UTC); a brief expires at the next midnight UTC. On a 402, settle the returned payment request and re-call with the SAME args plus payment_tx=<reference>. An Authorization: Bearer fnet_ key bypasses payment.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | stable id for your agent (scopes the free-tier counter). |
| date | – | – | brief date YYYY-MM-DD (default today, UTC). |
| payment_tx | – | – | payment transaction reference, when re-calling after a 402. |
| stripe_token | – | – | Stripe Checkout Session id (cs_…), when re-calling after paying the Stripe payment link (alternative to the metered rail). Can also be supplied via the X-Stripe-Token header. |
Structured output declared, but exposes no named fields.
No examples provided.
mint_info ~89
Get FoundryNet Data Network info and result-provenance details. FREE. Returns how this server attaches verifiable provenance to your agent's security/threat-intelligence analysis, plus the sister data servers (gov-contracts, brand-intel, patent-intel, financial-signals, weather-intel, compliance, academic-intel, fact-check, oss-intel, social-intel).
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
search_cve ~302
Search CVEs in the vulnerability database by keyword, CVSS severity/score, EPSS exploit-prediction likelihood, attack vector, recency, or CISA KEV status. Returns CVSS, EPSS, KEV flag, and affected products, newest first. Threat intel from NVD, EPSS, CISA KEV, and GHSA. PAID: $0.01 per query after a daily free allowance (25/day). On a 402, settle the returned payment request and re-call with the SAME args plus payment_tx=<reference>. agent_id scopes your allowance; an Authorization: Bearer fnet_ key bypasses it.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | stable id for your agent (scopes the free-tier counter). |
| attack_vector | – | – | network | adjacent | local | physical. |
| days_back | – | – | only CVEs published in the last N days. |
| is_kev | – | – | true → only CISA Known-Exploited Vulnerabilities. |
| keyword | – | – | text matched against the CVE description. |
| limit | integer | – | max rows (1-200, default 50). |
| min_cvss | – | – | minimum CVSS v3 base score (0-10). |
| min_epss | – | – | minimum EPSS exploit probability (0-1). |
| payment_tx | – | – | payment transaction reference, when re-calling after a 402. |
| severity | – | – | critical | high | medium | low. |
Structured output declared, but exposes no named fields.
No examples provided.
threat_feed ~201
Pull the recent threat-intelligence feed — real-time threat indicators (IPs, domains, hashes, URLs) from AlienVault OTX pulses and reputation checks, filterable by type, threat, confidence, and recency. PAID: $0.01 per query after the daily free allowance (25/day). On a 402, settle the returned payment request and re-call with the SAME args plus payment_tx=<reference>. An Authorization: Bearer fnet_ key bypasses it.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | stable id for your agent (scopes the free-tier counter). |
| hours_back | – | – | only indicators seen in the last N hours. |
| indicator_type | – | – | ip | domain | hash | url. |
| min_confidence | – | – | minimum confidence 0-100. |
| payment_tx | – | – | payment transaction reference, when re-calling after a 402. |
| threat_type | – | – | malware | phishing | botnet | scanner | spam. |
Structured output declared, but exposes no named fields.
No examples provided.
vulnerability_scan ~207
Scan a product/vendor/CPE for all known vulnerabilities, sorted by EPSS exploit-prediction likelihood with CISA KEV flags — the "should I be worried about this dependency?" security scanning tool. Threat intel from NVD, EPSS, CISA KEV, and GHSA. Premium. PAID: $0.02 per query after the daily free allowance (25/day). On a 402, settle the returned payment request and re-call with the SAME args plus payment_tx=<reference>. An Authorization: Bearer fnet_ key bypasses it.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | stable id for your agent (scopes the free-tier counter). |
| cpe | – | – | a CPE string to match exactly. |
| payment_tx | – | – | payment transaction reference, when re-calling after a 402. |
| product_name | – | – | product/library/software name, e.g. "log4j". |
| vendor | – | – | vendor name, e.g. "apache". |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Cybersecurity Threat Intelligence MCP server?
Cybersecurity Threat Intelligence MCP is a hosted endpoint at https://cyber-intel-mcp-production.up.railway.app/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 · cyber-intel-mcp-production.up.railway.app
claude mcp add --transport http foundrynet-cyber-intel-mcp 'https://cyber-intel-mcp-production.up.railway.app/mcp'
What is the Cybersecurity Threat Intelligence MCP server?
Cybersecurity Threat Intelligence MCP is listed in the public MCP registry as io.github.FoundryNet/cyber-intel-mcp. CVE search, vulnerability database, EPSS exploit prediction, KEV, IP reputation & threat feed. This page covers its hosted endpoint (https://cyber-intel-mcp-production.up.railway.app/mcp).
Is the Cybersecurity Threat Intelligence MCP server safe to use?
Cybersecurity Threat Intelligence MCP scores 0 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 Cybersecurity Threat Intelligence MCP server expose?
Cybersecurity Threat Intelligence MCP exposes 9 tools: search_cve, cve_detail, check_ip, check_domain, vulnerability_scan, and 4 more. Their descriptions and schemas cost roughly 1,648 tokens of context every time the server is loaded.
Does the Cybersecurity Threat Intelligence MCP server require authentication?
No. We connected to Cybersecurity Threat Intelligence MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Cybersecurity Threat Intelligence MCP server still maintained?
Cybersecurity Threat Intelligence MCP has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 29 July 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.