
Hound
io.github.tiluckdave由 GitHub 账号 tiluckdave 发布v0.2.1更新于 Oct 24, 2026
The dependency bloodhound for AI coding agents. Zero API keys, zero config.
概览
Hound 是一个本地 MCP 服务器,让 AI 编程助手在 7 个生态中检查依赖包的漏洞、许可证、仿冒包名和升级路径。
- 可以做什么
- 审计锁文件中的漏洞,并按策略检查许可证合规,也可扫描热门包的已知问题。获取包概况、0-100 评分与字母等级,以及安装前的 GO/CAUTION/NO-GO 结论。并排比较两个包,并找出能修复已知漏洞的最低安全升级版本。查看含传递依赖的完整解析依赖树,并检测包名的仿冒变体。按 GHSA、CVE 或 OSV 编号查询完整公告详情。使用内置提示执行完整安全审计、包评估和发布前检查。
- 适用场景
- 适合在助手推荐或安装包时做安全检查,在合并锁文件变更前把关,审计接手的代码库,或在商业项目中执行许可证合规要求。
- 运行要求
- 通过 stdio 在本地运行,通常用 npx 启动 npm 包 hound-mcp,因此需要 Node.js 和网络访问。未声明 API 密钥、账号或配置;它会调用免费的公共 deps.dev 和 OSV 接口。
安装
在 SourceWeft 中
- 打开 控制台中的 Hound,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
Hound MCP
The dependency bloodhound for AI coding agents.
[npm version] [npm downloads] [CI] [License: MIT]
Why Hound?
AI coding agents recommend and install packages without knowing if they're safe — and most security tools require accounts, API keys, or paid plans to tell you. Hound fixes that: it scans for vulnerabilities, checks licenses, audits dependency trees, and detects typosquatting across 7 ecosystems — zero config, zero API keys, zero cost.
Hound is the only security tool built specifically for AI coding agents — works across npm, PyPI, Go, Cargo, Maven, NuGet, and RubyGems, and plugs into Claude Code, Cursor, VS Code, and any MCP client out of the box.
It uses two fully free, unauthenticated public APIs: deps.dev (Google Open Source Insights) and OSV (Google Open Source Vulnerabilities).
Quickstart
Claude Code
Claude Desktop / Cursor / Windsurf
Add to your MCP config file:
VS Code (Copilot)
Config file locations
Tools
12 tools → Full reference with example outputs
Supported ecosystems: npm · pypi · go · maven · cargo · nuget · rubygems
Built-in Prompts
3 prompts you can invoke directly from your AI client. → Full prompt reference
Use Cases
→ See full examples with real lockfiles and expected output
- Before merging a PR — scan the lockfile diff to catch newly introduced vulnerabilities before they land in main
- Auditing an inherited codebase — run
hound_auditon an existing lockfile to get a full report in seconds - Checking a package before adding it — use
hound_preinstallto get a GO / CAUTION / NO-GO verdict - License compliance — run
hound_license_checkto ensure no GPL or AGPL packages sneak into a commercial project - CI security gate — ask your AI agent to run a security audit as part of every release check
Local Development
Roadmap
- Docker support — run Hound as a container for CI/CD pipelines
-
bun.lockbparser — Bun lockfile support -
gradle.lockfileparser — Gradle (Java/Android) ecosystem support -
hound_difftool — compare two lockfile snapshots to surface newly introduced risks - GitHub Action — run
hound_auditas a PR check without an AI agent
Contributing
Contributions are welcome. Read CONTRIBUTING.md to get started.
The one rule: Hound must stay zero-config and free forever. Don't add features that require API keys or accounts.
Good first issues are labeled and ready.
Community
💬 Questions or ideas? Open a Discussion
License
MIT © 2026 Tilak Dave
来源:README.md,提交 82fd52a
工具
0版本历史
1- v0.2.1最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分