threatcrush

安装

选择你使用的 AI 应用，然后复制设置。

通过 2/3 项检查 · 你的提问会经过开发者的服务器（threatcrush.com）

claude mcp add --transport http --scope user threatcrush https://threatcrush.com/api/mcp

{
  "mcpServers": {
    "threatcrush": {
      "url": "https://threatcrush.com/api/mcp"
    }
  }
}

{
  "servers": {
    "threatcrush": {
      "type": "http",
      "url": "https://threatcrush.com/api/mcp"
    }
  }
}

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档，检查于 2026年11月10日。

通过互联网连接，适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月11日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• av_hash_lookup

  CrushAV file reputation, no key needed: look up up to 100 SHA-256 file hashes. For each hash something is known about, returns `knownMalicious` (the source listing it as malware), `malwareName`, `trust` (0-100: how sure CIRCL hashlookup is that this is a published, known-good fil

• reputation_lookup

  Look up an IP address or a domain against the ThreatCrush community threat database (what every linked ThreatCrush daemon blocked). Returns `listed` (the corroboration bar: independent reporters agree), a 0-100 `score`, severity, reports, reporters, rules and country; a domain is

• reputation_bulk

  Look up many IPs or domains at once (up to 100 with a free key, 1,000 with Reputation Pro). Results come back in request order; each counts against the daily allowance.

• redeem_credit_code

  Redeem a ThreatCrush credit code (CR-XXXX-XXXX-XXXX-XXXX) into the signed-in account's credit balance (1 credit = $1.00). Needs the account's session token (`threatcrush login`), not a tc_agent_ key: agent keys belong to a team, not a person.

• list_invites

  The signed-in account's invites: how many are left of 3, who joined, and whether the bonus credits were paid. Session token only.

• create_invite

  Create one invite link (each account has 3, single use, 30 days). When a new account joins on it and confirms its email, both get bonus credits. Session token only.

• findings_list

  Your org's tracked findings from threatcrush scan, pentest and ai-scan (deduped across runs, with a triage status). Default: open + acknowledged. Session token or tc_agent_ key.

• findings_get

  One tracked finding with its details (code snippet, remediation, evidence), property and history.

• findings_triage

  Set the status and/or note of up to 500 findings: acknowledged, fixed, false_positive, ignored or open. fixed is reopened by a later run that still sees it; false_positive and ignored never are. Needs write.

• incidents_list

  Your org's incidents: what `threatcrush investigate --raise`, the daemon (critical detections) and people raised to humans. Filter by host and explicit since timestamp; only teams you can see. Session token or tc_agent_ key.

• incidents_get

  One incident: linked forensic evidence, recent events from the same observed source IP on its server, block history for that IP, saved AI assessment, multi-person assignees, fix and test progress, work history, recorded resolution/operator, findings, timeline, notes and who was p

• incidents_update

  Update fix work performed by your assigned agent or human: set multiple assignees, fix status, PR URL, test status and evidence, verification or blocker, and/or add a note. ThreatCrush catalogs the incident and does not execute remediation. Closing requires status fixed with pass

• incidents_raise

  Raise an incident report (report_version 1: title, severity, source, dedupe_key, summary, verdict, findings, timeline, recommendations, optional team_id/server_id). The same dedupe_key while open updates it; a new incident pages the team by SMS and email once. Reports that contai

• webhooks_list

  Your org's webhook endpoints (signed Standard Webhooks deliveries, retried for about three days) and the events ThreatCrush emits: detection.created, findings.raised, reputation.changed. Endpoints behind a Webhook alert destination follow your alert rules; the others get every ev

• webhooks_create

  Add a webhook endpoint (public https URL). Returns the endpoint and its signing secret (whsec_…), shown once.

• webhooks_update

  Change a webhook endpoint's url, events, description, or switch it on/off (on again clears its failure count).

• webhooks_delete

  Remove a webhook endpoint and its delivery log.

• webhooks_test

  Send a signed webhook.test event to one endpoint now and say how it went.

• webhooks_rotate_secret

  Replace an endpoint's signing secret; the old one stops working at once. Returns the new secret.

• webhooks_deliveries

  Recent webhook deliveries (status, attempts, last HTTP status/error, payload), for one endpoint or all.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月12日

• ! 注意

  作者与仓库一致

  注册中心没有列出源代码仓库，因此无法将发布者（profullstack.com）与代码对应起来

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 541 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 20 个工具描述，未发现针对 AI 的隐藏指令

用户评价

还没有评价

用 Google 登录后写评价

与“网络安全”中的其他服务器比较i

• 星标数多于此分类中其他 1041 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 1041 个服务器的 97% 更新
• 基础检查结果等于或优于此分类中其他 1041 个服务器的 44%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

同类别的其他选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Robin: AI-Powered Dark Web OSINT

Dark web OSINT over Tor: search onion engines, scrape pages, report with your own model.

作者：apurvsinghgautam·正在增长·★ 7961·40天前更新

在你的电脑上运行

安装

HOL Guard

Local-first AI agent security evidence and approval workflows through HOL Guard's stdio MCP server.

作者：hashgraph-online·广泛使用·↓ 7083/周·★ 1088·7天前更新

在你的电脑上运行

安装

SonarQube MCP Server

Analyze code quality and security with SonarQube Server or Cloud directly in AI assistants.

作者：SonarSource·正在增长·★ 685·昨天更新

在你的电脑上运行

安装

作者的 README

仓库中没有找到 README