← Index

Cisco Duo MCP

io.github.Servosity/cisco-duo-mcpv0.1.1Other

Fix Duo MFA lockouts and see every MSP subaccount at once, from your AI agent.

The current version, v0.1.1, was published to the official MCP registry on 2026-10-16. It is distributed through a declared package, filed under Other by this index, and declares 9 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using Cisco Duo MCP in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
REVIEWstatus: PARTIALfresh until 2026-11-15 06:02 UTC
screened 2026-10-16tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidence“Tool fixes Duo MFA lockouts and lists MSP subaccounts.”via static_description

Limits of this verdict
  • - Semantic screen only - the deterministic conformance probe has not run on this server
  • - Confidence is reported but not yet calibrated (v1)
  • - Screen reads the tool description, not the live behavior
  • - advisory
  • - registry description only no input schema
  • - screen model 8b
  • - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Test a description on the public screen → It is a separate check from the verdict above, so the two can differ.

That verdict was true at screening time (snapshot 2026-10-19).

Contracts can change after screening, with no version bump. The gate pins Cisco Duo MCP’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Cite this record

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

Markdown
[Independent trust record for Cisco Duo MCP](https://mcpindex.ai/server/io-github-servosity-cisco-duo-mcp) - screening verdict, registry provenance, and contract drift monitoring.
HTML
<a href="https://mcpindex.ai/server/io-github-servosity-cisco-duo-mcp">Independent trust record for Cisco Duo MCP</a> - screening verdict, registry provenance, and contract drift monitoring.
Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown
[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-servosity-cisco-duo-mcp)](https://mcpindex.ai/server/io-github-servosity-cisco-duo-mcp)
HTML
<a href="https://mcpindex.ai/server/io-github-servosity-cisco-duo-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-servosity-cisco-duo-mcp" alt="mcpindex verdict" height="20" /></a>
Environment variables
CISCO_DUO_API_HOST
required

Your Duo API hostname, e.g. api-XXXXXXXX.duosecurity.com (Duo Admin Panel > Applications > your Admin API application). For an MSP, use the parent account's hostname.

CISCO_DUO_IKEY
requiredsecret

Admin API integration key (ikey) from the same Admin API application.

CISCO_DUO_SKEY
requiredsecret

Admin API secret key (skey). Used only to sign each request; it is never sent to Duo.

CISCO_DUO_ACCOUNT_ID

Default customer subaccount for every call (account ID, or exact name from accounts list); a tool call that names its own account-id overrides it. Leave blank to act on the account the keys belong to; the fleet tools always cover every subaccount.

CISCO_DUO_MCP_READ_ONLY

Set to 1 for a read-only server: lockout fix, phone-swap, enrollment chase, sync, import and export are hidden, and the API execute tool refuses every non-GET call. Leave blank for the full tool set.

CISCO_DUO_BASE_URL

Overrides the full API root (for a test server). Leave blank; CISCO_DUO_API_HOST is the normal setting.

CISCO_DUO_MCP_HTTP_TOKEN
secret

Bearer token that cisco-duo-mcp --transport http requires from every HTTP client (Authorization: Bearer). Leave blank for the default stdio transport, which Claude Desktop uses and which never reads it.

CISCO_DUO_USER_AGENT

Overrides the User-Agent the CLI sends on Duo requests. Leave blank to use the CLI's own built-in User-Agent.

PRINTING_PRESS_CLIENT_PROFILE

Binds this MCP server to one tenant-gated client profile. Leave blank unless you configured client profiles.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
20
installability
25
documentation
15
stability
5
Alternatives in Other