Skip to main content
Glama
andreax79

otp-mcp-server

by andreax79
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OTP_MCP_SERVER_DBNoPath to the tokens database file
OTP_MCP_SERVER_HOSTNoHost to bind the server to
OTP_MCP_SERVER_PATHNoPath for HTTP transport
OTP_MCP_SERVER_PORTNoPort to bind the server to
OTP_MCP_SERVER_LOG_LEVELNoLogging level
OTP_MCP_SERVER_TRANSPORTNoTransport protocol to use

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
list_otp_tokensA

Returns the list of OTP tokens. Use this to understand which tokens are available before trying to generate code.

get_detailsC
Get the details of all the OTP tokens matching the pattern

Args:
    pattern: Token pattern (part of the name or token number)
calculate_otp_codesC
Calculate the OTP code for all tokens matching the pattern.

Args:
    pattern: Token pattern (part of the name or token number)
add_tokenC
Add a new OTP token.

Args:
    secret: Base32 encoded secret key
    issuer: Issuer of the OTP token
    account: Accout for the OTP token
    type: Type of the OTP token (TOTP or HOTP) (default is TOTP)
    algorithm: Hashing algorithm to use (SHA1, SHA256, SHA512, MD5) (default is SHA1)
    counter: Counter value for HOTP tokens (default is 0)
    digits: Number of digits in the OTP code (default is 6)
    period: Time period for TOTP tokens in seconds (default is 30)
delete_tokenC
Delete an OTP token matching the pattern.

Args:
    pattern: Token pattern (part of the name or token number)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
list_tokensProvides OTP tokens as JSON.
list_token_typesProvides the list of OTP token types.
list_algorithmsProvides the list of the supported OTP algorithms.
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: add_token creates tokens, calculate_otp_codes generates codes, delete_token removes tokens, get_details retrieves token metadata, and list_otp_tokens enumerates available tokens. There is no functional overlap between these operations.

Naming Consistency4/5

Four tools follow a consistent verb_noun pattern (add_token, delete_token, get_details, list_otp_tokens), but calculate_otp_codes uses a verb_object format that slightly deviates from the pattern. The naming is still highly readable and predictable.

Tool Count5/5

With 5 tools, this server is well-scoped for OTP management. It covers the essential CRUD operations (add, delete, list, get details) plus code calculation, which is the core functionality. No tool feels redundant or missing for the domain.

Completeness5/5

The toolset provides complete coverage for OTP token management: creation (add_token), retrieval (list_otp_tokens, get_details), usage (calculate_otp_codes), and deletion (delete_token). There are no obvious gaps in the lifecycle or functionality for this domain.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources