Triageshield

app.vercel.triageshieldPublished by triageshield.vercel.appOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Checks a vulnerability report's file, line and function claims against a GitHub repository's current default branch.

What you can do
Triageshield exposes a single tool, check_vuln_report. It takes the concrete, checkable claims in a vulnerability report — file paths, file.py:123 line citations and function names — and verifies them against the current state of a real GitHub repository's default branch. It does not judge whether the described vulnerability is real or exploitable; it only reports whether the referenced files, lines and functions exist as stated.
When to use it
Useful when triaging incoming vulnerability reports and you want a quick check of whether the cited code locations actually exist before spending time on deeper analysis. It fits workflows where reports reference specific GitHub repositories and line-level citations.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package, environment variables or headers are declared. The tool works against GitHub repositories, so the assistant needs the repository reference for each report.
Before you install
The tool only verifies that cited files, lines and functions exist; a passing check does not mean a vulnerability is real, and a failing one does not rule it out. Reports and repository details are sent to a third-party hosted endpoint, so avoid submitting sensitive or private report content unless that is acceptable.

Installation

In SourceWeft

  1. Open Triageshield in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.vercel.triageshield%2Ftriageshield/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "triageshield": {
      "type": "http",
      "url": "https://triageshield.vercel.app/api/mcp"
    }
  }
}

Tools

1

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.

Parametersreporequiredreportrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.