mcpbeat Sign in

Triageshield MCP Server

by vercel-triageshield Your server? Claim it
answering

Triageshield is answering right now. Last checked 2 min ago. It exposes 1 tools.

Verify a vuln report's file/line/function claims against a real GitHub repo.

Uptime history 5 days of history
5 days agonow
100.0%
Uptime 24h
92 of 92 checks
1
Tools
read from the server
238 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Triageshield every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add triageshield --transport http https://triageshield.vercel.app/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "triageshield": {
      "url": "https://triageshield.vercel.app/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.triageshield]
url = "https://triageshield.vercel.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "triageshield": {
      "url": "https://triageshield.vercel.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "triageshield": {
      "url": "https://triageshield.vercel.app/api/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

vuln
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.

Endpoints

URLTransportStateLatencyChecked
https://triageshield.vercel.app/api/mcp streamable-http answering 227 ms 2 min ago

Alternatives to Triageshield

same job, measured the same way
Triageshield
by edgethirteen-www

Verify a vuln report's file/line/function claims against a real GitHub repo.

1 tools answering
GitPin
by shmindmaster

Prove and verify multi-repo claims at Git HEAD: path, line, full SHA, no index.

241 installs/wk local only
MCP Assist — Coordination Memory
by aliomranih

Coordination memory with verification: reconcile-against-GitHub, verdict freshness, provenance.

answering
Botcall MCP
by danecodes

Give your AI agent a real phone number for SMS verification codes.

22 installs/wk local only
Kage
by kage-core

Verified memory for coding agents: claims cited against code, stale withheld, savings receipts.

216 installs/wk local only
RepoFold
by repofold

A cited wiki of your GitHub repo: search, read pages, find symbols and ask, with line citations.

answering
Prumo
by tomd4vs

Checks the context files a coding agent reads against the git index, and reports what drifted.

296 installs/wk local only
Audit
by commitshow

Score any public GitHub repo 0-100 against the commit.show audit rubric.

35 installs/wk local only

Triageshield — questions

Answers built from our own checks of this server.

What can Triageshield do?
It exposes 1 tools, read directly from the server on our last check. Among them: check_vuln_report. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Triageshield working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 238 ms. The bar chart above shows every period we have measured.
How do I connect Triageshield?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Triageshield need an API key?
No. Triageshield completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Triageshield?
It answers our handshake in 238 ms on average, which is faster than 59% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.