Is the Vercel Triageshield Triageshield MCP server down?

mcp-registry/app.vercel.triageshield/triageshield · v1.0.0

As of 2026-10-26 18:12 UTC, the Vercel Triageshield Triageshield MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

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

Point your MCP client at this streamable-http endpoint: https://triageshield.vercel.app/api/mcp

Agent-readiness: B (82/100)

What to fix (3)

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fapp.vercel.triageshield%2Ftriageshield/fixes

{
  "name": "check_vuln_report",
  "description": "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, n",
  "inputSchema": {
    "type": "object",
    "required": [
      "report",
      "repo"
    ],
    "properties": {
      "repo": {
        "type": "string",
        "description": "A github.com/owner/name URL for the repo the report claims to be about"
      },
      "report": {
        "type": "string",
        "description": "The vulnerability report text to check"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/app.vercel.triageshield/triageshield"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/app.vercel.triageshield/triageshield"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~227 tokens).
• Tool names are unique and portable across clients.
• 100.00% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• check_vuln_report ~227 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.vercel.triageshield%2Ftriageshield.svg)](https://glimind.com/server/mcp-registry%2Fapp.vercel.triageshield%2Ftriageshield?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fapp.vercel.triageshield%2Ftriageshield?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.vercel.triageshield%2Ftriageshield.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.vercel.triageshield%2Ftriageshield.svg
   :target: https://glimind.com/server/mcp-registry%2Fapp.vercel.triageshield%2Ftriageshield?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:7b4b4e2fb7c2d7d5…, first seen 2026-10-17, included at leaf 10688 of 74,624. Version history · verify what your client received.

Tools (1)

• check_vuln_report

Compare: most reliable security servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Vercel Triageshield Triageshield MCP server down right now?

As of 2026-10-26 18:12 UTC, the Vercel Triageshield Triageshield MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Vercel Triageshield Triageshield MCP server provide?

Vercel Triageshield Triageshield MCP server advertises 1 tool, including check_vuln_report.

How do I install Vercel Triageshield Triageshield MCP server?

Point your MCP client at this streamable-http endpoint: https://triageshield.vercel.app/api/mcp

Is the Vercel Triageshield Triageshield MCP server safe to connect to an AI agent?

Glimind scanned all 1 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Vercel Triageshield Triageshield MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.