Security & Testing

myotp.app

Manages OTP generation, delivery via SMS/WhatsApp/Telegram, verification, status checks, and expiry extension for secure authentication.

1 endpoint7 known toolsFirst detected May 29, 2026Last detected September 6, 2026

ENDPOINT 1

https://mcp.myotp.app/mcp

No auth detected

MCP server metadata

Name: myotp-mcp
Version: 0.1.0

Capabilities

tools.listChanged

Server instructions

MyOTP.App MCP server — send and verify OTPs over SMS, WhatsApp, and Telegram. Typical flow: call `generate_otp` with a phone number to send a code, save the returned `message_id`, then call `verify_otp` with the code the end user typed. Use `check_otp_status` to debug delivery, `extend_otp` to give users more time, and `get_usage_report` for transaction history. All operations require a MyOTP API key — get one at https://myotp.app/sign-up/ (15 free trial credits, no card required). Phone numbers must be in international format with no leading + or 0 (e.g. '14155551234' for a US number).

Known tools 7

generate_otp

Send a one-time password (OTP) to a phone number via SMS, WhatsApp, or Telegram.

Potential side effects

verify_otp

Verify a code submitted by an end user against the OTP MyOTP delivered.

Inferred read-only

check_otp_status

Check whether a previously sent OTP is still active and (with DLR_ACCESS entitlement on Enterprise plan) get its delivery status.

Inferred read-only

extend_otp

Extend the expiry time of an active OTP without sending a new one.

Inferred read-only

get_account_info

Return account details for the API key in use.

Inferred read-only

get_usage_report

Fetch a paginated list of OTP transactions for a date range.

Inferred read-only

create_account

Account signup at MyOTP.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.myotp-mcp]
url = "https://mcp.myotp.app/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "myotp-mcp": {
      "type": "http",
      "url": "https://mcp.myotp.app/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: myotp-mcp
Remote MCP URL: https://mcp.myotp.app/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "myotp-mcp": {
      "url": "https://mcp.myotp.app/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "myotp-mcp": {
      "type": "http",
      "url": "https://mcp.myotp.app/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "myotp-mcp",
  "transport": "streamable-http",
  "url": "https://mcp.myotp.app/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.