# Cisco Duo (oci · ghcr.io/wyre-ai/cisco-duo-mcp)

MCP server for Cisco Duo's identity/MFA administration API.

- Trust score: 38/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- oci · `ghcr.io/wyre-ai/cisco-duo-mcp`: 38/100 (this document), [markdown](https://verifymcp.io/servers/wyre-ai-cisco-duo-mcp/ghcr-io-wyre-ai-cisco-duo-mcp.md), [page](https://verifymcp.io/servers/wyre-ai-cisco-duo-mcp/ghcr-io-wyre-ai-cisco-duo-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/cisco-duo-mcp`
- Version: `v1.0.1`
- 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-11-05.

- **Supply Chain Security**: 0/100
  - 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.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **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 13 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1573 tokens (~71/item across 22 items; 22 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 22 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 22 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: 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.

## Install

### How do I install the Cisco Duo MCP server?

Cisco Duo runs locally as a container image, launched with docker run --rm -i -e DUO_IKEY -e DUO_SKEY -e DUO_API_HOST -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/cisco-duo-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.

### Claude

```bash
claude mcp add wyre-ai-cisco-duo-mcp -- docker run --rm -i -e DUO_IKEY -e DUO_SKEY -e DUO_API_HOST -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.1
```

This image reads DUO_IKEY, DUO_SKEY, DUO_API_HOST, 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.

### Cursor

```json
{
  "mcpServers": {
    "wyre-ai-cisco-duo-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "DUO_IKEY",
        "-e",
        "DUO_SKEY",
        "-e",
        "DUO_API_HOST",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.1"
      ]
    }
  }
}
```

This image reads DUO_IKEY, DUO_SKEY, DUO_API_HOST, 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.

### VS Code

```json
{
  "servers": {
    "wyre-ai-cisco-duo-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "DUO_IKEY",
        "-e",
        "DUO_SKEY",
        "-e",
        "DUO_API_HOST",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.1"
      ]
    }
  }
}
```

This image reads DUO_IKEY, DUO_SKEY, DUO_API_HOST, 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.

### Codex

```bash
codex mcp add wyre-ai-cisco-duo-mcp -- docker run --rm -i -e DUO_IKEY -e DUO_SKEY -e DUO_API_HOST -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.1
```

This image reads DUO_IKEY, DUO_SKEY, DUO_API_HOST, 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.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-ai-cisco-duo-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "DUO_IKEY",
        "-e",
        "DUO_SKEY",
        "-e",
        "DUO_API_HOST",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.1"
      ],
      "enabled": true
    }
  }
}
```

This image reads DUO_IKEY, DUO_SKEY, DUO_API_HOST, 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.

### Hermes

```yaml
mcp_servers:
  wyre-ai-cisco-duo-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "DUO_IKEY", "-e", "DUO_SKEY", "-e", "DUO_API_HOST", "-e", "MCP_TRANSPORT", "-e", "AUTH_MODE", "-e", "LOG_LEVEL", "ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.1"]
```

This image reads DUO_IKEY, DUO_SKEY, DUO_API_HOST, 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.

### Netclaw

```json
{
  "McpServers": {
    "wyre-ai-cisco-duo-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "DUO_IKEY",
        "-e",
        "DUO_SKEY",
        "-e",
        "DUO_API_HOST",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.1"
      ]
    }
  }
}
```

This image reads DUO_IKEY, DUO_SKEY, DUO_API_HOST, 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.

### Other

```json
{
  "mcpServers": {
    "wyre-ai-cisco-duo-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "DUO_IKEY",
        "-e",
        "DUO_SKEY",
        "-e",
        "DUO_API_HOST",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/cisco-duo-mcp:v1.0.1"
      ]
    }
  }
}
```

This image reads DUO_IKEY, DUO_SKEY, DUO_API_HOST, 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.

## 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-11-04 (score 38, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 37)

First indexed and scored.

## MCP tools (22)

### `duo_list_users` (~102 tokens)

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.

Input parameters:

- `limit` (number): Number of items per page (Duo default/max vary by endpoint).
- `offset` (number): Offset into the result set, for paging past the first page.
- `username` (string): Filter by exact username match.

### `duo_get_user` (~38 tokens)

Get full detail for a single user by user_id, including status and enrolled-factor summary.

Input parameters:

- `userId` (string, required): Duo user_id.

### `duo_list_user_groups` (~68 tokens)

List the groups a user belongs to.

Input parameters:

- `limit` (number): Number of items per page (Duo default/max vary by endpoint).
- `offset` (number): Offset into the result set, for paging past the first page.
- `userId` (string, required): Duo user_id.

### `duo_list_user_phones` (~80 tokens)

List the phones enrolled to a user (number, platform/OS, capabilities - PII).

Input parameters:

- `limit` (number): Number of items per page (Duo default/max vary by endpoint).
- `offset` (number): Offset into the result set, for paging past the first page.
- `userId` (string, required): Duo user_id.

### `duo_list_user_tokens` (~84 tokens)

List the hardware tokens enrolled to a user (type, serial - never the token's secret seed, which is stripped).

Input parameters:

- `limit` (number): Number of items per page (Duo default/max vary by endpoint).
- `offset` (number): Offset into the result set, for paging past the first page.
- `userId` (string, required): Duo user_id.

### `duo_list_user_webauthn_credentials` (~89 tokens)

List the WebAuthn credentials (security keys, platform authenticators) enrolled to a user. Never returns private key material.

Input parameters:

- `limit` (number): Number of items per page (Duo default/max vary by endpoint).
- `offset` (number): Offset into the result set, for paging past the first page.
- `userId` (string, required): Duo user_id.

### `duo_list_user_u2f_tokens` (~82 tokens)

List the legacy U2F security keys enrolled to a user. Never returns private key material.

Input parameters:

- `limit` (number): Number of items per page (Duo default/max vary by endpoint).
- `offset` (number): Offset into the result set, for paging past the first page.
- `userId` (string, required): Duo user_id.

### `duo_list_phones` (~103 tokens)

List phones in the Duo account, optionally filtered by number/extension. Returns phone metadata (phone_id, number, platform/OS, type - PII).

Input parameters:

- `extension` (string): Filter by extension.
- `limit` (number): Number of items per page (Duo default/max vary by endpoint).
- `number` (string): Filter by exact phone number.
- `offset` (number): Offset into the result set, for paging past the first page.

### `duo_get_phone` (~31 tokens)

Get full detail for a single phone by phone_id.

Input parameters:

- `phoneId` (string, required): Duo phone_id.

### `duo_list_hardware_tokens` (~103 tokens)

List hardware tokens (HOTP/TOTP/YubiKey) in the Duo account, optionally filtered by type/serial. Never returns a seed/secret.

Input parameters:

- `limit` (number): Number of items per page (Duo default/max vary by endpoint).
- `offset` (number): Offset into the result set, for paging past the first page.
- `serial` (string): Filter by serial number.
- `type` (string): Filter by token type.

### `duo_get_hardware_token` (~35 tokens)

Get full detail for a single hardware token by token_id.

Input parameters:

- `tokenId` (string, required): Duo hardware token_id.

### `duo_list_desktop_tokens` (~61 tokens)

List Duo Desktop tokens (platform, name, status).

Input parameters:

- `limit` (number): Number of items per page (Duo default/max vary by endpoint).
- `offset` (number): Offset into the result set, for paging past the first page.

### `duo_get_desktop_token` (~44 tokens)

Get full detail for a single Duo Desktop token by desktoptoken_id.

Input parameters:

- `desktoptokenId` (string, required): Duo desktoptoken_id.

### `duo_list_groups` (~64 tokens)

List groups in the Duo account (group_id, name, description, status).

Input parameters:

- `limit` (number): Number of items per page (Duo default/max vary by endpoint).
- `offset` (number): Offset into the result set, for paging past the first page.

### `duo_get_group` (~31 tokens)

Get full detail for a single group by group_id.

Input parameters:

- `groupId` (string, required): Duo group_id.

### `duo_list_group_users` (~68 tokens)

List the users belonging to a group.

Input parameters:

- `groupId` (string, required): Duo group_id.
- `limit` (number): Number of items per page (Duo default/max vary by endpoint).
- `offset` (number): Offset into the result set, for paging past the first page.

### `duo_list_integrations` (~81 tokens)

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.

Input parameters:

- `limit` (number): Number of items per page (Duo default/max vary by endpoint).
- `offset` (number): Offset into the result set, for paging past the first page.

### `duo_get_integration` (~47 tokens)

Get full metadata for a single integration by integration_key. Metadata only - secret keys are stripped before this tool ever returns a response.

Input parameters:

- `integrationKey` (string, required): Duo integration_key.

### `duo_get_authentication_log` (~154 tokens)

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).

Input parameters:

- `limit` (number): Max results per page (Duo default 100, max 1000).
- `maxtime` (number): Only return events at or before this Unix epoch millisecond timestamp.
- `mintime` (number, required): Only return events at or after this Unix epoch millisecond timestamp. Required.
- `next_offset` (string): Pagination cursor from a previous response.
- `sort` (string): Sort order by timestamp.

### `duo_get_administrator_log` (~48 tokens)

Get the administrator log (v1) - actions taken by Duo administrators in this account.

Input parameters:

- `mintime` (number): Only return events at or after this Unix epoch second timestamp.

### `duo_get_telephony_log` (~118 tokens)

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).

Input parameters:

- `limit` (number): Max results per page.
- `maxtime` (number): Only return events at or before this Unix epoch millisecond timestamp.
- `mintime` (number): Only return events at or after this Unix epoch millisecond timestamp.
- `next_offset` (string): Pagination cursor from a previous response.

### `duo_check_credentials` (~42 tokens)

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.

## Diagnostics

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

## Score history

- 2026-11-05: 38
- 2026-11-04: 38
- 2026-11-03: 37

## Common questions

### What is the Cisco Duo MCP server?

Cisco Duo is an MCP server listed in the public MCP registry as io.github.WYRE-AI/cisco-duo-mcp. MCP server for Cisco Duo's identity/MFA administration API. This page covers its container image (ghcr.io/wyre-ai/cisco-duo-mcp).

### Is the Cisco Duo MCP server safe to use?

Cisco Duo scores 38 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 Cisco Duo MCP server expose?

Cisco Duo exposes 22 tools: duo_list_users, duo_get_user, duo_list_user_groups, duo_list_user_phones, duo_list_user_tokens, and 17 more. Their descriptions and schemas cost roughly 1,573 tokens of context every time the server is loaded.

### Is the Cisco Duo MCP server still maintained?

Cisco Duo is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Cisco Duo MCP server under?

Cisco Duo 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

- GitHub Container Registry: https://ghcr.io/wyre-ai/cisco-duo-mcp
- Repository: https://github.com/WYRE-AI/cisco-duo-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-cisco-duo-mcp/ghcr-io-wyre-ai-cisco-duo-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-cisco-duo-mcp/ghcr-io-wyre-ai-cisco-duo-mcp.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-cisco-duo-mcp/ghcr-io-wyre-ai-cisco-duo-mcp