verifyapi_send_otpLABSCO SUMMARY
Phone verification and fraud scoring, callable.
The pieces of a signup flow that normally live inside your backend — send the code, check it, decide whether the number is worth trusting — become calls you can make while building or debugging that flow.
What it is
A TeleSign server covering verification, phone intelligence, fraud scoring and SMS, with TeleSign's own documentation alongside them. Codes go out over SMS, voice, WhatsApp, Viber, RCS or email, with automatic fallback between channels.
What you get
- verifyapi_send_otp sends a passcode over SMS, voice, WhatsApp, Viber, RCS or email, falling back between channels automatically
- verifyapi_check_code verifies the code a user typed; verifyapi_get_status reports on a verification in flight
- phoneid_get_info returns a number's type — mobile, landline or VoIP — with carrier and location
- intelligence_assess_risk returns a fraud risk score from 0 to 1000 with an allow, flag or block recommendation
- messaging_send_sms sends transactional or marketing SMS
- docs_search and docs_get read TeleSign's API documentation without opening a browser
Requirements
Node.js 18 or later and TeleSign API credentials. Works from Cursor, Claude Code, VS Code, Windsurf or any other MCP client.
Setup effort
One command plus a key — npx -y telesign-mcp, then supply credentials
USE CASES
01
Testing a signup verification flow end to end
The code goes out over the channel you name and the check runs against what the user typed, so the whole round trip is exercised in one session.
02
Deciding whether a phone number is worth trusting
A risk score from 0 to 1000 with an allow, flag or block call, plus whether the number is mobile, landline or VoIP.
03
Chasing a verification that never landed
The status of a verification in flight says whether it is still working through the fallback channels or has already failed.
04
Sending an alert to a customer
A transactional SMS goes out directly, without wiring the messaging API into whatever you are building first.
05
Looking up how a TeleSign endpoint behaves
The documentation is searchable and readable from the assistant, so the parameter you half-remember is confirmed in place.
8 tools
Listed in project docs. Your client may show a different list.
verifyapi_check_codeverifyapi_get_statusphoneid_get_infointelligence_assess_riskmessaging_send_smsdocs_searchdocs_getBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation.
Requires
- npx on PATH
- Node.js 18+
- TELESIGN_CUSTOMER_ID in your environment
- TELESIGN_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y telesign-mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"telesign": {
"command": "node",
"args": [
"<YOUR_PATH_TO_TELESIGN_MCP>/build/index.js"
],
"env": {
"TELESIGN_CUSTOMER_ID": "<YOUR_TELESIGN_CUSTOMER_ID>",
"TELESIGN_API_KEY": "<YOUR_TELESIGN_API_KEY>"
}
}
}
}
