SolidInvoice
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
CVEs, affected versions and fix versions for your dependencies, from an affected-version ledger.
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 20/100 | 热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-11-10 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 4/4 项(仅展示,不用于排序)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 VulnTracker。按照 https://mcp.popnx.com/i/vulntracker-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 4/4 项检查 · 你的提问会经过开发者的服务器(api.vulntracker.io) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 5 分钟
需要 VulnTracker 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
VulnTrackerhttps://api.vulntracker.io/mcp在 Request headers 下添加这个名称和值
AuthorizationBearer <在这里粘贴你的密钥>只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsVulnTracker
用 VulnTracker 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 VulnTracker,或回答中出现 VulnTracker 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 VulnTracker
VulnTracker 连接时需要你自己的密钥,但 OpenAI 帮助页面只说明了 OAuth 登录,没有我们能核实的填密钥方式
A · 使用能连接 VulnTracker 的应用
B · 会计、财务与税务 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code · 约 5 分钟
需要 VulnTracker 的密钥(在开发者网站创建)
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user vulntracker https://api.vulntracker.io/mcp --header 'Authorization: Bearer {api_key}'按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
应能看到 VulnTracker 在列表中并显示已连接
用 VulnTracker 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 VulnTracker,或回答中出现 VulnTracker 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 5 分钟
需要 VulnTracker 的密钥(在开发者网站创建)
在 VulnTracker 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 VulnTracker 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 VulnTracker,或回答中出现 VulnTracker 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 5 分钟
需要 VulnTracker 的密钥(在开发者网站创建)
在 VulnTracker 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 VulnTracker 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 VulnTracker,或回答中出现 VulnTracker 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --transport http --scope user vulntracker https://api.vulntracker.io/mcp --header 'Authorization: Bearer {api_key}'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"vulntracker": {
"url": "https://api.vulntracker.io/mcp",
"headers": {
"Authorization": "Bearer {api_key}"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"vulntracker": {
"type": "http",
"url": "https://api.vulntracker.io/mcp",
"headers": {
"Authorization": "Bearer {api_key}"
}
}
}
}说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
工具名称和描述与服务器在 2026年11月16日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
add_to_boardAdd CVEs to the team's board (the API key's team) as cards, or update their status if a card already exists. Use after a scan when the user asks to put the findings on the board; write which dependency and version each CVE came from into notes. Up to 50 CVE ids per call, counted
check_dependenciesCheck many product@version pairs in one call. Give the dependencies you read from the repository's manifests (go.mod, package.json / lock files, requirements.txt, pom.xml, Gemfile.lock, Cargo.lock, Dockerfile base images). For each one you get whether VulnTracker matched a produc
check_versionThe core question: which CVEs affect this exact version of a product, and which version fixes each? Returns (a) CVEs whose claims name this version, with evidence, confidence and fix versions, and (b) range_affected_cves: CVEs whose source gave a version range that contains this
create_jira_issueOpen a Jira issue for a CVE on the team's board (the card is created first if missing) using the team's Jira integration. Returns the issue key and URL; if the card already has an issue, returns that one with existing=true. Only when the user asks.
list_board_cardsThe team's CVE board: the CVEs that reached this team (by tracking notification or added by hand), each with its triage status (new, acknowledged, in_progress, resolved, dismissed), resolution status, notes, severity and the vendor/product it was recorded against. Use it to answe
list_trackingsThe vendors, products, versions, CVEs, keywords and CPEs this account's team is watching in VulnTracker.
lookup_cveFull record for one CVE: description, CVSS, EPSS, KEV/exploitation and SSVC, affected products with version ranges and fixes from the ledger, vendor advisories (CSAF), public exploit repositories, and VulnTracker's remediation guide when one is published.
product_cvesAll CVEs recorded against a product in the affected-version ledger, newest first, with the version ranges each one names. entry_kind 'affected' = the product itself is vulnerable; 'runs_on_platform' = another product is vulnerable when running on it.
product_versionsList the versions VulnTracker knows for a product, with per-version CVE and fix counts. Use to find the exact version string before calling check_version.
remediation_guideVulnTracker's published remediation guide for a CVE: summary, steps, workarounds, caveats, kind (fix / workaround / guidance) and the fix versions it rests on. Returns has_guide=false when none is published.
search_cvesSearch the CVE list with filters. Results are newest first, up to 100 per call; when has_more is true pass next_cursor back as 'cursor' for the following page (at most 10 pages per filter set, so narrow the filters instead of walking the whole database). 'tracked_only' limits to
search_productsFind VulnTracker products (software, firmware, libraries) by name. Returns slugs to use with check_version, product_versions and product_cves. Searches display names and known aliases (package names, CPE tokens).
trackStart watching something in VulnTracker for the API key's team: a product (default; slug or id from search_products / check_dependencies matched_slug), a vendor, a single CVE, or a keyword. New CVEs matching the tracking reach the team's board and its notification channels. Plan
untrackRemove a tracking from the API key's team: give the same type and target used with track (or shown by list_trackings). Board cards stay.
update_board_cardChange one board card: triage status (new, acknowledged, in_progress, resolved, dismissed), resolution (patched, mitigated, workaround, accepted_risk, false_positive), notes and resolution notes. Creates the card if the CVE is not on the board yet. Use when the user says a CVE is
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过域名 vulntracker.io 验证(注册中心会核实域名所有权)
代码最后更新于9天前
不适用:由 vulntracker.io 的所有者自己运行的云端服务器,你不会运行仓库里的代码
在 492 毫秒内响应(HTTP 200)
无需登录
已读取 15 个工具描述,未发现针对 AI 的隐藏指令
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/vulntracker-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 4 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于9天前,最新版本(2.5.0)于9天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:SolidInvoice, Signal8, Journalit, Beancount.io, Tapetide - Indian Stock Market MCP
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
SEC filings, dilution, insider & institutional ownership, and political-trade data for AI agents.
Trading journal in Obsidian. Ask Claude or ChatGPT about your trades; edits are previewed first.
Query, edit, and reconcile a hosted Beancount ledger: BQL, reports, files, and bank imports.
48 tools for ~8,000 NSE & BSE stocks: quotes, screener, financials, filings, FII/DII, options
| 本项 VulnTracker | SolidInvoice | Signal8 | Journalit | Beancount.io | Tapetide - Indian Stock Market MCP | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 是 | 否 | 是 | 否 | 否 | 是 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 4/4 | 4/6 | 5/5 | 4/4 | 4/4 | 5/5 |
| 许可证 | MIT | MIT | MIT | NOASSERTION | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Hosted MCP server for coding agents: ask which of your dependencies are vulnerable, which CVEs affect an exact version, and which version fixes each. Backed by VulnTracker's affected-version ledger, not by a model's memory.
This repository holds the connection instructions and the registry manifest. The server itself runs at https://api.vulntracker.io/mcp; there is nothing to install or run locally.
https://api.vulntracker.io/mcp (Streamable HTTP)Authorization: Bearer , keys start with vt_Create a key at Settings → API keys on vulntracker.io. It is shown once.
Claude Code
claude mcp add --transport http vulntracker https://api.vulntracker.io/mcp \
--header "Authorization: Bearer vt_…"
Cursor (.cursor/mcp.json) and Claude Desktop (claude_desktop_config.json)
{
"mcpServers": { "vulntracker": { "url": "https://api.vulntracker.io/mcp", "headers": { "Authorization": "Bearer vt_…" } } } }
Codex (~/.codex/config.toml)
[mcp_servers.vulntracker]
url = "https://api.vulntracker.io/mcp" http_headers = { Authorization = "Bearer vt_…" }
With the server connected, say:
check this repo for vulnerabilities with VulnTracker
The agent reads your lock files, calls check_dependencies with the resolved versions, verifies the hits with lookup_cve and reports a table with fix versions. Then:
add the exploited ones to the board and track these dependencies
(Pro / Business). In Claude Code the same procedure is available as the /mcp__vulntracker__scan_dependencies prompt.
| tool | question it answers |
|---|---|
check_dependencies | Which of these name@version pairs are vulnerable? Up to 50 per call |
search_products | What is the VulnTracker slug for openssl / log4j / fortios? |
product_versions | Which versions of this product are known, with CVE and fix counts? |
check_version | Which CVEs affect version X of this product, and which version fixes each? |
product_cves | All CVEs recorded against a product, with the version ranges they name |
lookup_cve | Full record: scores, EPSS, KEV / SSVC, affected products and fixes, vendor advisories, exploit repos, remediation guide |
search_cves | Filtered list: vendor, product, severity, exploited, remediation kind, dates |
remediation_guide | VulnTracker's published fix / workaround guide for a CVE |
list_board_cards | Your team's CVE board with triage status and notes |
list_trackings | What your team is watching |
add_to_board | *write, Pro+* — put CVEs on the team board with a status and a note |
update_board_card | *write, Pro+* — change a card's status, resolution or notes |
track / untrack | *write, Pro+* — start or stop watching a product, vendor, CVE or keyword |
Write tools act on the team the API key belongs to and name it in the answer. Agents are instructed to write only when asked.
fix_stated_by_source=false: the fix version was derived from a range bound, not stated by the vendor.match_confidence: token and exact are reliable; fallback items carry needs_confirmation=true and are left out of the vulnerable count until confirmed against matched_vendor.all_versions_cves: the source named no version at all. shadowed_range_cves: an open-start < X entry next to an A..X entry with the same end; probably the same branch restated.version_scheme="git": the version is a commit id and cannot be compared with a release number.| HTTP 401 | malformed, unknown or revoked key |
tool error authentication required | tool call without a key; tool listing works without one |
tool error plan_required | a write tool on the free plan |
tool error daily quota exceeded | wait for 00:00 UTC or upgrade; a new key does not reset it |