# Blackpoint Cyber (oci · ghcr.io/wyre-ai/blackpoint-mcp)

MCP server for Blackpoint Cyber MDR — alerts, threats, and operations.

- Trust score: 41/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- oci · `ghcr.io/wyre-ai/blackpoint-mcp`: 41/100 (this document), [markdown](https://verifymcp.io/servers/wyre-ai-blackpoint-mcp/ghcr-io-wyre-ai-blackpoint-mcp.md), [page](https://verifymcp.io/servers/wyre-ai-blackpoint-mcp/ghcr-io-wyre-ai-blackpoint-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/blackpoint-mcp`
- Version: `v1.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-10-17.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1215 tokens (~86/item across 14 items; 14 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Blackpoint Cyber MCP server?

Blackpoint Cyber runs locally as a container image, launched with docker run --rm -i -e BLACKPOINT_API_TOKEN -e BLACKPOINT_BASE_URL -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/blackpoint-mcp:v1.2.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add wyre-ai-blackpoint-mcp -- docker run --rm -i -e BLACKPOINT_API_TOKEN -e BLACKPOINT_BASE_URL -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/blackpoint-mcp:v1.2.1
```

This image reads BLACKPOINT_API_TOKEN, BLACKPOINT_BASE_URL, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Cursor

```json
{
  "mcpServers": {
    "wyre-ai-blackpoint-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "BLACKPOINT_API_TOKEN",
        "-e",
        "BLACKPOINT_BASE_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/blackpoint-mcp:v1.2.1"
      ]
    }
  }
}
```

This image reads BLACKPOINT_API_TOKEN, BLACKPOINT_BASE_URL, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### VS Code

```json
{
  "servers": {
    "wyre-ai-blackpoint-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "BLACKPOINT_API_TOKEN",
        "-e",
        "BLACKPOINT_BASE_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/blackpoint-mcp:v1.2.1"
      ]
    }
  }
}
```

This image reads BLACKPOINT_API_TOKEN, BLACKPOINT_BASE_URL, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Codex

```bash
codex mcp add wyre-ai-blackpoint-mcp -- docker run --rm -i -e BLACKPOINT_API_TOKEN -e BLACKPOINT_BASE_URL -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/blackpoint-mcp:v1.2.1
```

This image reads BLACKPOINT_API_TOKEN, BLACKPOINT_BASE_URL, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-ai-blackpoint-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "BLACKPOINT_API_TOKEN",
        "-e",
        "BLACKPOINT_BASE_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/blackpoint-mcp:v1.2.1"
      ],
      "enabled": true
    }
  }
}
```

This image reads BLACKPOINT_API_TOKEN, BLACKPOINT_BASE_URL, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Hermes

```yaml
mcp_servers:
  wyre-ai-blackpoint-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "BLACKPOINT_API_TOKEN", "-e", "BLACKPOINT_BASE_URL", "-e", "MCP_TRANSPORT", "-e", "AUTH_MODE", "-e", "LOG_LEVEL", "ghcr.io/wyre-ai/blackpoint-mcp:v1.2.1"]
```

This image reads BLACKPOINT_API_TOKEN, BLACKPOINT_BASE_URL, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Netclaw

```json
{
  "McpServers": {
    "wyre-ai-blackpoint-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "BLACKPOINT_API_TOKEN",
        "-e",
        "BLACKPOINT_BASE_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/blackpoint-mcp:v1.2.1"
      ]
    }
  }
}
```

This image reads BLACKPOINT_API_TOKEN, BLACKPOINT_BASE_URL, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Other

```json
{
  "mcpServers": {
    "wyre-ai-blackpoint-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "BLACKPOINT_API_TOKEN",
        "-e",
        "BLACKPOINT_BASE_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/blackpoint-mcp:v1.2.1"
      ]
    }
  }
}
```

This image reads BLACKPOINT_API_TOKEN, BLACKPOINT_BASE_URL, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

## 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-10-17 (score 41, +1)

- [functional improvement] Stability: unverified → 0.10

### 2026-10-14 (score 40, +31)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

### 2026-10-11 (score 9)

First indexed and scored.

## MCP tools (14)

### `blackpoint_navigate` (~33 tokens)

Navigate to a specific CompassOne domain to access its tools

Input parameters:

- `domain` (string, required): Domain to navigate to

### `blackpoint_status` (~17 tokens)

Show current navigation state and available domains

### `blackpoint_tenants_list` (~85 tokens)

List customer tenants under the current partner account

Input parameters:

- `accountId` (string): Filter by specific account ID
- `page` (number): Page number (default: 1)
- `pageSize` (number): Items per page (default: 50)
- `search` (string): Search tenants by name
- `status` (array): Filter by tenant status

### `blackpoint_tenants_get` (~28 tokens)

Get detailed information about a specific tenant

Input parameters:

- `id` (string, required): Tenant ID

### `blackpoint_assets_list` (~166 tokens)

List assets for one tenant. class is required (CONTAINER, DEVICE, FRAMEWORK, NETSTAT, PERSON, PROCESS, SERVICE, SOFTWARE, SOURCE, SURVEY, USER). tenantId is sent as the x-tenant-id header. CLOUD is not an asset class.

Input parameters:

- `class` (string, required): Asset class to list (required). Sent as the class query parameter.
- `page` (number): Page number (default: 1)
- `pageSize` (number): Items per page (default: 50)
- `search` (string): Search assets by name or description
- `status` (string): Filter by asset status
- `tenantId` (string, required): Tenant ID. Required. Sent as the x-tenant-id header, not as a query parameter.

### `blackpoint_assets_get` (~61 tokens)

Get one asset by id. tenantId is required and is sent as the x-tenant-id header.

Input parameters:

- `id` (string, required): Asset ID
- `tenantId` (string, required): Tenant ID. Required. Sent as the x-tenant-id header.

### `blackpoint_assets_relationships` (~128 tokens)

List relationships for an asset. direction is in (the other entity points at this asset) or out (this asset points at the other entity). class is the far-side asset class and is sent as entityClass. tenantId is sent as x-tenant-id.

Input parameters:

- `assetId` (string, required): Source asset ID
- `class` (string, required): Far-side asset class. Sent as the entityClass query parameter.
- `direction` (string, required): Relationship direction: in or out
- `tenantId` (string, required): Tenant ID. Required. Sent as the x-tenant-id header.

### `blackpoint_assets_search` (~120 tokens)

Search assets in one tenant. Issues one list call per class (all documented classes when classes is omitted). tenantId is sent as x-tenant-id on every call.

Input parameters:

- `classes` (array): Asset classes to search. Defaults to every documented class.
- `query` (string, required): Search query (asset name, description, etc.)
- `tenantId` (string, required): Tenant ID. Required. Sent as the x-tenant-id header.
- `tenantIds` (array): Optional extra filter applied to the returned assets after the tenant-scoped list.

### `blackpoint_detections_list` (~156 tokens)

List alert groups for a tenant (CompassOne removed GET /detections; groups are the triage unit). Paged with skip/take. status is OPEN or RESOLVED. tenantId is sent as the x-tenant-id header.

Input parameters:

- `search` (string): Search alert groups
- `since` (string): ISO-8601 instant. CompassOne allows at most 90 days back.
- `skip` (number): Number of alert groups to skip
- `status` (string): Alert group status: OPEN or RESOLVED
- `take` (number): Number of alert groups to return
- `tenantId` (string, required): Tenant ID. Required. Sent as the x-tenant-id header.

### `blackpoint_detections_get` (~74 tokens)

Get one alert group by id. tenantId is required and is sent as the x-tenant-id header. Reads GET /alert-groups/{id}.

Input parameters:

- `id` (string, required): Alert group ID
- `tenantId` (string, required): Tenant ID. Required. Sent as the x-tenant-id header.

### `blackpoint_vulnerabilities_list` (~136 tokens)

List vulnerability findings with filtering options

Input parameters:

- `assetId` (string): Filter by specific asset ID
- `cveId` (string): Filter by specific CVE ID
- `exploitAvailable` (boolean): Filter by exploit availability
- `page` (number): Page number (default: 1)
- `pageSize` (number): Items per page (default: 50)
- `patchAvailable` (boolean): Filter by patch availability
- `severity` (array): Filter by severity levels
- `status` (array): Filter by vulnerability status
- `tenantId` (string): Filter by specific tenant ID

### `blackpoint_vulnerabilities_scans_list` (~72 tokens)

List vulnerability scans with their status

Input parameters:

- `assetId` (string): Filter by specific asset ID
- `page` (number): Page number (default: 1)
- `status` (array): Filter by scan status
- `tenantId` (string): Filter by specific tenant ID

### `blackpoint_vulnerabilities_darkweb_list` (~71 tokens)

List dark web exposures for monitoring

Input parameters:

- `exposureType` (array): Filter by exposure type
- `page` (number): Page number (default: 1)
- `severity` (array): Filter by severity levels
- `tenantId` (string): Filter by specific tenant ID

### `blackpoint_vulnerabilities_external_list` (~68 tokens)

List external exposure findings

Input parameters:

- `exposureType` (array): Filter by exposure type
- `page` (number): Page number (default: 1)
- `severity` (array): Filter by severity levels
- `tenantId` (string): Filter by specific tenant ID

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/wyre-ai-blackpoint-mcp/ghcr-io-wyre-ai-blackpoint-mcp#diagnostics

## Score history

- 2026-10-17: 41
- 2026-10-16: 40
- 2026-10-15: 40
- 2026-10-14: 40
- 2026-10-13: 9
- 2026-10-12: 9
- 2026-10-11: 9

## Common questions

### What is the Blackpoint Cyber MCP server?

Blackpoint Cyber is an MCP server listed in the public MCP registry as io.github.WYRE-AI/blackpoint-mcp. MCP server for Blackpoint Cyber MDR, alerts, threats, and operations. This page covers its container image (ghcr.io/wyre-ai/blackpoint-mcp).

### Is the Blackpoint Cyber MCP server safe to use?

Blackpoint Cyber scores 41 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 Blackpoint Cyber MCP server expose?

Blackpoint Cyber exposes 14 tools: blackpoint_navigate, blackpoint_status, blackpoint_tenants_list, blackpoint_tenants_get, blackpoint_assets_list, and 9 more. Their descriptions and schemas cost roughly 1,215 tokens of context every time the server is loaded.

### Is the Blackpoint Cyber MCP server still maintained?

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

### What licence is the Blackpoint Cyber MCP server under?

Blackpoint Cyber declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- GitHub Container Registry: https://ghcr.io/wyre-ai/blackpoint-mcp
- Repository: https://github.com/WYRE-AI/blackpoint-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-blackpoint-mcp/ghcr-io-wyre-ai-blackpoint-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-blackpoint-mcp/ghcr-io-wyre-ai-blackpoint-mcp.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-blackpoint-mcp/ghcr-io-wyre-ai-blackpoint-mcp