Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

security_totp_qr_generator

Read-only

Build, parse, or generate secrets for otpauth TOTP/HOTP URIs to enrol in two-factor authentication with authenticator apps.

Instructions

2FA TOTP/HOTP otpauth URI Builder and Parser. Build, parse, or seed otpauth:// Key-URI strings for two-factor authentication (RFC 6238 TOTP, RFC 4226 HOTP), compatible with Google Authenticator, Authy, 1Password, Microsoft Authenticator, and Bitwarden. The single operation field selects one of three actions. buildUri assembles an otpauth:// URI from a supplied base32 secret plus issuer/account/algorithm/digits/period (it does NOT invent a secret) and returns app-compatibility warnings. generateSecret returns a fresh random base32 secret (non-deterministic, CSPRNG via random_bytes) of the requested byte length. parseUri decodes an existing otpauth:// URI back into its fields. The QR image itself is rendered client-side in the browser from the returned URI; the server only produces the string and never contacts an external service. Use osint_qr_code_generator for general-purpose QR codes (WiFi, vCard, plain URLs); use this tool only for authenticator-app 2FA enrolment URIs. Read-only, non-destructive, rate-limi

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYesAction to perform: buildUri (assemble an otpauth URI from supplied fields), generateSecret (return a fresh random base32 secret), or parseUri (decode an existing otpauth URI).
typeNobuildUri only. otpauth scheme: time-based (totp) or counter-based (hotp). Determines whether period or counter applies.totp
issuerNobuildUri only. Organisation/service name shown in the authenticator app (e.g. GitHub). Optional but recommended; omitting it triggers a warning.
accountNobuildUri only. Account label shown in the app (e.g. alice@example.com). Required for buildUri.
secretNobuildUri only. Base32-encoded shared secret (RFC 4648 alphabet A-Z 2-7); whitespace stripped and upper-cased. Required for buildUri. Non-base32 input still builds but is flagged in warnings.
algorithmNobuildUri only. HMAC hash. Most apps (notably Google Authenticator) assume SHA1; non-default values trigger a compatibility warning.SHA1
digitsNobuildUri only. Number of code digits. Most apps assume 6.
periodNobuildUri with type totp only. Time step in seconds (RFC 6238). Ignored for hotp.
counterNobuildUri with type hotp only. Initial HOTP counter (RFC 4226). Ignored for totp.
byteCountNogenerateSecret only. Raw random bytes before base32 encoding. RFC 6238 recommends 20 (160 bits) for SHA1.
uriNoparseUri only. An existing otpauth:// URI to decode into component fields.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the operation succeeded.
operationNoThe operation that was executed (buildUri, generateSecret, or parseUri).
resultNoOperation payload. buildUri returns uri/type/issuer/account/secret/algorithm/digits/period/counter/warnings. parseUri returns the same fields minus uri and warnings. generateSecret returns secret/byteCount/bits.
errorNoPresent only on failure: human-readable validation/runtime message.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Description explicitly states 'Read-only, non-destructive' and clarifies that the server only produces the URI string without external service contact, aligning with and adding context to the annotations (readOnlyHint: true, destructiveHint: false).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with front-loaded purpose and clear separation of actions. While slightly verbose, every sentence adds necessary detail and earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (three operations, 11 parameters), the description thoroughly covers each operation's behavior, return values (app-compatibility warnings), and boundaries. The existence of an output schema further reduces need for return value explanation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining operational nuances (e.g., buildUri does not invent a secret, generateSecret uses CSPRNG, parseUri decodes) and flags compatibility warnings. These details enhance understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states '2FA TOTP/HOTP otpauth URI Builder and Parser' and distinguishes from the sibling 'osint_qr_code_generator' by specifying this tool is only for authenticator-app 2FA enrolment URIs. It covers three distinct operations with specific verbs and resources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use this tool vs. the alternative: 'Use osint_qr_code_generator for general-purpose QR codes... use this tool only for authenticator-app 2FA enrolment URIs.' Also details the three sub-actions and their respective contexts.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server