Verify a vuln report's file/line/function claims against a real GitHub repo.
Scored across 1 tool
With only one tool, there is no possibility of overlap or misselection, and the tool's purpose is stated with unusual precision (it checks concrete cited claims, explicitly not vulnerability validity). An agent cannot confuse it with anything else in this surface.
The single name, check_vuln_report, follows a clean snake_case verb_noun convention and reads clearly. It is consistent by construction, though a one-tool set cannot demonstrate a repeatable pattern across the surface.
A single tool is thin even for a narrow purpose, and the server name 'triageshield' implies broader triage activity than one check operation. It is borderline rather than mismatched, since claim verification is genuinely a single focused check.
For the narrow claim-verification task the surface is reasonably covered, but the 'triage' framing suggests missing operations: no severity/exploitability assessment, no summarization of which claims failed, and no repo-inspection helper. Agents hitting those needs will dead-end.
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.
Inputs: repo (required), report (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Verify a vuln report's file/line/function claims against a real GitHub repo.
Scan a public GitHub repo, explain risks, get fix prompts and rescan to confirm fixes.
Scan a GitHub repository for vulnerabilities, with proof for every finding, from your coding agent.
Independent static verification for exact immutable public GitHub commits.
Add one secure layer between your agents and this server.