Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Blackpoint Cyber

OCI · GHCR.IO/WYRE-AI/BLACKPOINT-MCP:V1.1.15 · SCANNED SEP 20

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

+3 this week 47 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security0
  • Malware scan not yet available for this package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency45
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 932 tokens (~66/item across 14 items; 14 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

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 ghcr.io/wyre-ai/blackpoint-mcp:v1.1.15. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/wyre-ai/blackpoint-mcp:v1.1.15

# add to Claude Code
claude mcp add wyre-ai-blackpoint-mcp -- docker run --rm -i ghcr.io/wyre-ai/blackpoint-mcp:v1.1.15
// .cursor/mcp.json
{
  "mcpServers": {
    "wyre-ai-blackpoint-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/blackpoint-mcp:v1.1.15"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "wyre-ai-blackpoint-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/blackpoint-mcp:v1.1.15"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add wyre-ai-blackpoint-mcp -- docker run --rm -i ghcr.io/wyre-ai/blackpoint-mcp:v1.1.15
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-ai-blackpoint-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/blackpoint-mcp:v1.1.15"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  wyre-ai-blackpoint-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/wyre-ai/blackpoint-mcp:v1.1.15"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "wyre-ai-blackpoint-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/blackpoint-mcp:v1.1.15"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "wyre-ai-blackpoint-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/blackpoint-mcp:v1.1.15"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

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

  • 17 Sept 26 +1

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

  • 15 Sept 26 +1

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

  • 13 Sept 26 +1

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

  • 11 Sept 26 +4
    • Stability: unverified → 0.27 functional
  • 3 Sept 26 39

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed oci/ghcr.io/wyre-ai/blackpoint-mcp:v1.1.15

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 14 exposed · ~932 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
blackpoint_assets_get ~27

Get detailed information about a specific asset

NameTypeReqDescription
idstringyesAsset ID

No output schema declared.

No examples provided.

blackpoint_assets_list ~114

List assets by class (endpoint, server, network, cloud, mobile, iot). Returns paginated results.

NameTypeReqDescription
classstringyesAsset class to filter by (required)
pagenumberPage number (default: 1)
pageSizenumberItems per page (default: 50)
searchstringSearch assets by name or description
statusstringFilter by asset status
tenantIdstringFilter by specific tenant ID

No output schema declared.

No examples provided.

blackpoint_assets_relationships ~54

List relationships for an asset (parent/child/sibling connections)

NameTypeReqDescription
assetIdstringyesSource asset ID
classstringyesRelated asset class
directionstringyesRelationship direction

No output schema declared.

No examples provided.

blackpoint_assets_search ~60

Search assets across all classes with flexible filtering

NameTypeReqDescription
classesarrayAsset classes to search within
querystringyesSearch query (asset name, description, etc.)
tenantIdsarrayTenant IDs to search within

No output schema declared.

No examples provided.

blackpoint_detections_get ~29

Get detailed information about a specific detection

NameTypeReqDescription
idstringyesDetection ID

No output schema declared.

No examples provided.

blackpoint_detections_list ~138

List security detections with filtering options

NameTypeReqDescription
assetIdstringFilter by specific asset ID
fromDatestringFilter detections from this date (ISO 8601 format)
pagenumberPage number (default: 1)
pageSizenumberItems per page (default: 50)
severityarrayFilter by severity levels
statusarrayFilter by detection status
tenantIdstringFilter by specific tenant ID
toDatestringFilter detections to this date (ISO 8601 format)

No output schema declared.

No examples provided.

blackpoint_navigate ~33

Navigate to a specific CompassOne domain to access its tools

NameTypeReqDescription
domainstringyesDomain to navigate to

No output schema declared.

No examples provided.

blackpoint_status ~17

Show current navigation state and available domains

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

blackpoint_tenants_get ~28

Get detailed information about a specific tenant

NameTypeReqDescription
idstringyesTenant ID

No output schema declared.

No examples provided.

blackpoint_tenants_list ~85

List customer tenants under the current partner account

NameTypeReqDescription
accountIdstringFilter by specific account ID
pagenumberPage number (default: 1)
pageSizenumberItems per page (default: 50)
searchstringSearch tenants by name
statusarrayFilter by tenant status

No output schema declared.

No examples provided.

blackpoint_vulnerabilities_darkweb_list ~71

List dark web exposures for monitoring

NameTypeReqDescription
exposureTypearrayFilter by exposure type
pagenumberPage number (default: 1)
severityarrayFilter by severity levels
tenantIdstringFilter by specific tenant ID

No output schema declared.

No examples provided.

blackpoint_vulnerabilities_external_list ~68

List external exposure findings

NameTypeReqDescription
exposureTypearrayFilter by exposure type
pagenumberPage number (default: 1)
severityarrayFilter by severity levels
tenantIdstringFilter by specific tenant ID

No output schema declared.

No examples provided.

blackpoint_vulnerabilities_list ~136

List vulnerability findings with filtering options

NameTypeReqDescription
assetIdstringFilter by specific asset ID
cveIdstringFilter by specific CVE ID
exploitAvailablebooleanFilter by exploit availability
pagenumberPage number (default: 1)
pageSizenumberItems per page (default: 50)
patchAvailablebooleanFilter by patch availability
severityarrayFilter by severity levels
statusarrayFilter by vulnerability status
tenantIdstringFilter by specific tenant ID

No output schema declared.

No examples provided.

blackpoint_vulnerabilities_scans_list ~72

List vulnerability scans with their status

NameTypeReqDescription
assetIdstringFilter by specific asset ID
pagenumberPage number (default: 1)
statusarrayFilter by scan status
tenantIdstringFilter by specific tenant ID

No output schema declared.

No examples provided.

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:v1.1.15).

Is the Blackpoint Cyber MCP server safe to use?

Blackpoint Cyber scores 47 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 932 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 20 September 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.