Skip to main content
Glama

Cybersecurity Threat Intelligence MCP

by io.github.FoundryNet
OverviewDiscussionsAdmin

Server Details

CVE search, vulnerability database, EPSS exploit prediction, KEV, IP reputation & threat feed.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL
Repository
FoundryNet/cyber-intel-mcp
GitHub Stars
0
Server Listing
Cybersecurity Threat Intelligence MCP

TDQS

A4.3/5.0

Scored across 9 tools

Disambiguation5/5

Each tool targets a distinct resource: domain, IP, CVE, threat feed, daily brief, product scan, and meta-info. The only closely related pair (brief_summary vs daily_brief) is explicitly differentiated as a cheap sample vs full brief, so no real ambiguity exists.

Naming Consistency4/5

All tool names use lowercase snake_case, but the grammatical pattern is mixed: some are verb_noun (check_domain, check_ip, search_cve) while others are noun_noun or adjective_noun (cve_detail, daily_brief, threat_feed, vulnerability_scan, mint_info, brief_summary). The style is consistent, but the verb-first convention is not uniform.

Tool Count5/5

Nine tools cover the core threat-intelligence workflows without bloat: reputation lookups, CVE search/details, vulnerability scanning, briefs, and a live feed. This is a well-scoped count for the domain.

Completeness4/5

The server covers IP and domain reputation, CVE research, product scanning, and daily briefs, but lacks a single-tool lookup for hash or URL reputation (only available via the generic threat_feed). This is a workable minor gap since the feed can filter by those types, but a dedicated check_hash or check_url tool would make the surface fully complete.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 7 tool updates
    • Changedbrief_summary1 field changed
      • changedInput schema / properties / payment_tx / description
        Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."
    • Changedcheck_domain1 field changed
      • changedInput schema / properties / payment_tx / description
        Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."
    • Changedcheck_ip1 field changed
      • changedInput schema / properties / payment_tx / description
        Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."
    • Changeddaily_brief2 fields changed
      • changedInput schema / properties / payment_tx / description
        Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."
      • changedInput schema / properties / stripe_token / description
        Previous value: -"Stripe Checkout Session id (cs_…), when re-calling after\npaying the Stripe payment link (alternative to x402). Can also be\nsupplied via the X-Stripe-Token header."New value: +"Stripe Checkout Session id (cs_…), when re-calling after\npaying the Stripe payment link (alternative to the metered rail). Can\nalso be supplied via the X-Stripe-Token header."
    • Changedsearch_cve1 field changed
      • changedInput schema / properties / payment_tx / description
        Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."
    • Changedthreat_feed1 field changed
      • changedInput schema / properties / payment_tx / description
        Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."
    • Changedvulnerability_scan1 field changed
      • changedInput schema / properties / payment_tx / description
        Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."
  2. 1 tool update
    • Addedbrief_summary
  3. 1 tool update
    • Changeddaily_brief1 field changed
      • addedInput schema / properties / stripe_token
        Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Stripe Checkout Session id (cs_…), when re-calling after\npaying the Stripe payment link (alternative to x402). Can also be\nsupplied via the X-Stripe-Token header."
+}
  4. 1 tool update
    • Addeddaily_brief
  5. 7 tool updates
    • First observedcheck_domain
    • First observedcheck_ip
    • First observedcve_detail
    • First observedmint_info
    • First observedsearch_cve
    • First observedthreat_feed
    • First observedvulnerability_scan

Related MCP Connectors

Related MCP Servers

Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources