npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@thorcollective/hearth-mcp

v0.2.0

Published

Read-only MCP server for HEARTH, the community threat hunting hypothesis library

Readme

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."
  • "What Windows persistence techniques does HEARTH have no hunts for?"

Tools

| Tool | What it does | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | search_hunts | Ranked keyword search, with filters for category, tactic and data sources. | | get_hunt | One hunt in full: hypothesis, why it matters, notes, queries and references. | | hunts_for_actor | Hunts for a threat actor by name, alias or ATT&CK group ID. Includes coverage and gaps. | | hunts_for_datasources | Hunts your team can run with the log sources it has, and what each one is missing. | | coverage_gaps | ATT&CK techniques no hunt covers, for an actor, tactic or platform, most-used first. With your log sources, also techniques whose hunts you can't run. |

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 variable | Effect | | -------------------- | ------------------------------------------------------------------------------------------------------------------ | | HEARTH_OFFLINE=1 | Never touch the network; serve the bundled snapshot or the last download. | | HEARTH_DATA_URL | Fetch data from a mirror instead of https://hearth.thorcollective.com/. Must be https (http only for localhost). | | HEARTH_CACHE_DIR | Where 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".

Locked-down setup (enterprise)

For teams that review every change before it reaches analysts:

  • Pin the version. npx -y @thorcollective/hearth-mcp always fetches the latest release. Name an exact version instead, and nothing changes until you choose to upgrade.
  • Turn off the network. HEARTH_OFFLINE=1 stops the daily check, so the server only uses the hunt data that shipped with the version you pinned.
  • Or use your own mirror. Set HEARTH_DATA_URL to an internal copy of the site's data files, which you update on your own schedule.
  • Verify the package. After installing, run npm audit signatures to check that the package was built from this repository by GitHub Actions.

For example, in Claude Desktop:

{
  "mcpServers": {
    "hearth": {
      "command": "npx",
      "args": ["-y", "@thorcollective/[email protected]"],
      "env": { "HEARTH_OFFLINE": "1" }
    }
  }
}

Releases lists every version.

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/<version> 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, mcp/server.json and the pinned example under Locked-down setup in this README. A test fails if any of them differ.
  2. Merge to main.
  3. Push a tag named mcp-v<version>, 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.