Reviews
No review yet. Used threatcrush? Be the first to help others choose.What it does
threatcrush is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)Hosted endpoint
https://threatcrush.com/api/mcpstreamable-http
In Claude Code: claude mcp add --transport http threatcrush https://threatcrush.com/api/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"threatcrush": {
"url": "https://threatcrush.com/api/mcp"
}
}
}Reliability
Re-tested about every 3 days · last check 1d agoObserved endpoint availability: the share of our conclusive checks that got an answer. A request for a key or sign-in counts as an answer (the server is up, its access is protected). Timeouts, unreachable endpoints, server errors and invalid MCP replies count as failures; rate-limited checks and checks during our own incidents are not counted. This is what we observed at each check, not continuous uptime: an outage between two checks may go unseen. The 90-day figure will appear once 90 days of checks exist (checks since 11 Nov 2026). How we measure
Tool changes
Tool tracking since 13 Nov 2026 · test history since 11 Nov 2026No tool added or removed since tracking started. 20 tools in the latest list.
Changes are confirmed by comparing complete tool lists only, read about every 3 days, and dated by the day we saw them. A renamed tool appears as one removal and one addition.
Live check
Electra Index connected to the hosted endpoint 1d agoONLINE threatcrush answered an MCP connection on 20 Nov 2026 and introduced itself as threatcrush 1.0.1 (MCP protocol 2025-06-18).
20 tools offered to AI assistants
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 isreputation_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, rreputation_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 persolist_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,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.
Show 8 more
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 bywebhooks_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 ywebhooks_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.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Re-tested about every 3 days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://threatcrush.com/api/mcp | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Website | https://threatcrush.com | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Version | 1.0.0 | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 5d ago |
Change history
- NEW11 Nov 2026first seen in the index
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is threatcrush still online?
Free alerts · no account▲ 0Do you run threatcrush? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about threatcrush
How do I connect threatcrush?
Use the hosted endpoint https://threatcrush.com/api/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does threatcrush offer?
When Electra Index connected on 20 Nov 2026, it listed 20 tools: av_hash_lookup, reputation_lookup, reputation_bulk, redeem_credit_code, list_invites, create_invite, findings_list, findings_get and more. The full list is in "Live check" above.
Is threatcrush online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.