@ztechlab/mcp-server-yubikey
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YKMAN_PATH | No | Custom path to the ykman executable if not on PATH |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| yubikey-listA | List all connected YubiKeys with serial numbers |
| yubikey-infoA | Get detailed information about a connected YubiKey (serial, firmware, model, interfaces, applications) |
| yubikey-fido-infoB | Get FIDO2 applet status: PIN set, credentials stored, remaining retries |
| yubikey-fido-credentialsA | List FIDO2 resident credentials (passkeys) stored on the YubiKey. Requires PIN. |
| yubikey-otp-infoA | Get OTP slot configuration (Slot 1 and Slot 2 status) |
| yubikey-piv-infoA | Get PIV (smart card) application status: management key type, PIN/PUK retries, certificate slots in use |
| yubikey-piv-keys-infoA | Get private key metadata for a PIV slot: key type, origin (generated vs imported), PIN policy, touch policy |
| yubikey-openpgp-infoA | Get OpenPGP application status: key slots, touch policies, signature count |
| yubikey-fido-fingerprintsA | List enrolled fingerprints on a YubiKey Bio. Requires PIN. |
| yubikey-openpgp-keys-infoA | Get metadata about an OpenPGP key slot: key type, fingerprint, creation date |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool targets a distinct aspect of YubiKey functionality (FIDO, OpenPGP, OTP, PIV, general info), with no overlap. An agent can clearly differentiate them.
All tools follow the pattern 'yubikey-<subsystem>-<descriptor>', with only 'yubikey-list' and 'yubikey-info' being slightly standalone but still predictable.
10 tools cover the major YubiKey subsystems (FIDO, OpenPGP, OTP, PIV, listing, info) without being excessive or insufficient.
The tool set is entirely read-only, providing only info retrieval. Missing write operations (e.g., set PIN, generate keys, delete credentials) is a significant gap for management.