Triageshield MCP server

• verify_vulnerability_reportFree

  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.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 344ms20/20
• Tool poisoning1 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenanceno repository listed3/15
• Maintainer identityverified namespace with website, no repo4/10

Triageshield: common questions

Is Triageshield MCP server safe?

With care: it is graded C, so read the findings first (69/100). Read the Triageshield safety report

How do I install Triageshield?

It runs remotely at www.edgethirteen.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Triageshield need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Triageshield maintained?

The latest release is v1.0.0.

Is Triageshield up?

100% of our last 1 checks got an answer. We check remote servers about four times a day.

What can I use instead of Triageshield?

Servers from other publishers that do the same job: GitPin MCP server, Triageshield MCP server and GitHub MCP server. Compare all Triageshield alternatives.