CyberQP
OCI · GHCR.IO/WYRE-AI/CYBERQP-MCP
MCP server for CyberQP's privileged access management API.
Available components
Last scanned (19 hours ago)
Scores higher than 56% 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 & Transparency32
- 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
- License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 886 tokens (~88/item across 10 items; 10 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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.07 ▲ functional
- 15 Oct 26 +33
- 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 Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 14 Oct 26 6
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 18 Oct 2026 · Analysed oci/ghcr.io/wyre-ai/cyberqp-mcp@v1.0.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 →
cyberqp_check_jit_account_exists ~82
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).
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | – | Agent ID, required for LOCAL accounts. |
| customerId | string | yes | Customer ID. |
| userType | string | yes | Directory type to check. |
No output schema declared.
No examples provided.
cyberqp_get_customer_accounts ~116
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).
| Name | Type | Req | Description |
|---|---|---|---|
| accountType | string | – | Filter accounts by type. |
| cursor | string | – | Opaque cursor from a previous response, for cursor-based pagination. |
| id | string | yes | Customer ID. |
| limit | number | – | Number of items per page. |
| page | number | – | Page number (1-based, offset pagination). |
No output schema declared.
No examples provided.
cyberqp_get_customer_accounts_count ~39
Get counts of each account type (enduser/admin/service/jit) for a customer.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Customer ID. |
No output schema declared.
No examples provided.
cyberqp_get_customer_jit_status ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customerId | string | yes | 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. |
No output schema declared.
No examples provided.
cyberqp_get_event_types ~30
Get the full set of event-type values usable in cyberqp_get_events' eventType filter.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cyberqp_get_events ~224
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
cyberqp_get_jit_policies ~67
Get the configured JIT policy (approval requirements, max session duration) for a customer + account type. Policy configuration only - never returns credential material.
| Name | Type | Req | Description |
|---|---|---|---|
| accountType | string | yes | Account type the policy applies to. |
| customerId | string | yes | Customer ID. |
No output schema declared.
No examples provided.
cyberqp_get_tenant_company_data ~31
Get the authenticated tenant's own company profile (name, address, timezone, contact phone).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cyberqp_get_tenant_jit_status ~83
Get JIT account status (existence, enabled/disabled state, metadata) across the entire tenant. Never returns a password or OTP code.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of items per page. |
| page | number | – | Page number (1-based). |
| searchText | string | – | Optional search text to filter accounts by username. |
No output schema declared.
No examples provided.
cyberqp_list_customers ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| directoryType | string | yes | 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. |
No output schema declared.
No examples provided.
How do I install the CyberQP MCP server?
CyberQP runs locally as a container image, launched with docker run --rm -i -e CYBERQP_ACCESS_TOKEN -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/cyberqp-mcp:v1.0.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/cyberqp-mcp
claude mcp add wyre-ai-cyberqp-mcp -- docker run --rm -i -e CYBERQP_ACCESS_TOKEN -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/cyberqp-mcp:v1.0.1
This image reads CYBERQP_ACCESS_TOKEN, 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 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).
Is the CyberQP MCP server safe to use?
CyberQP scores 40 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 18 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 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.