# com.edgethirteen.www/triageshield (remote · www.edgethirteen.com)

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

- Trust score: 78/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `www.edgethirteen.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-edgethirteen-www-triageshield/api-mcp-triageshield.md), [page](https://verifymcp.io/servers/com-edgethirteen-www-triageshield/api-mcp-triageshield)

## Channel facts

- Endpoint: `https://www.edgethirteen.com/api/mcp/triageshield`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 86/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 145 tokens (~145/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the com.edgethirteen.www/triageshield MCP server?

com.edgethirteen.www/triageshield is a hosted endpoint at https://www.edgethirteen.com/api/mcp/triageshield, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-edgethirteen-www-triageshield 'https://www.edgethirteen.com/api/mcp/triageshield'
```

### Cursor

```json
{
  "mcpServers": {
    "com-edgethirteen-www-triageshield": {
      "url": "https://www.edgethirteen.com/api/mcp/triageshield"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-edgethirteen-www-triageshield": {
      "type": "http",
      "url": "https://www.edgethirteen.com/api/mcp/triageshield"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-edgethirteen-www-triageshield]
url = "https://www.edgethirteen.com/api/mcp/triageshield"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-edgethirteen-www-triageshield": {
      "type": "remote",
      "url": "https://www.edgethirteen.com/api/mcp/triageshield",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-edgethirteen-www-triageshield --url 'https://www.edgethirteen.com/api/mcp/triageshield' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-edgethirteen-www-triageshield:
    url: "https://www.edgethirteen.com/api/mcp/triageshield"
```

### Netclaw

```json
{
  "McpServers": {
    "com-edgethirteen-www-triageshield": {
      "Transport": "http",
      "Url": "https://www.edgethirteen.com/api/mcp/triageshield"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-edgethirteen-www-triageshield -t streamable-http -u 'https://www.edgethirteen.com/api/mcp/triageshield'
```

### Other

```json
{
  "mcpServers": {
    "com-edgethirteen-www-triageshield": {
      "type": "http",
      "url": "https://www.edgethirteen.com/api/mcp/triageshield"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 77, +3)

- [functional improvement] MCP protocol: fail → pass
- [functional] MCP protocol version: 2025-03-26 → 2025-11-25

### 2026-09-17 (score 74, +7)

- [security improvement] Authorization: unverified → partial

### 2026-09-15 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-14 (score 66)

First indexed and scored.

## MCP tools (1)

### `verify_vulnerability_report` (~145 tokens)

Check a vulnerability report's concrete claims (file paths, file:line references, function names) against a real public GitHub repo's current contents. Flags claims that don't check out -- the file doesn't exist, the line is past EOF, the function isn't in the file -- which is the most common signature of an AI-generated fabricated vuln report. Does not judge whether a real, verifiable claim describes an actual security bug; it only checks whether the claim is honest about the codebase.

Input parameters:

- `repo` (string, required): A github.com/owner/name URL for the public repo being reported against
- `report` (string, required): The full text of the vulnerability report to check

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-edgethirteen-www-triageshield/api-mcp-triageshield#diagnostics

## Score history

- 2026-09-20: 78
- 2026-09-19: 78
- 2026-09-18: 77
- 2026-09-17: 74
- 2026-09-16: 67
- 2026-09-15: 67
- 2026-09-14: 66

## Common questions

### What is the com.edgethirteen.www/triageshield MCP server?

com.edgethirteen.www/triageshield is an MCP server listed in the public MCP registry as com.edgethirteen.www/triageshield. Verify a vuln report's file/line/function claims against a real GitHub repo. This page covers its hosted endpoint (https://www.edgethirteen.com/api/mcp/triageshield).

### Is the com.edgethirteen.www/triageshield MCP server safe to use?

com.edgethirteen.www/triageshield scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the com.edgethirteen.www/triageshield MCP server expose?

com.edgethirteen.www/triageshield exposes 1 tool: verify_vulnerability_report. Their descriptions and schemas cost roughly 145 tokens of context every time the server is loaded.

### Does the com.edgethirteen.www/triageshield MCP server require authentication?

No. We connected to com.edgethirteen.www/triageshield without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the com.edgethirteen.www/triageshield MCP server still maintained?

com.edgethirteen.www/triageshield is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.edgethirteen.com/api/mcp/triageshield
- Website: https://www.edgethirteen.com/tools/triageshield
- Changelog RSS feed: https://verifymcp.io/servers/com-edgethirteen-www-triageshield/api-mcp-triageshield.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-edgethirteen-www-triageshield/api-mcp-triageshield.json
- HTML version of this page: https://verifymcp.io/servers/com-edgethirteen-www-triageshield/api-mcp-triageshield