Ext Ops Panel
Open dashboard
Comparison

Huntress MCP vs SpanHound

Huntress MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). SpanHound is an MCP server published by abhishekash. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceHuntress MCPSpanHound
Official MCP Registry Listed
Version: 0.1.11
Forks (GitHub): 13
Stars (GitHub): 63
Not marked · First seen
Listed
Version: 0.6.1
Downloads/month (PyPI): 0
Downloads/week (PyPI): 83
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Huntress MCP vs SpanHound
FactHuntress MCPSpanHound
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)63 (better)1 (worse)
Forks (GitHub) (differs)13 (better)0 (worse)
Last release (differs)2026-10-27 (better)2026-10-15 (worse)
Where it runs (differs)On your machine (https://github.com/Servosity/msp-skills/releases/download/huntress-v0.1.11/huntress-mcp.mcpb)On your machine (spanhound)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)8, secrets among them: 4Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/servosity/msp-skillsgithub.com/abhishekash/spanhound
Changes in the last 7 days (differs)100
First seen (differs)2026-10-112026-10-13

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Huntress MCP

In its own words, on Official MCP Registry:

Every Huntress endpoint, plus a local SQLite mirror that delivers fleet-wide incident, coverage

SpanHound

In its own words, on Official MCP Registry:

Capture local agent traces and inspect failures, approvals, and run comparisons.

How to run each

Huntress MCP As a Claude Code plugin

Claude Code
/plugin marketplace add servosity/msp-skills
/plugin install huntress@msp-skills

Requires: HUNTRESS_API_KEY (secret), HUNTRESS_API_SECRET (secret), HUNTRESS_MCP_HTTP_TOKEN (secret), PRINTING_PRESS_CLIENT_PROFILE (secret)

SpanHound As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio spanhound -- uvx spanhound

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of SpanHound publish no settings it asks for, so we do not compare settings.

What it can do: Huntress MCP · What it can do: SpanHound · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built