mcpbeat Sign in

Triageshield MCP Server

not responding

Triageshield is listed as active in the registry but did not answer our last check. It exposes 1 tools.

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

Uptime history 50 days of history · worst day 0%
50 days agonow
0.0%
Uptime 24h
0 of 91 checks
1
Tools
read from the server
69 ms
Response time
average over 24h
open, no key
Access
streamable-http

Triageshield does not always answer

Over the last week it answered 0.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 6 min ago.

run in your terminal
claude mcp add triageshield --transport http https://www.edgethirteen.com/api/mcp/triageshield
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "triageshield": {
      "type": "http",
      "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 69 ms 6 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.

89 installs/wk local only
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.

171 installs/wk local only
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.

83 installs/wk local only
Fin Codes API
by fincodesapi

Validate IBANs and bank codes, verify payee names, and screen names against sanctions lists.

answering
CI Guard MCP
by carelessdept

Local-first static repository security and configuration drift auditor (CLI, GitHub Action & MCP).

63 installs/wk local only
Pyxmark
by pyxmark

Vendor checks: sanctions lists, SEC filings, domain age and a due-diligence report with sources.

7 tools answering

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 0 of 91 checks got a reply (0.0%), average response time 69 ms. The bar chart above shows every period we have measured.
The registry lists Triageshield as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
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.