# CybRelay (remote · api.cybrelay.com)

Vulnerability remediation for AI agents: deterministic fix scripts, AI advice only, web scan.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.cybrelay.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/com-cybrelay-mcp/api.md), [page](https://verifymcp.io/servers/com-cybrelay-mcp/api)
- remote · `api.cybrelay.com`: 36/100, [markdown](https://verifymcp.io/servers/com-cybrelay-mcp/api-2.md), [page](https://verifymcp.io/servers/com-cybrelay-mcp/api-2)

## Channel facts

- Endpoint: `https://api.cybrelay.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1185 tokens (~169/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 CybRelay MCP server?

CybRelay is a hosted endpoint at https://api.cybrelay.com/mcp, 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-cybrelay-mcp 'https://api.cybrelay.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-cybrelay-mcp": {
      "url": "https://api.cybrelay.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-cybrelay-mcp:
    url: "https://api.cybrelay.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

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

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-11-21 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-20 (score 65, +29)

- [security regression] Authorization: fail → unverified
- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: fail

### 2026-11-17 (score 36)

First indexed and scored.

## MCP tools (7)

### `list_vulnerabilities` (~194 tokens)

Liste les failles réellement enregistrées dans votre espace CybRelay (analyses du site, du pipeline CI, de l'API et de la passerelle MCP), triées par priorité. Filtres stricts : un filtre sans correspondance renvoie 0 résultat.

Input parameters:

- `analysis_id` (string): Identifiant d'une analyse (renvoyé par trigger_pipeline_scan)
- `deduplicated_only` (boolean): Une faille retrouvée dans plusieurs analyses ne compte qu’une fois (la plus récente)
- `limit` (integer): Nombre maximum de résultats (100 au plus)
- `priority` (string): Filtre par priorité CybRelay
- `repo_name` (string): Projet : référence PRJ-…, nom du projet, adresse du dépôt ou « organisation/dépôt ». Vide ou « all » : tout l'espace.
- `severity` (string): Filtre par sévérité

### `analyze_file` (~228 tokens)

Analyse avec le moteur CybRelay le contenu envoyé par l'assistant : un fichier de code source ou le rapport d'un scanner (Trivy, SARIF, Snyk, SonarQube, Checkmarx, ZAP…). CybRelay ne clone aucun dépôt. Crédits débités selon le barème habituel ; un contenu déjà analysé n'est pas facturé une seconde fois.

Input parameters:

- `branch` (string): Branche, pour ranger l’analyse dans le sous-projet correspondant
- `fail_on` (string): Décision renvoyée (gate) : p1, p2 ou none (défaut)
- `file_content` (string): Contenu complet du fichier (15 Mo au plus)
- `file_name` (string): Nom du fichier (ex. src/routes/user.ts ou trivy-report.json)
- `project_reference` (string): Référence du projet CybRelay (PRJ-…) où ranger l’analyse
- `repo_url` (string): Adresse du dépôt, pour ranger l'analyse dans le projet correspondant (aucun clonage)

### `trigger_pipeline_scan` (~243 tokens)

[Ancien nom gardé pour compatibilité : utilisez analyze_file] Analyse avec le moteur CybRelay le contenu envoyé par l'assistant : un fichier de code source ou le rapport d'un scanner (Trivy, SARIF, Snyk, SonarQube, Checkmarx, ZAP…). CybRelay ne clone aucun dépôt. Crédits débités selon le barème habituel ; un contenu déjà analysé n'est pas facturé une seconde fois.

Input parameters:

- `branch` (string): Branche, pour ranger l’analyse dans le sous-projet correspondant
- `fail_on` (string): Décision renvoyée (gate) : p1, p2 ou none (défaut)
- `file_content` (string): Contenu complet du fichier (15 Mo au plus)
- `file_name` (string): Nom du fichier (ex. src/routes/user.ts ou trivy-report.json)
- `project_reference` (string): Référence du projet CybRelay (PRJ-…) où ranger l’analyse
- `repo_url` (string): Adresse du dépôt, pour ranger l'analyse dans le projet correspondant (aucun clonage)

### `get_remediation_patch` (~150 tokens)

Fournit le script de correction d'une faille de votre espace (et le correctif .patch quand le moteur a pu le valider sur le fichier envoyé). CybRelay n'applique rien dans votre dépôt et n'ouvre aucune pull request : l'assistant ou vous l'appliquez après relecture.

Input parameters:

- `file_content` (string): Contenu actuel du fichier concerné (2 Mo au plus) : permet au moteur de préparer et valider un correctif .patch
- `language` (string): Langage du script de correction (bash par défaut)
- `vulnerability_id` (string, required): Identifiant exact de la faille (renvoyé par list_vulnerabilities)

### `apply_remediation_patch` (~166 tokens)

[Ancien nom gardé pour compatibilité : utilisez get_remediation_patch] Fournit le script de correction d'une faille de votre espace (et le correctif .patch quand le moteur a pu le valider sur le fichier envoyé). CybRelay n'applique rien dans votre dépôt et n'ouvre aucune pull request : l'assistant ou vous l'appliquez après relecture.

Input parameters:

- `file_content` (string): Contenu actuel du fichier concerné (2 Mo au plus) : permet au moteur de préparer et valider un correctif .patch
- `language` (string): Langage du script de correction (bash par défaut)
- `vulnerability_id` (string, required): Identifiant exact de la faille (renvoyé par list_vulnerabilities)

### `get_scan_status` (~67 tokens)

Donne l'état et la synthèse (sévérités, priorités, empreinte SHA-256 du fichier analysé) d'une analyse de votre espace.

Input parameters:

- `scan_job_id` (string, required): Identifiant de l'analyse renvoyé par trigger_pipeline_scan (analysis_id)

### `scan_url_surface` (~137 tokens)

Scan SURFACE d'un site : contrôles passifs de configuration (en-têtes HTTP, TLS, redirection HTTPS, cookies, DNS de messagerie, security.txt), note de A+ à F. Aucun test d'intrusion. 1 scan gratuit par jour pour l'espace, ensuite payé en crédits au prix de la page publique. Résultat lisible 48 h ; masqué de la liste publique sauf hidden=false.

Input parameters:

- `hidden` (boolean): true (par défaut) : absent de la liste publique des scans récents
- `url` (string, required): Adresse du site (ex. https://exemple.com)

## Diagnostics

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

## Score history

- 2026-11-21: 66
- 2026-11-20: 65
- 2026-11-19: 36
- 2026-11-18: 36
- 2026-11-17: 36

## Common questions

### What is the CybRelay MCP server?

CybRelay is an MCP server listed in the public MCP registry as com.cybrelay/mcp. Vulnerability remediation for AI agents: deterministic fix scripts, AI advice only, web scan. This page covers its hosted endpoint (https://api.cybrelay.com/mcp).

### Is the CybRelay MCP server safe to use?

CybRelay scores 66 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 CybRelay MCP server expose?

CybRelay exposes 7 tools: list_vulnerabilities, analyze_file, trigger_pipeline_scan, get_remediation_patch, apply_remediation_patch, and 2 more. Their descriptions and schemas cost roughly 1,185 tokens of context every time the server is loaded.

### Does the CybRelay MCP server require authentication?

No. We connected to CybRelay without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the CybRelay MCP server still maintained?

CybRelay is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the CybRelay MCP server?

VerifyMCP ran 12 checks on CybRelay, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about CybRelay: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.cybrelay.com/mcp
- Authorisation metadata: https://api.cybrelay.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/cybrelay/cybrelay-mcp
- Website: https://cybrelay.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-cybrelay-mcp/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-cybrelay-mcp/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-cybrelay-mcp/api.json
- HTML version of this page: https://verifymcp.io/servers/com-cybrelay-mcp/api
