Access control for AI agents and MCP servers: allow, hold for approval, or block each tool call
Nothing to run from here
CyberQP is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
10
tools declared
—
trust score
local
runs on your machine
—
calls last 7d
What it does
MCP server for CyberQP's privileged access management API.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'CYBERQP_ACCESS_TOKEN=${CYBERQP_ACCESS_TOKEN}' --transport stdio cyberqp-mcp '--' docker run -i --rm -e MCP_TRANSPORT=stdio -e CYBERQP_ACCESS_TOKEN ghcr.io/wyre-ai/cyberqp-mcp:v1.0.1
# 2 — ask your agent for something these tools do
# cyberqp_list_customers, cyberqp_get_customer_accounts, cyberqp_get_customer_accounts_count and 7 more
It needs CYBERQP_ACCESS_TOKEN: this reads it from your environment, so export it first.
CyberQP costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
WAAll 82 servers
WYRE-AI82 servers
14 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts CyberQP as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It has not been scanned here, so read the surface, and its source, before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Docker installed and running. Only the required variables are passed into the container. To set an optional one (AUTH_MODE, LOG_LEVEL), add -e NAME before the image name and give it a value in the entry’s env: an unset -e would clear the default the image sets. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads CYBERQP_ACCESS_TOKEN (CyberQP OAuth2 access token (authorization_code flow, offline_access scope). Exchanged and refreshed upstream of this server - it only ever holds a live bearer) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx CYBERQP_ACCESS_TOKEN … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'CYBERQP_ACCESS_TOKEN=${CYBERQP_ACCESS_TOKEN}' --transport stdio cyberqp-mcp '--' docker run -i --rm -e MCP_TRANSPORT=stdio -e CYBERQP_ACCESS_TOKEN ghcr.io/wyre-ai/cyberqp-mcp:v1.0.1Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own image: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: CYBERQP_ACCESS_TOKEN — CyberQP OAuth2 access token (authorization_code flow, offline_access scope). Exchanged and refreshed upstream of this server - it only ever holds a live bearer. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
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).
No parameter schema on file.
Get counts of each account type (enduser/admin/service/jit) for a customer.
No parameter schema on file.
Get the tenant
No parameter schema on file.
Get the full set of event-type values usable in cyberqp_get_events\
No parameter schema on file.
Get the configured JIT policy (approval requirements, max session duration) for a customer + account type. Policy configuration only - never returns credential material.
No parameter schema on file.
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.
No parameter schema on file.
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).
No parameter schema on file.
Get JIT account status (existence, enabled/disabled state, metadata) across the entire tenant. Never returns a password or OTP code.
No parameter schema on file.
Get the authenticated tenant
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source is public; its licence metadata reads NOASSERTION rather than naming a licence
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install CyberQP or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing ships as a container image. The scanner reads packages on npm and PyPI and public source; an image is neither, so there is no grade here — not a withheld one, an unmeasured one.
Release history
It installs from a container image rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is v1.0.1.
v1.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish CyberQP can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.