Search / app.vercel.triageshield/triageshield
protogridR0· no sign-inVerify a vuln report's file/line/function claims against a real GitHub repo.
v1.0.0 · active · website · descriptor JSON · versions
{
"mcpServers": {
"triageshield": {
"type": "http",
"url": "https://triageshield.vercel.app/api/mcp"
}
}
}claude mcp add --transport http triageshield https://triageshield.vercel.app/api/mcp[mcp_servers.triageshield]
url = "https://triageshield.vercel.app/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"triageshield": {
"type": "remote",
"url": "https://triageshield.vercel.app/api/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"triageshield": {
"type": "http",
"url": "https://triageshield.vercel.app/api/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=triageshield&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vdHJpYWdlc2hpZWxkLnZlcmNlbC5hcHAvYXBpL21jcCJ9"
}{
"servers": {
"triageshield": {
"type": "http",
"url": "https://triageshield.vercel.app/api/mcp"
}
}
}{
"mcpServers": {
"triageshield": {
"httpUrl": "https://triageshield.vercel.app/api/mcp"
}
}
}extensions:
"triageshield":
enabled: true
name: "triageshield"
type: streamable_http
uri: "https://triageshield.vercel.app/api/mcp"
timeout: 300
protocol.modernnewest supported version is 2025-03-26; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_lengthdescriptions are concisetools.schemasevery tool has an object input schematools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky onestools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: check_vuln_report (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)tools.token_costabout 205 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changesno tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+dns-namespace +website +reachable +uptime-100% ~updated-37d-ago -no-repository
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://triageshield.vercel.app/api/mcp streamable-http | none | yes | 100% | 253 ms | 2025-03-26 | 2026-10-20 |
check_vuln_report | 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. |
Schemas: list_tools.
{
"name": "app.vercel.triageshield/triageshield",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-09-29/server.schema.json",
"remotes": [
{
"url": "https://triageshield.vercel.app/api/mcp",
"type": "streamable-http"
}
],
"version": "1.0.0",
"websiteUrl": "https://triageshield.vercel.app",
"description": "Verify a vuln report's file/line/function claims against a real GitHub repo."
}