# MyOTP.App (npm · @myotp/mcp)

Send and verify one-time passcodes over SMS, WhatsApp and Telegram.

- Trust score: 87/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `mcp.myotp.app`: 73/100, [markdown](https://verifymcp.io/servers/brntech-myotp/mcp.md), [page](https://verifymcp.io/servers/brntech-myotp/mcp)
- npm · `@myotp/mcp`: 87/100 (this document), [markdown](https://verifymcp.io/servers/brntech-myotp/myotp-mcp.md), [page](https://verifymcp.io/servers/brntech-myotp/myotp-mcp)

## Channel facts

- Registry: `npm`
- Package: `@myotp/mcp`
- Version: `0.1.13`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 39 of 123 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to brntech/myotp-agentkit).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2177 tokens (~217/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the MyOTP.App MCP server?

MyOTP.App runs locally as an npm package, launched with npx -y @myotp/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add brntech-myotp -- npx -y @myotp/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "brntech-myotp": {
      "command": "npx",
      "args": [
        "-y",
        "@myotp/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "brntech-myotp": {
      "command": "npx",
      "args": [
        "-y",
        "@myotp/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add brntech-myotp -- npx -y @myotp/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "brntech-myotp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@myotp/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add brntech-myotp --command npx --arg -y --arg @myotp/mcp
```

### Hermes

```yaml
mcp_servers:
  brntech-myotp:
    command: "npx"
    args: ["-y", "@myotp/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "brntech-myotp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@myotp/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add brntech-myotp -t stdio -c npx -a -y @myotp/mcp
```

### Other

```json
{
  "mcpServers": {
    "brntech-myotp": {
      "command": "npx",
      "args": [
        "-y",
        "@myotp/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 87, 0)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.57 → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.1.12 → 0.1.13

### 2026-09-19 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 85, +2)

- [security improvement] CVE-2026-82417 no longer affects this package
- [security improvement] CVE-2026-82562 no longer affects this package
- [security improvement] Known CVEs: fail → pass

### 2026-09-14 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (10)

### `generate_otp` (~663 tokens)

Send OTP

Send a one-time password (OTP) to a phone number via SMS, WhatsApp, or Telegram. MyOTP.App generates the code, formats the message, picks the best carrier route, and delivers it. Returns a `message_id` (UUID) — keep it; you'll pass it to `verify_otp`, `check_otp_status`, or `extend_otp` later. Each call deducts credits from the account balance; the per-message cost varies by destination country and channel and is returned in the `cost` field. Use this whenever an app needs to verify someone's phone — signup, login 2FA, password reset, transaction confirmation, etc.

Input parameters:

- `brand` (string): Sender brand name shown to the recipient (3-16 alphanumeric characters plus dots). Defaults to the brand registered against the API key, or 'MyOTP.App' if none.
- `channel` (string): Delivery channel. 'sms' (default) works in 190+ countries. 'whatsapp' is best for India/Brazil/Indonesia/Mexico/Nigeria/Turkey. 'telegram' is best for privacy-focused users. Same API for all three.
- `force_send` (boolean): If true, send a new OTP even if one is already active for this phone number. By default the API returns 409 in that case. Use sparingly — repeated sends to the same number can hit carrier-level spam…
- `otp_code` (string): Provide your own pre-generated numeric OTP code (3-8 digits, 4-8 for telegram) instead of letting MyOTP generate one. Useful when you already have a code from another system.
- `otp_length` (integer): Number of digits in the auto-generated OTP. Range 3-8 (4-8 for telegram). Default 6. Requires CUSTOM_OTP_LENGTH entitlement (Business plan or above).
- `otp_validity` (integer): How long the OTP stays valid, in seconds. Range 30-14400 (30-3600 for telegram). Default 300 (5 minutes). Requires CUSTOM_OTP_EXPIRY entitlement (Business plan or above).
- `phone_number` (string, required): Destination phone number in international format with NO leading + or 0. Must be 7-15 digits and start with a non-zero digit. Example: '14155551234' for a US number, '447911123456' for a UK number.
- `return_otp` (boolean): If true, the API response will include the generated OTP code in plain text. Useful for testing or when you want to deliver the OTP via your own channel. Defaults to false. SECURITY: never enable thi…
- `template_order` (integer): Pick a specific message template by its order number (1-99). WhatsApp has four: 12 (English, 5-minute code), 13 (English, 10 minutes), 14 (Spanish es_MX, 5 minutes), 15 (Spanish es_MX, 10 minutes). O…

Output parameters:

- `cost` (number): Credits charged for this send.
- `date_sent` (string): ISO 8601 date-time the OTP was sent.
- `expires_at` (string): ISO 8601 date-time the OTP expires.
- `message` (string): Message describing the status of the request.
- `message_id` (string): ID of the message sent. Pass it to verify_otp, check_otp_status and extend_otp.
- `otp` (string): The OTP value, present only when return_otp was true.
- `status` (string): Always 'accepted' on success; delivery state comes from check_otp_status.

### `verify_otp` (~238 tokens)

Verify OTP

Verify a code submitted by an end user against the OTP MyOTP delivered. Returns `{status: 'success'}` if the code matches and the OTP hasn't expired — at that point the OTP is consumed and cannot be reused. Returns `{status: 'failed', reason: 'invalid' | 'expired' | 'not found'}` otherwise. You MUST pass either `phone_number` or `message_id` to identify which OTP you're verifying against. Call this after collecting the code from the user (login form, signup screen, etc.).

Input parameters:

- `message_id` (string): The UUID returned by `generate_otp`. Provide either this OR `phone_number`. Prefer this when you have it — it disambiguates if the same number got multiple OTPs.
- `otp` (string, required): The OTP code the end user typed in (3-8 numeric digits). This is the code you're trying to verify against what was sent.
- `phone_number` (string): Phone number the OTP was originally sent to, in international format without + or leading 0. Provide either this OR `message_id` — `message_id` is more precise.

Output parameters:

- `message` (string): Message describing the verification result.
- `reason` (string): Why verification failed: 'invalid', 'expired' or 'not found'. Absent on success.
- `status` (string): 'success' when the code matched and the OTP was consumed, otherwise 'failed' (or 'expired').

### `check_otp_status` (~188 tokens)

Check OTP delivery status

Check whether a previously sent OTP is still active and (with DLR_ACCESS entitlement on Enterprise plan) get its delivery status. Returns `is_active` (bool) and `expires_at` (ISO timestamp) on every plan. On Enterprise plans, also returns `DLR`: 'delivered', 'sent', 'read', 'pending', or a failure as `failed.<reason>` (on WhatsApp, `failed.Undeliverable` means the number cannot receive WhatsApp and `failed.Provider` means a retry is worth it). Useful when an end user reports they didn't receive the code — you can confirm whether MyOTP delivered it before deciding to resend. Does NOT verify a code; use `verify_otp` for that.

Input parameters:

- `message_id` (string, required): The UUID returned by `generate_otp` — this identifies which OTP you want a status report on.

Output parameters:

- `DLR` (string): Delivery state: carrier status (ATES, DELIVRD, UNDELIV, EXPIRED, REJECTD) or sent/delivered/read/pending/failed.<reason>, a 'Pending: ...' hint, or a 'Not available ...' explanation. Absent when the…
- `DLR:` (string): Deprecated alias of DLR.
- `Message:` (string): Deprecated alias of message.
- `expires_at` (string): ISO 8601 date-time the OTP expires. Absent when the message_id is unknown.
- `is_active` (boolean): Whether the OTP can still be verified (it has not expired).
- `message` (string): Present instead of DLR when the message_id is not found.

### `extend_otp` (~180 tokens)

Extend OTP expiry

Extend the expiry time of an active OTP without sending a new one. Useful when the end user is taking longer than expected to enter the code (e.g., switched apps, dealing with carrier delivery delay). Adds `duration` seconds (60-14400) to the current `expires_at`. Requires the EXTEND_OTP entitlement (Business or Enterprise plan). Some destination countries don't allow extensions — the API will return 403 in that case. Cheaper and less spammy than calling `generate_otp` again.

Input parameters:

- `duration` (integer, required): Additional seconds to add to the OTP's expiry. Range 60-14400 (1 minute to 4 hours). The new expiry will be the current expiry + this duration.
- `message_id` (string, required): The UUID returned by `generate_otp` — identifies the OTP you want to extend.

Output parameters:

- `expires_at` (string): The new ISO 8601 expiry date-time.
- `message` (string): Message describing the result.
- `status` (string): Status of the request.

### `get_account_info` (~75 tokens)

Get account info

Return account details for the API key in use. Always returns at least the account `email`; depending on plan and platform version may also return balance/credit/plan info. Use this as a sanity check when wiring up MyOTP for the first time — if this call succeeds, your API key and IP whitelist are configured correctly.

Output parameters:

- `email` (string): Email address of the account the API key belongs to.

### `get_usage_report` (~226 tokens)

Get usage report

Fetch a paginated list of OTP transactions for a date range. Each transaction includes message_id, timestamp, phone_number, channel, country, cost, status, and the originating client IP. Date range cannot exceed 31 days. Defaults: last 7 days, page 1, 10 per page. Requires the API_REPORTING entitlement (Business or Enterprise plan). Use this to: audit recent activity, build internal dashboards, reconcile billing, or debug delivery issues across many recipients.

Input parameters:

- `end_date` (string): End date in YYYY-MM-DD format (UTC). If omitted, defaults to today. The range start_date..end_date cannot exceed 31 days.
- `page` (integer): Page number for paginated results, starting at 1. Default 1.
- `per_page` (integer): Results per page, 1-100. Default 10.
- `start_date` (string): Start date in YYYY-MM-DD format (UTC). If omitted, defaults to 7 days before today. The range start_date..end_date cannot exceed 31 days.

Output parameters:

- `current_page` (integer): The page returned.
- `message` (string): Present when the endpoint has no data for the range.
- `per_page` (integer): Rows per page.
- `total_count` (integer): Total transactions matching the date range.
- `total_pages` (integer): Number of pages at the requested per_page.
- `transactions` (array): Transaction rows for the page. May be empty or absent when there is no data.

### `create_account` (~96 tokens)

Create a MyOTP agent account

Create a MyOTP.App agent account and return its one-time API key. No API key is required for this tool. The new account starts with zero balance; USDC top-ups work immediately, while card top-ups unlock after a human confirms the email address.

Input parameters:

- `email` (string, required): Email address for the new MyOTP.App account.
- `name` (string): Optional account, company, or product name (maximum 64 characters).

Output parameters:

- `account_id` (string): Account identifier, 'a' followed by 12 hex characters.
- `api_key` (string): The API key. Shown once, in this response only. Send it as the X-API-Key header.
- `api_key_note` (string)
- `balance` (number): Credits on the balance. Zero at registration.
- `docs` (string)
- `email` (string)
- `email_verified` (boolean): True once the human has confirmed the emailed link. Unlocks card top-ups.
- `plan_id` (integer)
- `status` (string): Account status, 'active' when the key can be used.
- `topup` (object): Where to buy credits.
- `verification_email_sent` (boolean): Whether the confirmation email was queued.

### `get_account_status` (~70 tokens)

Get agent account status

Return email verification, balance, plan, and status for the configured MyOTP agent account. Set resend_verification to request another confirmation email first. Unverified accounts can top up with USDC, but cards stay locked.

Input parameters:

- `resend_verification` (boolean): Send another confirmation email before returning account status.

Output parameters:

- `balance` (number): Credits on the balance.
- `email_verified` (boolean): True once the human has confirmed the emailed link. Unlocks card top-ups.
- `hint` (string): What to do next: verify the email, top up, or start sending.
- `plan_id` (integer)
- `status` (string): Account status, 'active' when the key can be used.

### `get_topup_quote` (~104 tokens)

Get a MyOTP credit top-up quote

Get the live price and payment options for buying MyOTP credits, without making a purchase. Use this when generate_otp or another send fails with HTTP 403 insufficient balance / NoBalance, or before calling `top_up_credits` to show the cost. Returns USDC and card client commands and never exposes the configured API key.

Input parameters:

- `credits` (integer): Number of credits to quote. Integer from 25 to 50,000; defaults to 100.

Output parameters:

- `amount_usd` (string): Total price in US dollars, as a decimal string.
- `credits` (integer): The number of credits priced.
- `currency` (string): Always 'usd'.
- `how_to_pay` (object): Ready-to-run client commands for this amount.
- `max_credits` (integer)
- `methods` (array): Human-readable list of the accepted payment methods.
- `min_credits` (integer)
- `price_per_credit_usd` (number): Unit price. Currently 0.02.
- `rules` (string): Top-up limits: unit price, minimum, maximum and the card cap.

### `top_up_credits` (~142 tokens)

Buy MyOTP credits

Prepare or complete an autonomous MyOTP credit purchase with USDC or card through Machine Payments Protocol (MPP). Use this when generate_otp or another send fails with HTTP 403 insufficient balance / NoBalance. The tool quotes first, then returns a structured 402 challenge and exact retry details for the agent's own MPP client; if fetch is already wrapped by a credential-carrying MPP runtime, it returns the credited response directly.

Input parameters:

- `credits` (integer, required): Number of credits to buy. Integer from 25 to 50,000.
- `dry_run` (boolean): If true, return only the quote and explanation without requesting a payment challenge.

Output parameters:

- `amount_usd` (string): Amount paid in US dollars (settled result).
- `balance` (number): Account balance in credits after the top-up (settled result).
- `challengeId` (string): The MPP challenge id from the 402 response.
- `credits` (integer): Credits bought in this call (settled result).
- `currency` (string)
- `explanation` (string): What happened and what the caller must do next (dry run and 402 results).
- `how_to_pay` (object): Ready-to-run client commands (402 result).
- `offers` (array): Decoded Payment offers from the WWW-Authenticate challenge (402 result).
- `payment` (object): Payment method and reference (settled result).
- `plan_id` (integer)
- `quote` (object): The quote for the requested credits (dry run and 402 results).
- `retry` (object): The request to replay with a payment credential (402 result).
- `status` (string): 'credited' or 'already_credited' (settled result).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/brntech-myotp/myotp-mcp#diagnostics

## Score history

- 2026-09-21: 87
- 2026-09-20: 87
- 2026-09-19: 87
- 2026-09-18: 86
- 2026-09-17: 86
- 2026-09-16: 85
- 2026-09-15: 83
- 2026-09-14: 83
- 2026-09-13: 82
- 2026-09-12: 82
- 2026-09-11: 82
- 2026-09-10: 81
- 2026-09-09: 81
- 2026-09-08: 80
- 2026-09-07: 80
- 2026-09-06: 79
- 2026-09-05: 79
- 2026-09-04: 78
- 2026-09-03: 54

## Common questions

### What is the MyOTP.App MCP server?

MyOTP.App is an MCP server listed in the public MCP registry as io.github.brntech/myotp. Send and verify one-time passcodes over SMS, WhatsApp and Telegram. This page covers its npm package (@myotp/mcp).

### Is the MyOTP.App MCP server safe to use?

MyOTP.App scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the MyOTP.App MCP server expose?

MyOTP.App exposes 10 tools: generate_otp, verify_otp, check_otp_status, extend_otp, get_account_info, and 5 more. Their descriptions and schemas cost roughly 1,982 tokens of context every time the server is loaded.

### Is the MyOTP.App MCP server still maintained?

MyOTP.App is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the MyOTP.App MCP server under?

MyOTP.App declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@myotp/mcp
- Socket report: https://socket.dev/npm/package/@myotp/mcp
- Repository: https://github.com/brntech/myotp-agentkit
- Website: https://mcp.myotp.app/
- Changelog RSS feed: https://verifymcp.io/servers/brntech-myotp/myotp-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/brntech-myotp/myotp-mcp.json
- HTML version of this page: https://verifymcp.io/servers/brntech-myotp/myotp-mcp