io.github.tiluckdave/hound
NPM · HOUND-MCP · SCANNED SEP 20
The dependency bloodhound for AI coding agents. Zero API keys, zero config.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to tiluckdave/hound-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 78 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1017 tokens (~84/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.tiluckdave/hound MCP server?
io.github.tiluckdave/hound runs locally as an npm package, launched with npx -y hound-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · hound-mcp
claude mcp add tiluckdave-hound -- npx -y hound-mcp
{
"mcpServers": {
"tiluckdave-hound": {
"command": "npx",
"args": [
"-y",
"hound-mcp"
]
}
}
} {
"servers": {
"tiluckdave-hound": {
"command": "npx",
"args": [
"-y",
"hound-mcp"
]
}
}
} codex mcp add tiluckdave-hound -- npx -y hound-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tiluckdave-hound": {
"type": "local",
"command": [
"npx",
"-y",
"hound-mcp"
],
"enabled": true
}
}
} openclaw mcp add tiluckdave-hound --command npx --arg -y --arg hound-mcp
mcp_servers:
tiluckdave-hound:
command: "npx"
args: ["-y", "hound-mcp"] {
"McpServers": {
"tiluckdave-hound": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"hound-mcp"
]
}
}
} assistant mcp add tiluckdave-hound -t stdio -c npx -a -y hound-mcp
{
"mcpServers": {
"tiluckdave-hound": {
"command": "npx",
"args": [
"-y",
"hound-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
- Security disclosure: unverified → pass ▲ functional
- 12 Sept 26 0
- Security disclosure: pass → unverified ▼ functional
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/hound-mcp@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | tiluckdave/hound-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/tiluckdave/hound-mcp/.github/workflows/release.yml@refs/tags/v0.2.1 |
| Rekor log index | 1084354262 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7747fc7fac42e1f3c1c4f8bde6276e99171ec0c2c48db7c62e8525ee12b6fc76792b2a7e1313249e7323ef89057c4a625e07bd9eb8f53fdd4e70bbb67 |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
hound_advisories ~85
Get full details for a security advisory by ID (GHSA, CVE, or OSV ID). Returns title, severity, affected versions, fix versions, and references.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Advisory ID — e.g. GHSA-rv95-896h-c2vc, CVE-2024-29041, or any OSV ID |
No output schema declared.
No examples provided.
hound_audit ~103
Scan a project's lockfile for dependency risks. Parses package-lock.json, yarn.lock, pnpm-lock.yaml, requirements.txt, Cargo.lock, or go.sum and batch-queries OSV for vulnerabilities across all dependencies.
| Name | Type | Req | Description |
|---|---|---|---|
| lockfile_content | string | yes | Full text content of the lockfile |
| lockfile_name | string | yes | Filename to determine format: package-lock.json, yarn.lock, pnpm-lock.yaml, requirements.txt, Cargo.lock, go.sum |
No output schema declared.
No examples provided.
hound_compare ~74
Side-by-side comparison of two packages: vulnerabilities, OpenSSF Scorecard, GitHub stars, release recency, and license. Returns a recommendation.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Package ecosystem (default: npm) |
| package_a | string | yes | First package name |
| package_b | string | yes | Second package name |
No output schema declared.
No examples provided.
hound_inspect ~72
Get a comprehensive profile of a package version: licenses, vulnerabilities, OpenSSF scorecard, GitHub stats, and dependency count — all in one call.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Package ecosystem (default: npm) |
| name | string | yes | Package name |
| version | string | yes | Package version |
No output schema declared.
No examples provided.
hound_license_check ~136
Scan a lockfile for license compliance. Resolves licenses for every dependency and flags packages that violate the chosen policy (permissive, copyleft, or none).
| Name | Type | Req | Description |
|---|---|---|---|
| lockfile_content | string | yes | Full text content of the lockfile |
| lockfile_name | string | yes | Filename: package-lock.json, yarn.lock, pnpm-lock.yaml, requirements.txt, Cargo.lock, go.sum |
| policy | string | – | License policy to enforce: 'permissive' (MIT/Apache/BSD only), 'copyleft' (allows GPL but not AGPL), 'none' (report only, no violations) |
No output schema declared.
No examples provided.
hound_popular ~79
Scan a list of popular (or user-specified) packages for known vulnerabilities. Quickly surface which widely-used packages in an ecosystem have open security issues.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Package ecosystem (default: npm) |
| packages | array | – | Specific package names to check. If omitted, uses a curated list of popular packages for the ecosystem. |
No output schema declared.
No examples provided.
hound_preinstall ~75
Safety check before installing a package. Checks known vulnerabilities, typosquatting risk, abandonment, and license concerns. Returns a go/no-go verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Package ecosystem (default: npm) |
| name | string | yes | Package name |
| version | string | – | Package version (defaults to latest) |
No output schema declared.
No examples provided.
hound_score ~82
Compute a 0-100 Hound Score for a package version combining vulnerability severity, OpenSSF Scorecard, release recency, and license risk. Returns a letter grade (A-F) with a breakdown.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Package ecosystem (default: npm) |
| name | string | yes | Package name |
| version | string | yes | Package version |
No output schema declared.
No examples provided.
hound_tree ~85
Show the full resolved dependency tree for a package version, including all transitive dependencies with their depth and relation type.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Package ecosystem (default: npm) |
| maxDepth | integer | – | Maximum depth to display (default: 3, max: 10) |
| name | string | yes | Package name |
| version | string | yes | Package version |
No output schema declared.
No examples provided.
hound_typosquat ~64
Check if a package name looks like a typosquat of a popular package. Generates likely typo variants and checks which ones exist in the registry.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Package ecosystem (default: npm) |
| name | string | yes | Package name to check |
No output schema declared.
No examples provided.
hound_upgrade ~83
Find the minimum version upgrade that resolves all known vulnerabilities for a package. Checks every published version and returns the nearest safe one.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Package ecosystem (default: npm) |
| name | string | yes | Package name (e.g. express, lodash) |
| version | string | yes | Current vulnerable version (e.g. 4.17.20) |
No output schema declared.
No examples provided.
hound_vulns ~79
List all known vulnerabilities for a specific package version, grouped by severity with fix versions and advisory links.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Package ecosystem (default: npm) |
| name | string | yes | Package name (e.g. express, lodash) |
| version | string | yes | Package version (e.g. 4.18.2) |
No output schema declared.
No examples provided.
What is the io.github.tiluckdave/hound MCP server?
io.github.tiluckdave/hound is an MCP server listed in the public MCP registry as io.github.tiluckdave/hound. The dependency bloodhound for AI coding agents. Zero API keys, zero config. This page covers its npm package (hound-mcp).
Is the io.github.tiluckdave/hound MCP server safe to use?
io.github.tiluckdave/hound scores 96 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.tiluckdave/hound MCP server expose?
io.github.tiluckdave/hound exposes 12 tools: hound_vulns, hound_inspect, hound_tree, hound_typosquat, hound_advisories, and 7 more. Their descriptions and schemas cost roughly 1,017 tokens of context every time the server is loaded.
Is the io.github.tiluckdave/hound MCP server still maintained?
io.github.tiluckdave/hound is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.tiluckdave/hound MCP server under?
io.github.tiluckdave/hound declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.