Triageshield
com.edgethirteen.wwwPublished by www.edgethirteen.comOfficial publisherv1.0.0Updated Oct 24, 2026
Verify a vuln report's file/line/function claims against a real GitHub repo.
The publisher's own server: Accessproof
Overview
Checks whether a vulnerability report's claimed file, line, and function actually exist in a real GitHub repository.
- What you can do
- Triageshield is a remote MCP server that verifies claims made in a vulnerability report against an actual GitHub repository. It takes the file, line, and function references cited in a report and checks them against the repository contents, helping an assistant confirm whether the cited code locations are real. The manifest lists no tools, so the exact operations are not documented here.
- When to use it
- Useful when triaging vulnerability reports or bug bounty submissions and you want to confirm that the cited file paths, line numbers, and function names exist before spending time on deeper analysis. It suits workflows where false or fabricated code references are a common noise source.
- Requirements
- A remote MCP server reached over streamable HTTP at the provider's endpoint; no package installation is needed. The manifest declares no authentication, environment variables, or headers, but access to the GitHub repository being checked is implied by the described function.
Installation
In SourceWeft
- Open Triageshield in the dashboard and add it to a workspace.
- 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/com.edgethirteen.www%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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"triageshield": {
"type": "http",
"url": "https://www.edgethirteen.com/api/mcp/triageshield"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
56% 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
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- 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.
Other Edgethirteen integrations
Accessproof
com.edgethirteen.wwwOfficial publisher
Scans a web page's markup for common WCAG accessibility failures, such as those cited in ADA demand letters.
Sanctions
com.edgethirteen.wwwOfficial publisher
Lets an assistant screen a person or entity name against OFAC's SDN and Consolidated Sanctions lists before a transaction.
Voicebrief
com.edgethirteen.wwwOfficial publisher
A remote MCP endpoint that supplies SEC-grounded stock facts phrased as single spoken sentences for a voice assistant to read aloud.
Tariff Refund Screen
com.edgethirteen.wwwOfficial publisher
A remote MCP server that screens US public companies for IEEPA tariff-refund exposure disclosed in their SEC filings.
Hubspot Dbv
com.edgethirteen.wwwOfficial publisher
A remote MCP endpoint that maps HubSpot legacy v1–v4 API operations to their date-based-versioning replacements.