Blackpoint Cyber
OCI · GHCR.IO/WYRE-AI/BLACKPOINT-MCP
MCP server for Blackpoint Cyber MDR — alerts, threats, and operations.
Available components
Last scanned (5 hours ago)
Scores higher than 57% of OCI servers
Category Security
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
- 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.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1215 tokens (~86/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 Management10
- Stability observed for 3 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.
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.
- 17 Oct 26 +1
- Stability: unverified → 0.10 ▲ functional
- 14 Oct 26 +31
- 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). security
- Tool coverage: unverified → 100 ▲ functional
- 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 functional
- 11 Oct 26 9
First indexed and scored.
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 17 Oct 2026 · Analysed oci/ghcr.io/wyre-ai/blackpoint-mcp@v1.2.1
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 →
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 →
blackpoint_assets_get ~61
Get one asset by id. tenantId is required and is sent as the x-tenant-id header.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Asset ID |
| tenantId | string | yes | Tenant ID. Required. Sent as the x-tenant-id header. |
No output schema declared.
No examples provided.
blackpoint_assets_list ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| class | string | yes | 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 | yes | Tenant ID. Required. Sent as the x-tenant-id header, not as a query parameter. |
No output schema declared.
No examples provided.
blackpoint_assets_relationships ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| assetId | string | yes | Source asset ID |
| class | string | yes | Far-side asset class. Sent as the entityClass query parameter. |
| direction | string | yes | Relationship direction: in or out |
| tenantId | string | yes | Tenant ID. Required. Sent as the x-tenant-id header. |
No output schema declared.
No examples provided.
blackpoint_assets_search ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| classes | array | – | Asset classes to search. Defaults to every documented class. |
| query | string | yes | Search query (asset name, description, etc.) |
| tenantId | string | yes | 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. |
No output schema declared.
No examples provided.
blackpoint_detections_get ~74
Get one alert group by id. tenantId is required and is sent as the x-tenant-id header. Reads GET /alert-groups/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Alert group ID |
| tenantId | string | yes | Tenant ID. Required. Sent as the x-tenant-id header. |
No output schema declared.
No examples provided.
blackpoint_detections_list ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Tenant ID. Required. Sent as the x-tenant-id header. |
No output schema declared.
No examples provided.
blackpoint_navigate ~33
Navigate to a specific CompassOne domain to access its tools
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain 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
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Tenant ID |
No output schema declared.
No examples provided.
blackpoint_tenants_list ~85
List customer tenants under the current partner account
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
blackpoint_vulnerabilities_darkweb_list ~71
List dark web exposures for monitoring
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
blackpoint_vulnerabilities_external_list ~68
List external exposure findings
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
blackpoint_vulnerabilities_list ~136
List vulnerability findings with filtering options
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
blackpoint_vulnerabilities_scans_list ~72
List vulnerability scans with their status
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
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.
oci · ghcr.io/wyre-ai/blackpoint-mcp
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.
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.