# TeleSign MCP > TeleSign helps you validate user identity instantly using phone number intelligence, risk scoring, and multi-channel verification. It prevents fraud at sign-up by checking everything from carrier details to deactivation status, giving your application confidence in every new user. ## Overview - **Category:** communication-messaging - **Price:** Free - **Tags:** phone-verification, fraud-prevention, otp-authentication, risk-scoring, identity-verification, phone-intelligence ## Description Need to know if a user's phone number is real and safe? This MCP connects your agent to TeleSign’s full suite of identity tools. You can get deep insights into any number—like its carrier, type, or even location—before asking for more data. Need proof the user owns the line? Send an SMS code, a voice call, or use push notifications for verification. Plus, it calculates a risk score to tell you how likely that phone is involved in fraud. You can also check if a number has been deactivated or ported recently. When you connect this MCP via Vinkius, your AI client gains access to all these checks, letting you build robust sign-up flows without leaving your chat window. ## Tools ### check_deactivation Confirms whether a specific phone number is currently active or if it has been deactivated by the carrier. ### check_telesign_status Verifies the API connectivity and overall operational status of the TeleSign service. ### check_verification Retrieves the current verification status for a user who has already attempted an identity check. ### get_phone_id Gathers core identifying information about a phone number, such as its country code and carrier details. ### get_phone_type Determines the nature of the phone line—whether it is mobile, landline, or another type. ### score_phone Analyzes a phone number and outputs a numerical risk score based on known fraud patterns. ### send_push_verification Triggers an identity verification request via a push notification, which is useful for app-based signups. ### send_sms Sends a standard text message (SMS) containing a unique one-time password to the user's number. ### send_verification Handles the general process of sending out a required verification code for account setup. ### send_voice_verification Delivers the necessary verification codes using an automated voice call to the user's phone number. ## Prompt Examples **Prompt:** ``` Send a verification code to +14155551234. ``` **Response:** ``` Verification code sent! Reference ID: ref_8291. The user should receive the code shortly. ``` **Prompt:** ``` Score fraud risk for +14155551234. ``` **Response:** ``` Risk score for +14155551234: 120/1000 (Low Risk). Carrier: Verizon, Type: Mobile, Location: San Francisco, CA. ``` **Prompt:** ``` Check if +14155551234 has been deactivated. ``` **Response:** ``` Number +14155551234 is active. Last ported: 2024-03-15 from AT&T to Verizon. No deactivation detected. ``` ## Capabilities ### Score phone risk The tool calculates a detailed risk score for any given number, helping you filter out suspicious accounts. ### Verify user ownership You can send verification codes via SMS, automated voice calls, or push notifications to confirm the user has access to that line. ### Check phone status It identifies a number's carrier, type (mobile/landline), and location intelligence, giving you full context on the line itself. ### Detect deactivation You can check if a phone number is currently active or if it has been deactivated or ported away from its original service. ## Use Cases ### Onboarding a new B2B user. A Product Manager asks their agent to onboard a high-value client. The agent first uses score_phone and get_phone_type to confirm the number is corporate, then sends an SMS code using send_sms for verification. If both checks pass, the account is created. ### Debugging suspicious sign-up spikes. A Fraud Analyst needs to investigate a sudden spike in failed signups. They use check_deactivation on the suspect numbers and run get_phone_id repeatedly to see if they share common carrier patterns, helping pinpoint bot activity. ### Testing internal system health. A DevOps Engineer needs to confirm that their new signup microservice is talking correctly to TeleSign. They use check_telesign_status first and then run check_verification on a test number to ensure the entire flow works. ### Handling enterprise app logins. An agent needs to authenticate an employee using company devices. Instead of SMS, they opt for send_push_verification, ensuring that only users with the current corporate app can proceed, securing the account flow. ## Benefits - Reduce sign-up fraud immediately. Instead of just checking if a number is valid, you use the score_phone tool to calculate risk levels and reject high-risk accounts before they hurt your business. - Support multiple verification paths. You aren't limited to SMS; you can send codes via automated voice calls or push notifications, giving flexible options for different user flows. - Get full line context upfront. The get_phone_id tool gives your agent the carrier and location details instantly, which helps differentiate between a real, active business number and a burner phone. - Handle account lifecycle checks. You can use check_deactivation to confirm if a number that was previously valid is still in service, preventing support headaches months down the line. - Automate complex workflows. By running multiple tools like score_phone and get_phone_type together, you build a single, smart decision point for your agent. ## How It Works The bottom line is your agent gets immediate, actionable data on phone numbers that prevents bad actors from getting into your system. 1. First, your agent passes the target phone number to this MCP. 2. The tool runs several checks—like scoring the risk and checking deactivation status—and then sends back a comprehensive JSON report with all the details. 3. Your AI client reads the report, allowing you to make an automated decision about whether to accept or deny the user sign-up. ## Frequently Asked Questions **How does TeleSign MCP help prevent fraud?** It calculates a risk score (score_phone) and uses phone intelligence to identify suspicious patterns, allowing you to reject high-risk signups automatically before they enter your system. **Can I send verification codes using multiple methods with TeleSign MCP?** Yes. You can use the dedicated tools for SMS (send_sms), voice calls (send_voice_verification), or push notifications (send_push_verification) to cover all user scenarios. **What is phone intelligence in TeleSign MCP?** Phone intelligence refers to the deep data about a number, including its carrier, type (mobile/landline), and location. The get_phone_id tool provides this context instantly. **Does TeleSign MCP check if a phone number is still active?** Yes, the check_deactivation tool verifies the current status of a number, confirming it hasn't been deactivated or ported away from its original service.