# TeleSign MCP for AI Agents AI Agent Connect > TeleSign lets your AI agent handle phone verification, SMS OTPs, and fraud scoring at scale. It gives your agent the ability to identify carriers, check for deactivations, and assess risk scores for incoming phone numbers during sign-up or identity checks. It's the bridge between your AI and enterprise-grade communication security. ## Overview - **Category:** communication-messaging - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_oiuYgXjrVlaOSsTSlNFA3oyRAAL75ekhSY2WHRyf/ai-agent-connect - **Tags:** phone-verification, fraud-prevention, otp-authentication, risk-scoring, identity-verification, phone-intelligence ## Description This TeleSign MCP lets you manage phone verification and intelligence. You're trying to build a system that doesn't let fake accounts flood your platform. Usually, this means jumping between carrier databases and manual verification logs. This Connector changes that by letting your AI agent do the digging for you. Instead of you hunting for a phone's location or carrier, your agent pulls that data and calculates a risk score in seconds. It handles the actual delivery of OTPs through text, voice calls, or push notifications, so you don't have to manage the plumbing of the communication channels. When you add this to your stack via the Vinkius catalog, your agent becomes a gatekeeper that can spot a high-risk number before a user even finishes creating an account. It's about moving from a state of uncertainty to knowing exactly who your users are without adding more manual steps to your workflow. You get a production-ready way to handle high-volume identity checks while keeping your security posture tight. This means fewer bot registrations, cleaner data, and a much smoother experience for your real customers who just want to get into the app. It takes the guesswork out of phone-based security by providing immediate, actionable data on every number that touches your platform. ## Tools ### get_phone_id Fetch the unique identity details for a phone number. Use this to keep track of specific users across different sessions. ### check_telesign_status Check if your account is connected and ready to send messages. This ensures your agent knows the connection is live before trying to send an OTP. ### check_verification See if a specific user has already completed their verification. This helps your agent determine if a user can proceed to the next step. ### get_phone_type Find out if a number is a mobile, landline, or VoIP. This helps filter out non-mobile numbers during the sign-up process. ### score_phone Get a risk score for a phone number to detect potential fraud. This lets your agent block high-risk numbers automatically. ### send_push_verification Send a push notification to a registered device for verification. This provides a modern alternative to SMS for verified users. ### send_sms Send a standard text message to any phone number. Use this for general communication or simple alerts. ### send_verification Send a specific verification code to a user's phone. This is the primary tool for standard OTP workflows. ### send_voice_verification Deliver a verification code via an automated phone call. This works well for users who don't receive text messages. ### check_deactivation Verify if a phone number is still active and reachable. This prevents sending messages to dead numbers and wasting credits. ## Prompt Examples **Prompt:** ``` Check if +12025550123 is a mobile number and tell me the carrier. ``` **Response:** ``` I've checked the phone number +12025550123. Here are the details: | Detail | Information | | :--- | :--- | | **Type** | Mobile | | **Carrier** | Verizon | | **Location** | Washington, D.C. | The number is confirmed as a valid mobile line. ``` **Prompt:** ``` Send a verification code to +14155550199. ``` **Response:** ``` Verification code sent! Reference ID: ref_9921. The user should receive the code shortly. ``` **Prompt:** ``` Is this number high risk? +18005550100. ``` **Response:** ``` Risk score for +18005550100: **850/1000 (High Risk)**. * **Carrier**: Unknown * **Type**: VoIP * **Recommendation**: Block registration. ``` ## Capabilities ### Send SMS OTPs Dispatch verification codes via text message to users instantly. ### Deliver voice codes Send automated calls with verification codes for users who can't receive texts. ### Check phone metadata Identify carrier, line type, and location for any phone number. ### Assess fraud risk Generate a risk score for phone numbers to detect and block bad actors. ### Verify push notifications Send push-based verification to registered devices for a modern auth flow. ### Check deactivation status Confirm if a phone number is still active before attempting to send messages. ### Test API connection Verify your account is active and reachable before starting a workflow. ## Use Cases ### Fraud Prevention A security team uses `score_phone` to flag numbers from high-risk regions during a spike in bot registrations. ### Multi-Factor Auth A product manager sets up `send_voice_verification` as a backup for users who can't receive SMS codes. ### Identity Verification A customer success agent uses `get_phone_id` to confirm a user's identity during a live support chat. ### Onboarding Flow A developer uses `send_verification` to gate access to a beta feature, ensuring only real users can enter. ## Benefits - Block fraudulent registrations by using `score_phone` to identify high-risk numbers instantly. - Reach users more effectively by choosing between `send_sms`, `send_voice_verification`, or `send_push_verification`. - Gain deeper insights into your user base by pulling carrier and location data with `get_phone_type`. - Save on communication costs by using `check_deactivation` to confirm a number is active before sending a message. - Automate your entire onboarding flow with `send_verification` to provide a faster experience for real users. - Maintain system reliability by running `check_telesign_status` to ensure your connection is always active. ## How It Works The bottom line is you get a secure, automated way to verify users and block fraud without managing the underlying communication protocols. 1. Connect your TeleSign account to the Connector. 2. Grant the necessary permissions for your AI agent to access communication tools. 3. Ask your agent to send a verification code or check a phone's risk score. ## Frequently Asked Questions **How does TeleSign MCP help prevent bots?** It provides a risk score for every phone number. Your AI agent can use these scores to automatically block high-risk numbers during the sign-up process, keeping your platform clean from bots. **Can I send voice calls for verification?** Yes, the Connector supports automated voice calls. This is a great fallback for users who do not receive SMS messages or prefer voice authentication. **How do I know if a phone number is active?** You can check the deactivation status of any number. This ensures you aren't wasting credits on dead numbers and helps maintain high delivery rates. **What kind of phone data can I get?** The Connector can identify the carrier, the line type (like mobile or landline), and the general location of the phone number. **Can this handle high-volume SMS?** Yes, it connects to TeleSign's enterprise-grade infrastructure, making it suitable for high-volume verification needs. **How does the fraud scoring work?** It analyzes the phone number against known risk patterns to generate a score. Your agent can then use this score to decide whether to allow or block a registration. **Can I use push notifications instead of SMS?** Yes, you can send push-based verification. This is a great way to offer a modern authentication experience for users who already have the app installed. **Can my AI send and verify OTP codes?** Yes. `send_verification` sends the code, then `check_verification` validates the user's response. **Can I check fraud risk for a phone number?** Yes. `score_phone` returns a fraud risk score based on carrier intelligence and historical data. **Can I identify if a number is mobile or landline?** Yes. `get_phone_type` returns whether the number is mobile, landline, VoIP, or toll-free.