DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to generate an authenticator code locally for your own account with MCP Server

Compute a time-based one-time code on your machine using the totp_code tool.

Authorization notice. MCP Server is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Credentials. The authenticator secret grants access to the account, so it must belong to an account the operator controls and must be stored securely.

Who it is forA developer whose agent must log into an account the developer owns and that asks for an authenticator code.

The problemThe agent needs the current six-digit style time-based code and must compute it without sending the secret elsewhere.

The outcomeThe agent receives an authenticator code computed locally by RFC 6238.

What you need first

  • An SV Number account created at https://sms-verification-number.com/en/register/
  • An API key from https://sms-verification-number.com/en/user/profile/
  • A funded account balance, since the README says there is no free tier
  • An MCP-capable agent such as Claude Code, Codex, Cursor or Claude Desktop

Steps

  1. Add the server with claude mcp add sv-number --env SVN_API_KEY=your_key_here -- npx -y sv-number-mcp.
  2. Store the authenticator secret for your own account in a location the agent can read, and keep it out of logs. (inferred, check the README)
  3. Call totp_code with that secret to get the current code.
  4. Enter the code into the login flow within its validity window.

Prompt for your agent

Using the sv-number/mcp-server totp_code tool, compute the current authenticator code for <account name> from its secret. Expected output: the current time-based code computed locally by RFC 6238. Verify that the secret is not echoed in the response or in any log before you use the code.

Caveat. The README describes totp_code as local computation, but it does not describe how the secret should be supplied, so check the tool schema before storing any secret.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page