mcpbeat Sign in

Triageshield MCP Server

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 4 days of history · worst day 33%
4 days agonow
33.7%
Uptime 24h
31 of 92 checks
1
Tools
read from the server
846 ms
Response time
average over 24h
open, no key
Access
streamable-http

Triageshield does not always answer

Over the last week it answered 74.6% 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 2 min ago.

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

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.

verify
verify_vulnerability_report
Check a vulnerability report's concrete claims (file paths, file:line references, function names) against a real public GitHub repo's current contents. Flags claims that don't check out -- the file doesn't exist, the line is past EOF, the function isn't in the file -- which is the most common signature of an AI-generated fabricated vuln report. Does not judge whether a real, verifiable claim describes an actual security bug; it only checks whether the claim is honest about the codebase.

Endpoints

URLTransportStateLatencyChecked
https://www.edgethirteen.com/api/mcp/triageshield streamable-http answering 840 ms 2 min ago

Alternatives to Triageshield

same job, measured the same way
Triageshield
by vercel-triageshield

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: verify_vulnerability_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 31 of 92 checks got a reply (33.7%), average response time 846 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 846 ms on average, which is faster than 12% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.