Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

HEARTH

by THORCollectiveversion 0.1.0i★ –iRuns on your computer
Registry nameio.github.THORCollective/hearth

Install

Overview

Description from the maker (original English)

Search community threat hunting hypotheses by keyword, threat actor, or the log sources you have.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Cybersecurity

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "hearth": {
      "command": "npx",
      "args": [
        "-y",
        "@thorcollective/hearth-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add hearth -- npx -y @thorcollective/hearth-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "hearth": {
      "command": "npx",
      "args": [
        "-y",
        "@thorcollective/hearth-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "hearth": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@thorcollective/hearth-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 10, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account THORCollective, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Cybersecurityi

  • More stars than 0% of the other 1012 servers in this category
  • Published to the registry more recently than 100% of the other 1012 servers in this category
  • Basic checks equal to or better than 100% of the other 1012 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is HEARTH safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry today.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Proofpoint MCP, adfraudit – Klickbetrug / Click Fraud, Keeper Security MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Proofpoint MCP

Proofpoint TAP threats, VAPs, clickers, and IOCs from your terminal, with a local threat store.

by servosityVery newUpdated today

Runs on your computer

Keeper Security MCP

Read-only Keeper MSP posture across every client, with history, a change feed and no path to a

by servosityVery newUpdated today

Runs on your computer

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

HEARTH MCP server

Ask your AI assistant what to hunt for. This MCP server gives Claude, Cursor, VS Code and other MCP clients read-only access to HEARTH, the community library of threat hunting hypotheses.

Questions you can ask:

  • "What can I hunt for Volt Typhoon with firewall and appliance logs?"
  • "Find hunts for macOS persistence."
  • "We only have Windows endpoint and identity logs. Which hunts can we run fully?"
  • "Show me H432."

Tools

ToolWhat it does
search_huntsRanked keyword search, with filters for category, tactic and data sources.
get_huntOne hunt in full: hypothesis, why it matters, notes, queries and references.
hunts_for_actorHunts for a threat actor by name, alias or ATT&CK group ID. Includes coverage and gaps.
hunts_for_datasourcesHunts your team can run with the log sources it has, and what each one is missing.

Every tool is read-only. Retired hunts are hidden unless you ask for them.

Install

You need Node.js 20 or later. Each snippet runs the published package with npx.

Claude Code
claude mcp add hearth -- npx -y @thorcollective/hearth-mcp
Claude Desktop

Add this to claude_desktop_config.json (Settings → Developer → Edit Config), then restart Claude Desktop:

{

"mcpServers": { "hearth": { "command": "npx", "args": ["-y", "@thorcollective/hearth-mcp"] } } }

Cursor

Add this to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json for every project:

{

"mcpServers": { "hearth": { "command": "npx", "args": ["-y", "@thorcollective/hearth-mcp"] } } }

VS Code

Add this to .vscode/mcp.json in your workspace:

{

"servers": { "hearth": { "type": "stdio", "command": "npx", "args": ["-y", "@thorcollective/hearth-mcp"] } } }

Settings
Environment variableEffect
HEARTH_OFFLINE=1Never touch the network; serve the bundled snapshot or the last download.
HEARTH_DATA_URLFetch data from a mirror instead of https://hearth.thorcollective.com/. Must be https (http only for localhost).
HEARTH_CACHE_DIRWhere downloaded data is kept. Defaults to your platform's cache folder (~/Library/Caches/hearth-mcp on macOS).

Set them in your client's config, for example "env": { "HEARTH_OFFLINE": "1" } next to "args".

Other clients

Any MCP client that supports stdio servers can run the same command: npx -y @thorcollective/hearth-mcp.

Privacy and security

  • No telemetry. The server sends nothing anywhere.
  • One small network check a day. At most once every 24 hours the server asks hearth.thorcollective.com whether the hunt data has changed. It uses conditional requests, so usually nothing is downloaded. It sends only those requests and a hearth-mcp/ user agent.
  • Works offline. If the site can't be reached, or sends data that fails validation, the server keeps using its last good copy, falling back to the snapshot bundled with each release.
  • Hunt text is treated as untrusted. Hunts are written by the community:
  • The server makes hidden and right-to-left characters visible, and removes hidden text.
  • It caps field lengths.
  • It labels every hunt text field as untrusted, so your assistant reads it as data, not instructions.
  • New hunts are also checked for prompt-injection text in CI before they merge.
  • Review detection queries before you run them, as you would any query from the internet.
  • Verify the package: releases are published from GitHub Actions with npm provenance. Run npm audit signatures after installing to check it.

Develop

From the repository root:

npm ci && npm ci --prefix mcp

npm run build --prefix mcp # bundle to mcp/dist and snapshot site data to mcp/data npm test # unit, golden and stdio protocol tests claude mcp add hearth-dev -- node "$PWD/mcp/dist/index.js"

The server reuses the site's own logic from src/lib, so search behaves the same way in both.

Golden queries

mcp/golden/ holds real analyst questions and the hunts a good answer must include. Adding one is the most useful way to improve search. See golden/README.md.

Releasing

Maintainers only:

  1. Bump version in mcp/package.json and mcp/server.json. A test fails if they differ.
  2. Merge to main.
  3. Push a tag named mcp-v , for example mcp-v0.1.0.

The publish workflow then:

  1. Waits for approval in the npm-publish environment.
  2. Publishes to npm with provenance, using trusted publishing (no npm token is stored).
  3. Waits for npm to serve the new version, which can take several minutes.
  4. Lists the release in the MCP Registry as io.github.THORCollective/hearth.

If the run fails after the npm publish, use Re-run failed jobs. A version already on npm is never published twice, so the re-run picks up at the registry step.

Ask PopNx