triageshield
Verify a vuln report's file/line/function claims against a real GitHub repo.
我該用這個嗎
品質與安全性
根據工具定義與協定合規性的自動化分析。
上下文成本
這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高，可用於其他工作的注意力就越少。
安裝
一鍵安裝
將以下內容加入你的 `claude_desktop_config.json` 檔案：
{
"mcpServers": {
"triageshield": {
"url": "https://triageshield.vercel.app/api/mcp"
}
}
}遠端端點
https://triageshield.vercel.app/api/mcpstreamable-http它能做什麼
工具清單
工具（1）
🟢check_vuln_report(report, repo)
Verify a vulnerability report's concrete, checkable claims (file paths, `file.py:123` line citations, function names) against a real GitHub repo's current default-branch state. Does NOT judge whether the described vulnerability is real or exploitable -- it only checks whether the files/lines/functions cited actually exist, which is the exact 'AI slop' failure mode (hallucinated specifics) that makes up a real share of auto-generated vuln reports. A PLAUSIBLE verdict means the claims check out, not that the vulnerability is confirmed real.
輸入結構描述
{
"type": "object",
"properties": {
"report": {
"type": "string",
"description": "The vulnerability report text to check"
},
"repo": {
"type": "string",
"description": "A github.com/owner/name URL for the repo the report claims to be about"
}
},
"required": [
"report",
"repo"
]
}社群
證據