Send and verify one-time passcodes over SMS, WhatsApp and Telegram.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
MyOTP.App API key, sent per request so the hosted server never stores it. Omit it to call create_account or get_topup_quote, which need no key. Note: calls reach the MyOTP API from 108.61.176.199, so add that IP to your key's allowlist or every call returns 403.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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.
The UUID returned by `generate_otp` — this identifies which OTP you want a status report on.
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.
| Argument | Type | Description |
|---|---|---|
| message_id* | string | The UUID returned by `generate_otp` — this identifies which OTP you want a status report on. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"message_id"
],
"properties": {
"message_id": {
"type": "string",
"format": "uuid",
"description": "The UUID returned by `generate_otp` — this identifies which OTP you want a status report on."
}
},
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| name | string | Optional account, company, or product name (maximum 64 characters). |
| email* | string | Email address for the new MyOTP.App account. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"email"
],
"properties": {
"name": {
"type": "string",
"maxLength": 64,
"description": "Optional account, company, or product name (maximum 64 characters)."
},
"email": {
"type": "string",
"format": "email",
"description": "Email address for the new MyOTP.App account."
}
},
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| duration* | integer | 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 | The UUID returned by `generate_otp` — identifies the OTP you want to extend. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"message_id",
"duration"
],
"properties": {
"duration": {
"type": "integer",
"maximum": 14400,
"minimum": 60,
"description": "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": {
"type": "string",
"format": "uuid",
"description": "The UUID returned by `generate_otp` — identifies the OTP you want to extend."
}
},
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| 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. |
| 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. |
| 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 filters. |
| 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). |
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.
No arguments.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}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.
| Argument | Type | Description |
|---|---|---|
| resend_verification | boolean | Send another confirmation email before returning account status. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"resend_verification": {
"type": "boolean",
"description": "Send another confirmation email before returning account status."
}
},
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| credits | integer | Number of credits to quote. Integer from 25 to 50,000; defaults to 100. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"credits": {
"type": "integer",
"default": 100,
"maximum": 50000,
"minimum": 25,
"description": "Number of credits to quote. Integer from 25 to 50,000; defaults to 100."
}
},
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| page | integer | Page number for paginated results, starting at 1. Default 1. |
| 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. |
| 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. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"page": {
"type": "integer",
"minimum": 1,
"description": "Page number for paginated results, starting at 1. Default 1."
},
"end_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "End date in YYYY-MM-DD format (UTC). If omitted, defaults to today. The range start_date..end_date cannot exceed 31 days."
},
"per_page": {
"type": "integer",
"maximum": 100,
"minimum": 1,
"description": "Results per page, 1-100. Default 10."
},
"start_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "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."
}
},
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| credits* | integer | 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. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"credits"
],
"properties": {
"credits": {
"type": "integer",
"maximum": 50000,
"minimum": 25,
"description": "Number of credits to buy. Integer from 25 to 50,000."
},
"dry_run": {
"type": "boolean",
"description": "If true, return only the quote and explanation without requesting a payment challenge."
}
},
"additionalProperties": false
}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.).
| Argument | Type | Description |
|---|---|---|
| otp* | string | 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. |
| 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. |
| 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. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"otp"
],
"properties": {
"otp": {
"type": "string",
"pattern": "^\\d{3,8}$",
"description": "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."
},
"message_id": {
"type": "string",
"format": "uuid",
"description": "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."
},
"phone_number": {
"type": "string",
"pattern": "^[1-9]\\d{6,14}$",
"description": "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."
}
},
"additionalProperties": false
}| 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 this in production user flows. |
| 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 | Destination phone number in international format with NO leading + or 0. Must be 7-15 digits and start with a non-zero digit. Example: '14155550123' for a US number, '447911123456' for a UK number. |
| 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). On WhatsApp the template's own expiry overrides otp_validity. Requires the ACCESS_TO_TEMPLATES entitlement (Business plan and up). Not supported on telegram (Telegram generates its own message text). |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"phone_number"
],
"properties": {
"brand": {
"type": "string",
"pattern": "^[a-zA-Z0-9.]+$",
"maxLength": 16,
"minLength": 3,
"description": "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": {
"enum": [
"sms",
"whatsapp",
"telegram"
],
"type": "string",
"description": "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."
},
"otp_code": {
"type": "string",
"pattern": "^\\d{3,8}$",
"description": "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."
},
"force_send": {
"type": "boolean",
"description": "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 filters."
},
"otp_length": {
"type": "integer",
"maximum": 8,
"minimum": 3,
"description": "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)."
},
"return_otp": {
"type": "boolean",
"description": "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 this in production user flows."
},
"otp_validity": {
"type": "integer",
"maximum": 14400,
"minimum": 30,
"description": "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": {
"type": "string",
"pattern": "^[1-9]\\d{6,14}$",
"maxLength": 15,
"minLength": 7,
"description": "Destination phone number in international format with NO leading + or 0. Must be 7-15 digits and start with a non-zero digit. Example: '14155550123' for a US number, '447911123456' for a UK number."
},
"template_order": {
"type": "integer",
"maximum": 99,
"minimum": 1,
"description": "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). On WhatsApp the template's own expiry overrides otp_validity. Requires the ACCESS_TO_TEMPLATES entitlement (Business plan and up). Not supported on telegram (Telegram generates its own message text)."
}
},
"additionalProperties": false
}