com.threadlinqs/intelthreadlinqs-mcp

What we checked

Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.

• Injection surface

  fail25% of grade

  Tool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).

  tool "get_c2" description: names an outbound copy/exfil destination (BCC/exfil verb). tool "generate_c2_blocklist" description: names an outbound copy/exfil destination (BCC/exfil verb). tool "get_c2_dns_intel" description: names an outbound copy/exfil destination (BCC/exfil verb). tool "get_entity_aliases" description: bare 'IMPORTANT:' prose in a description (tag form is high-confidence; prose is warn). tool "get_d3fend_posture" description: bare 'IMPORTANT:' prose in a description (tag form is high-confidence; prose is warn).

• Supply chain

  pass25% of grade

  Package provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.

  repository linkage verified

• Credential hygiene

  pass15% of grade

  How the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.

  No hardcoded secrets, secret-shaped tool parameters, or leaked keys found. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

• Permission scope

  pass15% of grade

  Declared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.

  No shell-exec, unbounded/sensitive filesystem, or download-and-run primitives found in scanned source. PASS = no static red flag. Static scanning is blind to code fetched or executed at runtime.

• Version behavior

  pass10% of grade

  Diff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).

  vs prior 7.1.4 (major bump): new tool "get_started" touches a sensitive surface (email/exec/net/fs); new tool "search_vulnerabilities" appeared; new tool "search_threats" appeared; new tool "get_threat" appeared; new tool "get_recent_threats" appeared; new tool "get_detections" appeared; new tool "search_iocs" appeared; new tool "get_mitre_coverage" appeared; new tool "get_mitre_technique" appeared; new tool "get_threat_enrichment" touches a sensitive surface (email/exec/net/fs); new tool "get_malware_intelligence" appeared; new tool "get_tool_intelligence" touches a sensitive surface (email/exec/net/fs); new tool "get_campaign_intelligence" appeared; new tool "resolve_entity" appeared; new tool "get_actor" touches a sensitive surface (email/exec/net/fs); new tool "search_actors" appeared; new tool "get_actor_relationships" appeared; new tool "get_entity_aliases" appeared; new tool "list_campaigns" appeared; new tool "get_cve" appeared; new tool "get_cwe" touches a sensitive surface (email/exec/net/fs); new tool "get_platform_stats" appeared; new tool "get_similar_threats" appeared; new tool "get_landscape_briefing" touches a sensitive surface (email/exec/net/fs); new tool "get_daily_theme" appeared; new tool "get_threat_level" appeared; new tool "get_ioc_blast_radius" appeared; new tool "get_ioc_intelligence" appeared; new tool "get_ioc_dns" appeared; new tool "get_infrastructure_pivots" touches a sensitive surface (email/exec/net/fs); new tool "get_osint" appeared; new tool "search_xscan_indicators" appeared; new tool "get_c2" touches a sensitive surface (email/exec/net/fs); new tool "generate_c2_blocklist" touches a sensitive surface (email/exec/net/fs); new tool "get_correlations" touches a sensitive surface (email/exec/net/fs); new tool "predict_mitre_transitions" touches a sensitive surface (email/exec/net/fs); new tool "get_attack_flow" touches a sensitive surface (email/exec/net/fs); new tool "get_flow_similar_threats" appeared; new tool "get_flow_coverage" appeared; new tool "get_d3fend_posture" appeared; new tool "get_atlas_intelligence" appeared; new tool "get_threat_simulations" touches a sensitive surface (email/exec/net/fs); new tool "list_debriefs" appeared; new tool "get_debrief" appeared; new tool "export_stix" appeared; new tool "export_attack_navigator" appeared; new tool "list_threat_categories" appeared; new tool "search_detections" appeared; new tool "get_detection_detail" appeared; new tool "list_simulations" appeared; new tool "get_threat_transcripts" touches a sensitive surface (email/exec/net/fs); new tool "get_mitre_gap_analysis" appeared; new tool "get_enrichment_overview" touches a sensitive surface (email/exec/net/fs); new tool "get_roadmap" appeared; new tool "get_changelog" appeared; new tool "export_detection" appeared; new tool "get_latest_debrief" appeared; new tool "get_threat_bundle" appeared; new tool "get_threat_hunting_bundle" appeared; new tool "get_daily_intel_bundle" appeared; new tool "bulk_get_threats" touches a sensitive surface (email/exec/net/fs); new tool "bulk_get_cves" touches a sensitive surface (email/exec/net/fs); new tool "get_actor_intelligence" appeared; new tool "get_cve_intelligence" appeared; new tool "health" touches a sensitive surface (email/exec/net/fs); new tool "hunt" touches a sensitive surface (email/exec/net/fs); new tool "hunt_schema" appeared; new tool "get_attribution_evidence" appeared; new tool "get_attribution_coverage" appeared; new tool "explain_correlation" appeared; new tool "get_correlation_path" appeared; new tool "get_entity_profile" appeared; new tool "get_pivotal_entities" appeared; new tool "get_graph_campaigns" touches a sensitive surface (email/exec/net/fs); new tool "get_technique_rules" appeared; new tool "get_engine_status" appeared; new tool "get_osint_trends" touches a sensitive surface (email/exec/net/fs); new tool "get_community_campaigns" appeared; new tool "get_c2_dns_intel" appeared; new tool "get_correlation_subgraph" appeared; new tool "search_corpus_semantic" appeared. Low-severity drift (informational; consistent with the version bump).

• Transport config

  unscannable10% of grade

  Remote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.

  local stdio server: no remote transport or auth surface, and no phone-home/telemetry signal found in source. Absence of transport findings is NOT a safety guarantee — phone-home hosts can be constructed at runtime and defeat static analysis.