Nullcone Threat Intelligence

io.github.maco144Published by GitHub account maco144v0.1.0Updated Oct 24, 2026

Real-time threat intel for AI agents: 890K+ IOCs incl. prompt-injection & AI-skill threats

VerifiedStreamable HTTPWeb executableSecurity & MonitoringAI & ML

Overview

AI-generated overview

A hosted threat-intelligence MCP server that lets an assistant look up IOCs, check prompts and AI skills for malicious patterns, and contribute indicators to a

What you can do
Look up and browse threat indicators: exact IOC lookup, recent threats, malware families, and filtering by IOC type, plus aggregate stats and incremental sync since a last ID. Submit indicators individually or in batches to a shared feed, report detections, and vote on likely false positives. Screen prompts and text for known prompt-injection patterns, with cache warming and cache statistics. Vet AI skills and MCP tool definitions before use: skill hash validation, skill content scanning, and tool-metadata fingerprinting for injection or exfiltration patterns. Monitor MCP registry tooling: flagged tools and registry monitoring statistics. Manage live threat subscriptions: subscribe, drain,
When to use it
Use it when an assistant needs to check IPs, domains, URLs, hashes, CVEs, prompt-injection payloads, or AI-skill and MCP-tool definitions against a shared threat feed, or when you want to contribute detections and receive live threat updates without polling.
Requirements
Remote streamable HTTP endpoint; no signup, token, or API key is required for the hosted service. Self-hosting needs Python with the requirements file, or Docker, and the MCP_TRANSPORT, MCP_PORT, and MCP_PUBLIC settings.
Before you install
Submitting IOCs, reporting detections, and voting publish data to a shared network visible to other agents; do not send sensitive or internal indicators. Revocation and other destructive tools are disabled on the public endpoint but available when self-hosted. The server is a third-party service, so lookups and submissions leave your machine.

Installation

In SourceWeft

  1. Open Nullcone Threat Intelligence in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.maco144%2Fnullcone/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "nullcone-threat-intelligence": {
      "type": "http",
      "url": "https://nullcone.ai/mcp"
    }
  }
}

README

Nullcone MCP Server

Real-time threat intelligence for AI agents, exposed as a Model Context Protocol server. Check IPs, domains, URLs, hashes, CVEs, prompt-injection payloads, and malicious AI-skill / MCP-tool definitions against the Nullcone network — 890K+ IOCs, free, no API key.

Backed by nullcone.ai.

Use it (hosted — nothing to install)

The server is hosted at https://nullcone.ai/mcp over streamable HTTP. Add it to any MCP client:

Claude Code

bash
claude mcp add --transport http nullcone https://nullcone.ai/mcp

Cursor / other MCP clients — add to your MCP config:

json
{  "mcpServers": {    "nullcone": {      "url": "https://nullcone.ai/mcp"    }  }}

No signup or token required. Read tools and IOC submission are open; destructive tools (e.g. revoke_ioc) are disabled on the public endpoint.

Tools

30+ tools including:

  • lookup_ioc(value) — check any indicator against the feed
  • recent_threats(limit, min_severity) — current threat picture
  • submit_ioc(...) / submit_batch(...) — contribute indicators
  • check_prompt(...) — sub-millisecond prompt-injection lookup
  • validate_skill(...) / scan_skill_content(...) — vet MCP tools / AI skills before loading
  • poll_since(last_id) — incremental sync, no persistent connection
  • get_stats(), list_families(), search_by_type(...), and more

Resources: threat://stats, threat://recent, threat://families, threat://family/{name}, threat://ioc/{value}. Prompts: analyze_ioc, triage_alert, threat_brief.

Self-host

The server is built on the public nullcone SDK.

bash
pip install -r requirements.txtMCP_TRANSPORT=streamable-http MCP_PORT=8001 python server.py

Or with Docker:

bash
docker build -t nullcone-mcp .docker run -p 8001:8001 nullcone-mcp

Set MCP_PUBLIC=1 to run an anonymous public endpoint (disables destructive tools); omit it for full local control over stdio (MCP_TRANSPORT=stdio).

License

Rising Sun License v1.0 — see LICENSE. Free for individuals and small teams.

Source: README.md at commit dc20249

Tools

30

submit_ioc

Submit a threat indicator (IOC) to the shared intelligence network. The IOC is automatically classified into a malware family, metadata is compressed, and deduplication is handled atomically. All subscribed agents see the new IOC instantly. Args: ioc_type: IOC category. One of: hash_md5, hash_sha1, hash_sha256, ip, ip_port, domain, url, yara, email, mutex, registry, filepath, asn, ja3, imphash, cve, prompt, skill value: The indicator value (e.g. "evil.example.com", "1.2.3.4") severity: 0-10. Use Severity enum values: 1=info, 3=low, 5=medium, 7=high, 9=critical confidence: 0-100 confidence score context: Free-text context about why this is malicious tags: List of tags (e.g. ["c2", "phishing", "ransomware"]) source: Origin of the intel (e.g. "honeypot", "sandbox", "osint") family_hint: Optional malware family name to skip auto-classification

Parameterstagsvaluerequiredsourcecontextioc_typerequiredseverityconfidencefamily_hint

submit_batch

Submit multiple IOCs in a single call. Preferred over looping submit_ioc for bulk ingest from honeypots, sandboxes, or feed processing. Each dict in `iocs` follows the same schema as submit_ioc parameters. Required keys: ioc_type, value. All others are optional. Returns one result dict per input IOC in the same order. Args: iocs: List of IOC dicts. Each must have 'ioc_type' and 'value'. Optional: severity, confidence, context, tags, source, family_hint

Parametersiocsrequired

lookup_ioc

Look up a threat signature by its exact IOC value. Returns the full signature record if found, including severity, family, detection count, and false positive votes. Args: value: The exact IOC value to search for (e.g. "evil.example.com")

Parametersvaluerequired

recent_threats

Return the most recently observed threat signatures. Args: limit: Max number of results to return (1-200) min_severity: Minimum severity level (0-10). Default 5 (medium+)

Parameterslimitmin_severity

family_threats

Return all threat signatures associated with a known malware family. Use list_families() first to discover available family names. Args: family_name: Exact malware family name (e.g. "emotet", "qbot", "cobalt_strike") limit: Max results to return (1-500). Default 50.

Parameterslimitfamily_namerequired

list_families

Return all known malware families in the intelligence database. Each entry includes the family name, description, and category. Use family_threats(family_name) to retrieve the IOCs for a specific family.

Takes no parameters.

search_by_type

Return threat signatures filtered by IOC type. Useful for pulling all known-bad IPs, all malicious domains, all malicious AI skill hashes, etc. Args: ioc_type: One of: hash_md5, hash_sha1, hash_sha256, ip, ip_port, domain, url, yara, email, mutex, filepath, asn, ja3, imphash, cve, prompt, skill limit: Max results to return (1-1000). Default 50. min_severity: Minimum severity (0-10). Default 0 (all).

Parameterslimitioc_typerequiredmin_severity

report_detection

Report that you detected and acted on a known threat signature. Increments the signature's detection count and creates a ThreatEvent visible to all other agents in real-time. Args: signature_id: ID of the ThreatSignature (from submit_ioc or lookup_ioc) action: Action taken. One of: logged, alerted, blocked, quarantined, eradicated context: Optional dict with additional context (process name, path, etc.)

Parametersactionrequiredcontextsignature_idrequired

vote_false_positive

Flag a threat signature as a likely false positive. When more than 20% of agents vote false positive on a signature, its `is_likely_fp` flag becomes True — a signal to review before blocking. Args: signature_id: ID of the ThreatSignature to flag reason: Optional explanation for the vote

Parametersreasonsignature_idrequired

poll_since

Fetch new threat signatures since a high-water mark ID. This is the recommended sync pattern — one call, get new data, persist next_id, disconnect. No persistent connection required. Call with last_id=0 on first run to get all signatures. Persist the returned next_id and pass it on the next call to get only new entries. If count == batch_size, call again immediately to drain backlog. Args: last_id: Last signature ID seen (0 for all). Persist this between calls. batch_size: Max signatures to return (1–5000) min_severity: Skip signatures below this severity (0–10)

Parameterslast_idbatch_sizemin_severity

get_stats

Return aggregate statistics for the threat intelligence database. Includes total signatures, known malware families, active agents, and total detection events.

Takes no parameters.

validate_skill

Synchronous SKILL IOC lookup — call this before loading or invoking any MCP tool/skill to check it against the Nullcone threat feed. This is the pre-invocation enforcement hook. Returns an allow/warn/block decision based on whether the skill hash is a known-malicious indicator. Args: skill_hash: SHA256 of the skill manifest (preferred identifier) skill_name: Human-readable skill name (for logging) manifest_url: URL of the skill manifest (fallback if hash unknown) Returns: risk: "clean" | "suspicious" | "malicious" action: "allow" | "warn" | "block" confidence: 0-100 signature_id: DB id of matching IOC (if found) family_name: Associated malware family (if known) reason: Human-readable explanation

Parametersskill_hashrequiredskill_namemanifest_url

scan_skill_content

Pre-execution content scan for skill/instruction files. Analyzes the full text of a skill (markdown, plain text, SKILL.md, etc.) for malicious patterns BEFORE the agent follows the instructions. This is the critical defense against remote skill-mediated credential exfiltration (CodeMax attack class, 2026-03-14) where model-level safety only fires AFTER the payload has already executed. Call this on any skill/instruction content fetched from the web before executing any of its steps. If should_block is True, refuse to proceed. Detection signals: - Download-and-execute chains (wget/curl → chmod +x → run) - Bootstrap file modification (.npmrc, NODE_OPTIONS, LD_PRELOAD) - Encrypted credential exfiltration (GPG, openssl → HTTP POST) - Credential access patterns (process.env, keychain, .env files) - Code obfuscation (base64 decode pipe to shell) - Multi-stage kill chain correlation Args: content: Full text content of the skill file source_url: URL where the skill was fetched from (for reporting) Returns: risk: "CLEAN" | "LOW" | "SUSPICIOUS" | "MALICIOUS" risk_score: 0.0–1.0 should_block: True if the skill should NOT be executed should_warn: True if the skill warrants user confirmation kill_chain: True if a multi-stage attack chain was detected signals: List of detection signals with categories and excerpts content_hash: SHA256 of the content (for IOC submission if malicious)

Parameterscontentrequiredsource_url

get_new_threats

Drain the live push-subscription buffer of threats received since the last call. Zero-polling — threats are delivered via SpacetimeDB WebSocket subscription and buffered server-side. Use this instead of poll_since() when you need sub-second latency without maintaining your own WebSocket connection. The MCP server maintains the subscription; you just drain the buffer on demand. Args: drain: If True (default), clear the buffer after returning. Set False to peek without consuming. Returns: signatures: list of new threat signatures received since last drain count: number of signatures returned buffered: total currently in buffer (equals count if drain=True) push_active: whether the background subscription is running

Parametersdrain

warm_prompt_cache

Load all PROMPT IOCs from SpacetimeDB into the in-memory hash set. Call once at startup (or after a major feed update) to populate the sub-1ms query cache. Subsequent check_prompt() calls require no network access. The cache auto-refreshes every 5 minutes in the background. Returns: loaded: Number of PROMPT IOC hashes loaded duration_ms: Time taken to warm the cache window_sizes: Token window sizes used for querying

Takes no parameters.

check_prompt

Check a prompt or text fragment for known PROMPT IOC patterns. Uses an in-memory hash set for sub-1ms token-level querying — no network calls after the cache is warmed. Slides a window of 3, 5, 8, and 10 tokens across the input and checks each window's canonical SHA256 against the PROMPT IOC feed. This is the primary real-time prompt injection detection endpoint. Call it on every user-supplied prompt before passing to the LLM. Args: text: The prompt text to check (raw, any length) auto_warm: If True and cache is empty, warm it first (adds ~300ms on first call only). Default True. Returns: matched: True if a known PROMPT IOC pattern was detected matched_hash: SHA256 of the matching token window (if matched) window_text: The matched token window text (if matched) window_size: Number of tokens in the matching window token_offset: Position in the token stream where match starts latency_us: Query latency in microseconds cache_size: Number of PROMPT IOC hashes currently cached

Parameterstextrequiredauto_warm

check_prompt_batch

Check multiple prompts for PROMPT IOC patterns in a single call. More efficient than calling check_prompt() in a loop — tokenization overhead is amortized and the cache reference is shared. Args: texts: List of prompt strings to check Returns: One result dict per input text, in the same order.

Parameterstextsrequired

prompt_cache_stats

Return PROMPT IOC cache statistics: size, hit rate, latency, refresh status. Use this to verify the cache is warmed and healthy before relying on check_prompt() for real-time detection.

Takes no parameters.

check_freshness

Validate that IOC threat intelligence is fresh enough for the named action. Call this before any high-risk agent action to ensure the TI snapshot is not stale. The check itself completes in <1ms (no network I/O). Action → staleness tier mapping: critical (≤30s): credential_access, keychain_access, execute_shell, sudo high (≤120s): load_skill, install_package, network_call, http_request medium (≤300s): file_write, file_delete, registry_write, env_write low (≤900s): file_read, list_directory, query_db, read_env Args: action: The action about to be executed. Unknown actions default to HIGH tier (120s limit). block_on_stale: If True and TI is stale, return an error dict that your agent should treat as a hard block. Default False (warn only). Returns: action: "allow" | "warn" | "block" tier: Staleness tier for this action staleness_s: Seconds since last successful sync max_staleness_s: Limit for this tier hwm: Current high-water mark latency_ms: Check latency (always <100ms) reason: Human-readable explanation

Parametersactionblock_on_stale

freshness_limits

Return the configured IOC freshness limits for all action tiers. Shows max staleness, warn threshold, and which actions belong to each tier. Use this to understand when check_freshness() will warn or block.

Takes no parameters.

fingerprint_tool_metadata

Analyze an MCP tool definition for instruction-injection and malicious patterns. Performs semantic fingerprinting of the tool's description, parameter schemas, and error templates — detecting credential exfiltration vectors, C2 callbacks, base64 payloads, authority spoofing, and injection phrase patterns. Also checks the tool hash against the SKILL IOC feed and the description against the PROMPT IOC feed for known-malicious matches. If track=True (default), the tool definition is compared against a stored baseline and semantic drift is detected on subsequent calls for the same tool. Args: tool_def: MCP tool definition dict. Expected keys: name, description, inputSchema (optional), annotations (optional). registry: Registry this tool came from ("mcp.so", "clawhub", "smithery", "npm", "pypi", "github", or "unknown"). track: If True, maintain baseline and detect drift across calls. Returns: tool_name: Tool name tool_hash: SHA256 of canonical tool definition risk: "clean" | "low" | "suspicious" | "malicious" risk_score: 0.0–1.0 should_block: True if risk == malicious should_warn: True if risk >= suspicious signals: List of detected signals with field, pattern, excerpt prompt_ioc_matched: True if description matched PROMPT IOC feed skill_ioc_matched: True if tool hash matched SKILL IOC feed latency_ms: Analysis latency drift: Drift result (if track=True and tool was seen before)

Parameterstrackregistrytool_defrequired

registry_monitor_stats

Return MCP registry monitoring statistics. Shows how many tool definitions are tracked, how many have been flagged, and the current drift detection rate.

Takes no parameters.

registry_flagged_tools

Return all MCP tools that have been flagged as suspicious or malicious. Includes tools flagged on initial ingestion (high-risk fingerprint) and tools that showed significant semantic drift on update.

Takes no parameters.

subscribe_threats

Open a named, stateful subscription to live threat push delivery. Returns a subscription_id. Pass it to drain_subscription() to collect the IOCs that have arrived since your last drain — zero polling, each caller gets their own isolated stream. Multiple subscribers receive independent copies of every matching IOC. Subscriptions expire after 1 hour of inactivity (no drain calls). Composition filters let you narrow the stream: - ioc_types: only deliver these IOC types (empty = all) - families: only deliver IOCs from these malware families (empty = all) - tags: only deliver IOCs with at least one of these tags (empty = all) Requires the MCP server to be running in SSE mode (MCP_TRANSPORT=sse) with a live SpacetimeDB push subscription active. Args: min_severity: Minimum severity to deliver (0-10). Default 5 (medium+). ioc_types: List of IOC types to include. E.g. ["skill","prompt","ip"]. Valid: hash_md5, hash_sha1, hash_sha256, ip, ip_port, domain, url, yara, email, mutex, filepath, asn, ja3, imphash, cve, prompt, skill. Empty = all types. families: List of malware family names to include. Empty = all. tags: List of tags — IOC must match at least one. Empty = all. Returns: subscription_id: Opaque ID — pass to drain_subscription() / unsubscribe() push_active: Whether the background push subscription is running filters: Echo of the composition filters applied

Parameterstagsfamiliesioc_typesmin_severity

drain_subscription

Drain the buffer of a stateful subscription created by subscribe_threats(). Returns all IOCs delivered to this subscription since the last drain. Each subscription is independent — draining yours does not affect others. Args: subscription_id: The ID returned by subscribe_threats() drain: If True (default), clear the buffer after returning. Set False to peek without consuming. Returns: signatures: List of new threat signatures count: Number of signatures returned buffered: Total signatures currently in buffer push_active: Whether the background push subscription is running

Parametersdrainsubscription_idrequired

unsubscribe

Cancel a stateful subscription and free its buffer. Call this when you no longer need the subscription to release memory. Subscriptions also auto-expire after 1 hour of inactivity. Args: subscription_id: The ID returned by subscribe_threats() Returns: status: "ok" if removed, "not_found" if already expired/removed drained: Number of unread signatures discarded on removal

Parameterssubscription_idrequired

list_subscriptions

List all active stateful push subscriptions on this MCP server instance. Returns metadata for each subscription (not the buffered IOCs themselves). Useful for inspecting what agents are currently subscribed and what filters they have configured.

Takes no parameters.

revoke_ioc

Revoke an IOC by its value hash, pushing the expiration event to all active subscriptions in real-time. Call this when an IOC is determined to be a false positive, expired, or superseded. Subscribed agents receive the revocation event on their next drain_subscription() call with event_type="revocation". Args: value_hash: SHA256 of {ioc_type}:{value.lower()} — same format as IOC.value_hash(). Obtainable from list_revocations() or the threat signature record. reason: One of: false_positive, expired, superseded, attribution_error, retracted. ioc_type: Original IOC type (optional, for subscriber filtering). Returns: event: Revocation event details. pushed: Number of active subscriptions notified.

Parametersreasonioc_typevalue_hashrequired

is_ioc_revoked

Check whether an IOC has been revoked. O(1) in-process lookup. Use this before acting on any cached threat intelligence to ensure the IOC has not been retracted since it was loaded. Args: value_hash: SHA256 of {ioc_type}:{value.lower()}. Returns: revoked: bool event: Revocation event details if revoked, null otherwise.

Parametersvalue_hashrequired

list_revocations

List recent IOC revocations, newest first. Args: limit: Maximum number of revocations to return (default 50). since_hours: Only return revocations newer than this many hours ago. 0 = no time filter (return all retained). Returns: revocations: List of revocation event dicts. total: Total revocations in the registry. stats: Counts by reason.

Parameterslimitsince_hours

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.