mcpbeat Sign in

Triageshield MCP Server

by vercel-triageshield Your server? Claim it
answering

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

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

Uptime history 56 days of history · worst day 42%
56 days agonow
65.2%
Uptime 24h
60 of 92 checks
1
Tools
read from the server
251 ms
Response time
average over 24h
open, no key
Access
streamable-http

Triageshield does not always answer

Over the last week it answered 75.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

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 3 min ago.

run in your terminal
claude mcp add triageshield --transport http https://triageshield.vercel.app/api/mcp
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "triageshield": {
      "type": "http",
      "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 245 ms 3 min ago

Alternatives to Triageshield

same job, measured the same way
GitPin
by shmindmaster

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

71 installs/wk local only
Contribpath
by cloudcorprecords

Check a CONTRIBUTING document against the repo's actual contribution gates; report gaps.

288 installs/wk local only
M
MALN — Multi-Agent Learning Network
by trenchsearch

Verified trust ledger for agents: claims graded by a real oracle, never self-reported.

8 tools answering
Botcall MCP
by danecodes

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

34 installs/wk local only
Kage
by kage-core

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

104 installs/wk local only
veraPDF by pagespool
by pagespool

Hosted veraPDF: check a PDF against PDF/A or PDF/UA and get the full validation report.

2 tools answering
spendtron
by swantron

Finds the GitHub Actions workflow eating your CI bill and suggests fix diffs, verified against runs.

1 tools answering
Prumo
by tomd4vs

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

90 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 60 of 92 checks got a reply (65.2%), average response time 251 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 in the form 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 251 ms on average, which is faster than 56% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.