# CyberQP (oci · ghcr.io/wyre-ai/cyberqp-mcp:v1.0.0)

MCP server for CyberQP's privileged access management API.

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

## Components

- oci · `ghcr.io/wyre-ai/cyberqp-mcp:v1.0.0`: 39/100 (this document), [markdown](https://verifymcp.io/servers/wyre-ai-cyberqp-mcp/ghcr-io-wyre-ai-cyberqp-mcp-v1-0-0.md), [page](https://verifymcp.io/servers/wyre-ai-cyberqp-mcp/ghcr-io-wyre-ai-cyberqp-mcp-v1-0-0)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/cyberqp-mcp:v1.0.0`
- 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-09-20.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - 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.
  - Install-script risk not yet assessed.
  - 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.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license.
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 886 tokens (~88/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 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: 2 categories.** Categories scored 0 because we could not verify them: 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 CyberQP MCP server?

CyberQP runs locally as a container image, launched with docker run --rm -i ghcr.io/wyre-ai/cyberqp-mcp:v1.0.0. 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-cyberqp-mcp -- docker run --rm -i ghcr.io/wyre-ai/cyberqp-mcp:v1.0.0
```

### Cursor

```json
{
  "mcpServers": {
    "wyre-ai-cyberqp-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/cyberqp-mcp:v1.0.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "wyre-ai-cyberqp-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/cyberqp-mcp:v1.0.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add wyre-ai-cyberqp-mcp -- docker run --rm -i ghcr.io/wyre-ai/cyberqp-mcp:v1.0.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-ai-cyberqp-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/cyberqp-mcp:v1.0.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  wyre-ai-cyberqp-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/wyre-ai/cyberqp-mcp:v1.0.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "wyre-ai-cyberqp-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/cyberqp-mcp:v1.0.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "wyre-ai-cyberqp-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/cyberqp-mcp:v1.0.0"
      ]
    }
  }
}
```

## 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-20 (score 39)

First indexed and scored.

## MCP tools (10)

### `cyberqp_list_customers` (~105 tokens)

List customers visible to the authenticated CyberQP technician account, filterable by directory type and name. Metadata only (customer id, name, attributes) - never returns account passwords or OTP codes.

Input parameters:

- `directoryType` (string, required): Directory type to filter customers by.
- `limit` (number): Number of items per page. Defaults to 25.
- `name` (string): Filter by customer name.
- `page` (number): Page number. Defaults to 1.

### `cyberqp_get_customer_accounts` (~116 tokens)

List account METADATA for a customer (id, username, type, status) - never returns passwords or OTP codes. Optionally filter by account type (enduser/admin/service/jit).

Input parameters:

- `accountType` (string): Filter accounts by type.
- `cursor` (string): Opaque cursor from a previous response, for cursor-based pagination.
- `id` (string, required): Customer ID.
- `limit` (number): Number of items per page.
- `page` (number): Page number (1-based, offset pagination).

### `cyberqp_get_customer_accounts_count` (~39 tokens)

Get counts of each account type (enduser/admin/service/jit) for a customer.

Input parameters:

- `id` (string, required): Customer ID.

### `cyberqp_get_events` (~224 tokens)

Get the tenant's event log (technician/account activity, e.g. self-serve resets, admin actions), filterable by customer, account, event type, status, and date range. Never returns account passwords or OTP codes.

Input parameters:

- `accountId` (string): Filter events by account ID.
- `cursor` (string): Opaque cursor from a previous response, for cursor-based pagination.
- `customerId` (string): Filter events by customer ID.
- `endDate` (string): Only return events created at or before this ISO 8601 date.
- `eventType` (string): Filter by event type (e.g. SELF-SERVE, ACCOUNT-MANAGEMENT-END-USER). Call cyberqp_get_event_types for the full, current set of values.
- `limit` (number): Number of items per page.
- `page` (number): Page number (1-based, offset pagination).
- `startDate` (string): Only return events created at or after this ISO 8601 date.
- `status` (string): Filter by event outcome.

### `cyberqp_get_event_types` (~30 tokens)

Get the full set of event-type values usable in cyberqp_get_events' eventType filter.

### `cyberqp_get_tenant_company_data` (~31 tokens)

Get the authenticated tenant's own company profile (name, address, timezone, contact phone).

### `cyberqp_get_jit_policies` (~67 tokens)

Get the configured JIT policy (approval requirements, max session duration) for a customer + account type. Policy configuration only - never returns credential material.

Input parameters:

- `accountType` (string, required): Account type the policy applies to.
- `customerId` (string, required): Customer ID.

### `cyberqp_get_customer_jit_status` (~109 tokens)

Get JIT account status (existence, enabled/disabled state, metadata) for a specific customer. Never returns a password or OTP code - use this to check the current state of JIT accounts, not to retrieve credentials.

Input parameters:

- `customerId` (string, required): Customer ID.
- `limit` (number): Number of items per page.
- `page` (number): Page number (1-based).
- `searchText` (string): Optional search text to filter accounts by username.

### `cyberqp_check_jit_account_exists` (~82 tokens)

Check whether a JIT account exists for a customer + directory type (existence check only - returns account metadata if present, never a password or OTP code).

Input parameters:

- `agentId` (string): Agent ID, required for LOCAL accounts.
- `customerId` (string, required): Customer ID.
- `userType` (string, required): Directory type to check.

### `cyberqp_get_tenant_jit_status` (~83 tokens)

Get JIT account status (existence, enabled/disabled state, metadata) across the entire tenant. Never returns a password or OTP code.

Input parameters:

- `limit` (number): Number of items per page.
- `page` (number): Page number (1-based).
- `searchText` (string): Optional search text to filter accounts by username.

## Diagnostics

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

## Score history

- 2026-09-20: 39

## Common questions

### What is the CyberQP MCP server?

CyberQP is an MCP server listed in the public MCP registry as io.github.WYRE-AI/cyberqp-mcp. MCP server for CyberQP's privileged access management API. This page covers its container image (ghcr.io/wyre-ai/cyberqp-mcp:v1.0.0).

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

CyberQP scores 39 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 CyberQP MCP server expose?

CyberQP exposes 10 tools: cyberqp_list_customers, cyberqp_get_customer_accounts, cyberqp_get_customer_accounts_count, cyberqp_get_events, cyberqp_get_event_types, and 5 more. Their descriptions and schemas cost roughly 886 tokens of context every time the server is loaded.

### Is the CyberQP MCP server still maintained?

CyberQP 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 CyberQP MCP server under?

CyberQP declares the NOASSERTION licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

## Links

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