app.vercel.triageshield/triageshield
https://triageshield.vercel.app/api/mcp ↗
Description
Verify a vuln report's file/line/function claims against a real GitHub repo.
What our measurements say
app.vercel.triageshield/triageshield is a remote MCP server published at triageshield.vercel.app. It has been probed 6 times since 9/14/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 262 ms, placing it among the faster endpoints. It offers a narrow, focused set of 1 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool name clearly indicates its purpose of verifying vulnerability reports.
- Description explicitly defines scope and limitations (e.g., does not assess exploitability).
- Parameters are clearly named and marked as required.
Weaknesses
- Description is truncated mid-sentence, creating ambiguity about functionality.
- No explicit error handling or validation constraints for invalid inputs (e.g., non-existent repos).
check_vuln_report— Description cut off mid-sentence, leaving functionality unclear.
Verdict
Event narrative
Sign up free to generateRaw observations
| Run | Era | Modern | ms |
|---|
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 171ms → warm 183ms (penalty 0ms)
Tools
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
check_vuln_reportVerify 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.
reportstringrequiredrepostringrequired
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Added to watch — era: Legacy
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/app-vercel-triageshield-triageshield)<a href="https://mcpmetrics.io/servers/app-vercel-triageshield-triageshield"><img src="https://mcpmetrics.io/badge/app.vercel.triageshield/triageshield/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeSimilar MCP servers
The catalog entries whose name and description are closest to this one, found with the same index the search box uses.
- GitHub Repo Shapeagent-observatory-sensor.nolimit-observatory.workers.dev
Parse owner and repo from a GitHub URL. Path discarded.
- Whysaid — Verify claims, sources & AI answer shareapi.whysaid.ai
Verify claims and sources, and check whether AI assistants name a brand.
- Trending Repository Tracker — new GitHub repo discovery ($0.01/query)a2awire.com
Trending GitHub repos: new & rising daily. $0.01/query. Register in-session — free testnet funds.
- Github Public Repos Mcpgithub-public-repos-mcp.mcpize.run
Dive into the world of open-source with the GitHub Repo Explorer! Utilize the powerful GitHub
- Korea Business Verify (KBV)kbv-server-f7vfitmlkq-du.a.run.app
Real-time Korean business verification via NTS. 10 free calls/day, then pay-per-call (x402).
- Repo-to-RAGrepo-to-rag-mcp.vercel.app
GitHub repository vectorizer and context synthesizer for RAG pipelines.
Comments
Sign in to write a comment
No comments yet. Be the first.