app.vercel.triageshield/triageshield vs GitLumen MCP
app.vercel.triageshield/triageshield is an MCP server published by triageshield.vercel.app. Marketplaces we read that list it: 1 (Official MCP Registry). GitLumen MCP is an MCP server published by gitlumen-team. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  GitLumen MCP | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | app.vercel.triageshield/triageshield | GitLumen MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (triageshield.vercel.app/api/mcp) | Remote server (mcp-github-screen.gitlumen.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/gitlumen-team/gitlumen-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 days ago | Not responding since 2026-10-13 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
app.vercel.triageshield/triageshield
Verify a vuln report's file/line/function claims against a real GitHub repo.
GitLumen MCP
Screens public GitHub repos and PRs to generate risk maps, findings, and merge-readiness signals.
How to run each
app.vercel.triageshield/triageshield As a remote MCP server
claude mcp add --transport http triageshield https://triageshield.vercel.app/api/mcpGitLumen MCP As a remote MCP server
claude mcp add --transport http gitlumen-mcp https://mcp-github-screen.gitlumen.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of app.vercel.triageshield/triageshield responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: app.vercel.triageshield/triageshield · What it can do: GitLumen MCP · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.