Cisco Duo
OCI · GHCR.IO/WYRE-AI/CISCO-DUO-MCP
MCP server for Cisco Duo's identity/MFA administration API.
Available components
Last scanned (8 hours ago)
Scores higher than 38% 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 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1573 tokens (~71/item across 22 items; 22 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 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 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 22 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.
- 4 Nov 26 +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.
- 3 Nov 26 37
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 5 Nov 2026 · Analysed oci/ghcr.io/wyre-ai/cisco-duo-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 →
duo_check_credentials ~42
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
duo_get_administrator_log ~48
Get the administrator log (v1) - actions taken by Duo administrators in this account.
| Name | Type | Req | Description |
|---|---|---|---|
| mintime | number | – | Only return events at or after this Unix epoch second timestamp. |
No output schema declared.
No examples provided.
duo_get_authentication_log ~154
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
duo_get_desktop_token ~44
Get full detail for a single Duo Desktop token by desktoptoken_id.
| Name | Type | Req | Description |
|---|---|---|---|
| desktoptokenId | string | yes | Duo desktoptoken_id. |
No output schema declared.
No examples provided.
duo_get_group ~31
Get full detail for a single group by group_id.
| Name | Type | Req | Description |
|---|---|---|---|
| groupId | string | yes | Duo group_id. |
No output schema declared.
No examples provided.
duo_get_hardware_token ~35
Get full detail for a single hardware token by token_id.
| Name | Type | Req | Description |
|---|---|---|---|
| tokenId | string | yes | Duo hardware token_id. |
No output schema declared.
No examples provided.
duo_get_integration ~47
Get full metadata for a single integration by integration_key. Metadata only - secret keys are stripped before this tool ever returns a response.
| Name | Type | Req | Description |
|---|---|---|---|
| integrationKey | string | yes | Duo integration_key. |
No output schema declared.
No examples provided.
duo_get_phone ~31
Get full detail for a single phone by phone_id.
| Name | Type | Req | Description |
|---|---|---|---|
| phoneId | string | yes | Duo phone_id. |
No output schema declared.
No examples provided.
duo_get_telephony_log ~118
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
duo_get_user ~38
Get full detail for a single user by user_id, including status and enrolled-factor summary.
| Name | Type | Req | Description |
|---|---|---|---|
| userId | string | yes | Duo user_id. |
No output schema declared.
No examples provided.
duo_list_desktop_tokens ~61
List Duo Desktop tokens (platform, name, status).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
duo_list_group_users ~68
List the users belonging to a group.
| Name | Type | Req | Description |
|---|---|---|---|
| groupId | string | yes | 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. |
No output schema declared.
No examples provided.
duo_list_groups ~64
List groups in the Duo account (group_id, name, description, status).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
duo_list_hardware_tokens ~103
List hardware tokens (HOTP/TOTP/YubiKey) in the Duo account, optionally filtered by type/serial. Never returns a seed/secret.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
duo_list_integrations ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
duo_list_phones ~103
List phones in the Duo account, optionally filtered by number/extension. Returns phone metadata (phone_id, number, platform/OS, type - PII).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
duo_list_user_groups ~68
List the groups a user belongs to.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Duo user_id. |
No output schema declared.
No examples provided.
duo_list_user_phones ~80
List the phones enrolled to a user (number, platform/OS, capabilities - PII).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Duo user_id. |
No output schema declared.
No examples provided.
duo_list_user_tokens ~84
List the hardware tokens enrolled to a user (type, serial - never the token's secret seed, which is stripped).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Duo user_id. |
No output schema declared.
No examples provided.
duo_list_user_u2f_tokens ~82
List the legacy U2F security keys enrolled to a user. Never returns private key material.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Duo user_id. |
No output schema declared.
No examples provided.
duo_list_user_webauthn_credentials ~89
List the WebAuthn credentials (security keys, platform authenticators) enrolled to a user. Never returns private key material.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Duo user_id. |
No output schema declared.
No examples provided.
duo_list_users ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
oci · ghcr.io/wyre-ai/cisco-duo-mcp
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.
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.