Access control for AI agents and MCP servers: allow, hold for approval, or block each tool call
Nothing to run from here
Cisco Duo 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.
22
tools declared
—
trust score
local
runs on your machine
—
calls last 7d
What it does
MCP server for Cisco Duo's identity/MFA administration API.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'DUO_IKEY=${DUO_IKEY}' --env 'DUO_SKEY=${DUO_SKEY}' --env 'DUO_API_HOST=${DUO_API_HOST}' --transport stdio wyre-ai-cisco-duo-mcp '--' docker run -i --rm --platform linux/amd64 -e DUO_IKEY -e DUO_SKEY -e DUO_API_HOST ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.1
# 2 — ask your agent for something these tools do
# duo_check_credentials, duo_list_groups, duo_get_group and 19 more
It needs DUO_IKEY, DUO_SKEY, DUO_API_HOST: this reads them from your environment, so export them first.
Cisco Duo 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 87 servers
WYRE-AI87 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 Cisco Duo 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 (MCP_TRANSPORT, 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 DUO_IKEY (Duo integration key (Basic-auth username for the v5 signed-request scheme). Not secret on its own, but paired with DUO_SKEY it authenticates as this integration), DUO_SKEY (Duo secret key - HMAC-SHA512 signing key for every request. Bearer-equivalent for this integration's admin scope), DUO_API_HOST (This account's Duo API hostname, e.g. api-xxxxxxxx.duosecurity.com) from your environment each time it starts the server, so the value stays out of its config: export them in your shell profile (macOS, Linux), or run setx DUO_IKEY …, setx DUO_SKEY …, setx DUO_API_HOST … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'DUO_IKEY=${DUO_IKEY}' --env 'DUO_SKEY=${DUO_SKEY}' --env 'DUO_API_HOST=${DUO_API_HOST}' --transport stdio wyre-ai-cisco-duo-mcp '--' docker run -i --rm --platform linux/amd64 -e DUO_IKEY -e DUO_SKEY -e DUO_API_HOST ghcr.io/wyre-ai/cisco-duo-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: DUO_IKEY — Duo integration key (Basic-auth username for the v5 signed-request scheme). Not secret on its own, but paired with DUO_SKEY it authenticates as this integration.; DUO_SKEY — Duo secret key - HMAC-SHA512 signing key for every request. Bearer-equivalent for this integration's admin scope.; DUO_API_HOST — This account's Duo API hostname, e.g. api-xxxxxxxx.duosecurity.com.. You set them 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
22 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Validate that the configured Duo credentials (ikey/skey/api host) are correct and the Auth API is reachable. Side-effect-free - does not initiate any MFA transaction.
No parameter schema on file.
List groups in the Duo account (group_id, name, description, status).
No parameter schema on file.
Get full detail for a single group by group_id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| groupId | string | yes | Duo group_id. |
List the users belonging to a group.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| groupId | string | yes | Duo group_id. |
List integrations configured in the Duo account (integration_key, name, type, status). Metadata only - secret keys are stripped before this tool ever returns a response.
No parameter schema on file.
Get full metadata for a single integration by integration_key. Metadata only - secret keys are stripped before this tool ever returns a response.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| integrationKey | string | yes | Duo integration_key. |
Get the authentication log (v2) - every MFA authentication event, filterable by time range. mintime/maxtime are Unix epoch milliseconds. Paginate with next_offset (pass back the comma-joined pair from the previous response's metadata.next_offset).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mintime | number | yes | Only return events at or after this Unix epoch millisecond timestamp. Required. |
| maxtime | number | no | Only return events at or before this Unix epoch millisecond timestamp. |
| limit | number | no | Max results per page (Duo default 100, max 1000). |
| next_offset | string | no | Pagination cursor from a previous response. |
| sort | string | no | Sort order by timestamp. |
Get the administrator log (v1) - actions taken by Duo administrators in this account.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mintime | number | no | Only return events at or after this Unix epoch second timestamp. |
Get the telephony log (v2) - phone call/SMS credit usage events. Paginate with next_offset (pass back the comma-joined pair from the previous response's metadata.next_offset).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mintime | number | no | Only return events at or after this Unix epoch millisecond timestamp. |
| maxtime | number | no | Only return events at or before this Unix epoch millisecond timestamp. |
| limit | number | no | Max results per page. |
| next_offset | string | no | Pagination cursor from a previous response. |
List phones in the Duo account, optionally filtered by number/extension. Returns phone metadata (phone_id, number, platform/OS, type - PII).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| number | string | no | Filter by exact phone number. |
| extension | string | no | Filter by extension. |
Get full detail for a single phone by phone_id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| phoneId | string | yes | Duo phone_id. |
List hardware tokens (HOTP/TOTP/YubiKey) in the Duo account, optionally filtered by type/serial. Never returns a seed/secret.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | Filter by token type. |
| serial | string | no | Filter by serial number. |
Get full detail for a single hardware token by token_id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tokenId | string | yes | Duo hardware token_id. |
List Duo Desktop tokens (platform, name, status).
No parameter schema on file.
Get full detail for a single Duo Desktop token by desktoptoken_id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| desktoptokenId | string | yes | Duo desktoptoken_id. |
List users in the Duo account, optionally filtered by exact username. Returns user metadata (user_id, username, email, status, realname, phone/created timestamps) - PII, classified isAdmin.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| username | string | no | Filter by exact username match. |
Get full detail for a single user by user_id, including status and enrolled-factor summary.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| userId | string | yes | Duo user_id. |
List the groups a user belongs to.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| userId | string | yes | Duo user_id. |
List the phones enrolled to a user (number, platform/OS, capabilities - PII).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| userId | string | yes | Duo user_id. |
List the hardware tokens enrolled to a user (type, serial - never the token's secret seed, which is stripped).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| userId | string | yes | Duo user_id. |
List the WebAuthn credentials (security keys, platform authenticators) enrolled to a user. Never returns private key material.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| userId | string | yes | Duo user_id. |
List the legacy U2F security keys enrolled to a user. Never returns private key material.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| userId | string | yes | Duo user_id. |
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 Cisco Duo 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 1.0.1.
1.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 Cisco Duo 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.