updated 2026-11-10 04:07 UTC

Hound MCP

Repository

The dependency bloodhound for AI coding agents. Free, no API keys.

MCP Servers TypeScript Listed MIT

Is Hound MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.5 / 10
Provenance Attested
Signed commits 60%
Last push 13d ago
Advisories None known
Compare Hound MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Hound MCP scores 71.5/100 (Grade B), ranked #338 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.5/10; 60% of recent commits are signed; no published advisory affects its latest release (hound-mcp); last pushed 2026-10-28. Every point is earned from checkable signals — never paid placement. How scoring works →

How Hound MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Hound MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/tiluckdave/hound-mcp, MIT, last pushed 2026-10-28. 60% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.5/10 (scanned Nov 4, 2026). The checks that decide who can get a change released:

    • Code Review5
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 5
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 5
    Contributors 6
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 0
    Packaging 10
    Pinned-Dependencies 0
    SAST 9
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked and attested

    • npm hound-mcp Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: hound-mcp 0.3.0. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-30 OSSF Scorecard: 6.3/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Hound MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Hound MCP compares in MCP Servers

  1. #198 Mcpcap 71.9 +0.4
  2. #199 Fr0ster MCP Abap Adt 71.6 +0.1
  3. #200 Hound MCP 71.5 this agent
  4. #201 Upstash MCP Server 71.5 ±0
  5. #202 Cronometer MCP 71.4 −0.1

Bars show each HVTrust score; the tick marks Hound MCP’s 71.5.

Where the 71.5 comes from

HVTrust dimensions vs the MCP Servers average

71.5 / 100 · 100.0% confidence

Hound MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.4 / 25
6.6 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
13.2 / 17
0.9 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
11.1 / 20
1.1 below avg 12.2
AdoptionLog-scaled stars · package downloads
5.8 / 20
1.8 below avg 7.6

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-10-29
Rank Moved
Rank dropped 12 spots (#306 → #318)
2026-10-27
Rank Moved
Rank rose 24 spots (#328 → #304)
2026-10-18
Rank Moved
Rank dropped 11 spots (#325 → #336)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.5/10. Tighten the weakest checks to improve public safety evidence.
Compare with another agent
View MCP Servers Report missing data
36.9
Activity sub-score · out of 100
#200
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 13 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
17
Forks
20
Last Push
2026-10-28
13 days ago
Commits (4 wk)
0
Downloads (7d)
112
npm
HN mentions (30d)
—
Open Issues
7
Rank Change
▼3
was #335

Analysis

Activity Inputs

36.9 / 100
StarsRepository reach
7.5 / 30
FreshnessLast push recency
23.2 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
6.1 / 20

Common questions about Hound MCP

Hound MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Hound MCP publish package provenance?
Yes. Hound MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Hound MCP have an OpenSSF Scorecard?
Hound MCP has an OpenSSF Scorecard score of 5.5/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Hound MCP actively maintained?
Maintained. Last push was 13 days ago.
What license does Hound MCP use?
Hound MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Hound MCP's commits signed?
60% of the last 100 commits to Hound MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Hound MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Hound MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-24
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Hound MCP?

For maintainers

HVTrust scores Hound MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 18HVTrust 3Grade 2Score 1Scorecard 1Delisted 1Listed 1Provenance 1MCP 1
2026-10-29
Rank Moved
Rank dropped 12 spots (#306 → #318)
2026-10-27
Rank Moved
Rank rose 24 spots (#328 → #304)
2026-10-18
Rank Moved
Rank dropped 11 spots (#325 → #336)
2026-10-12
Rank Moved
Rank dropped 30 spots (#290 → #320)
2026-09-24
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-24
Rank Moved
Rank rose 44 spots (#297 → #253)
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 654 spots (#951 → #297)
2026-09-23
HVTrust Changed
HVTrust up 45.7pts (25.8 → 71.5)
2026-09-22
Newly Listed
First tracked at rank #951
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-11
Rank Moved
Rank dropped 11 spots (#248 → #259)
2026-09-07
Rank Moved
Rank dropped 22 spots (#221 → #243)
2026-09-05
Rank Moved
Rank dropped 54 spots (#165 → #219)
2026-09-03
Grade Changed
Trust grade D → B
2026-09-03
Rank Moved
Rank rose 560 spots (#723 → #163)
2026-09-03
HVTrust Changed
HVTrust up 24.2pts (49.5 → 73.7)
2026-09-01
Rank Moved
Rank dropped 31 spots (#691 → #722)
2026-08-31
Rank Moved
Rank dropped 34 spots (#657 → #691)
2026-08-30
Scorecard Added
OSSF Scorecard: 6.3/10
2026-08-30
Rank Moved
Rank rose 179 spots (#836 → #657)
2026-08-30
HVTrust Changed
HVTrust up 8.8pts (39.6 → 48.4)
2026-08-29
Rank Moved
Rank dropped 45 spots (#791 → #836)
2026-08-28
Rank Moved
Rank dropped 49 spots (#742 → #791)
2026-08-28
Activity Score Changed
Activity score down 8pts (43 → 35)
2026-08-27
Rank Moved
Rank dropped 22 spots (#720 → #742)
2026-08-26
Rank Moved
Rank dropped 99 spots (#621 → #720)
2026-08-16
Rank Moved
Rank dropped 11 spots (#607 → #618)
GitHub → npm: hound-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 71.5 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/hound-mcp.svg)](https://hvtracker.net/agents/hound-mcp)
HTML:
<a href="https://hvtracker.net/agents/hound-mcp"><img src="https://hvtracker.net/badge/hound-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON