triageshield
Verify a vuln report's file/line/function claims against a real GitHub repo.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"triageshield": {
"url": "https://triageshield.vercel.app/api/mcp"
}
}
}Remote endpoints
https://triageshield.vercel.app/api/mcpstreamable-httpWhat it can do
Tool inventory
Tools (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.
Input Schema
{
"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"
]
}Community
Evidence