app.vercel.triageshield/triageshield is an MCP server published by app.vercel.triageshield, hosted at triageshield.vercel.app. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 1 tool, including check_vuln_report.
Verify a vuln report's file/line/function claims against a real GitHub repo.
107 connections through 4 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
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.
| Parameter | Type | Description |
|---|---|---|
| repo * | string | A github.com/owner/name URL for the repo the report claims to be about |
| report * | string | The vulnerability report text to check |
{
"name": "check_vuln_report",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"report",
"repo"
],
"properties": {
"repo": {
"type": "string",
"description": "A github.com/owner/name URL for the repo the report claims to be about"
},
"report": {
"type": "string",
"description": "The vulnerability report text to check"
}
}
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.