All servers · Code & repositories · Security
app.vercel.triageshield/triageshield
app.vercel.triageshield/triageshield · v1.0.0
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-03-26 |
| Rank score | — |
| Declared risk | Not declared (tools carry no read/destructive hints) |
| Capabilities declared | tools |
| Tool definitions | 1 tools · with description 100% · input schema is an object 100% · read/destructive hints 0% |
Description written by the publisher, not verified
Verify a vuln report's file/line/function claims against a real GitHub repo.
Connect
streamable-http · https://triageshield.vercel.app/api/mcp
claude mcp add --transport http triageshield https://triageshield.vercel.app/api/mcp{
"mcpServers": {
"triageshield": {
"url": "https://triageshield.vercel.app/api/mcp"
}
}
}Tools as reported by the server
check_vuln_reportVerify 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/functio
Website · JSON · Text for agents · Registry updated 2026-09-13