telesign-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELESIGN_API_KEY | Yes | Your TeleSign API key | |
| TELESIGN_CUSTOMER_ID | Yes | Your TeleSign customer ID |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| phoneid_get_infoB | Get detailed information about a phone number including type (mobile/landline/VoIP), carrier, and location. See docs://telesign/phone-id for details. |
| intelligence_assess_riskA | Get fraud risk score (0-1000) for a phone number. Returns recommendation: allow/flag/block. See docs://telesign/intelligence for score interpretation. |
| verifyapi_send_otpA | Send a one-time passcode (OTP) to a phone number. Returns reference_id needed for verifyapi_check_code. Supports multiple fallback channels with fallback_time. See docs://telesign/verify-api. |
| verifyapi_check_codeA | Verify an OTP code that was sent to a user. Requires the reference_id from verifyapi_send_otp. |
| verifyapi_get_statusA | Retrieve details about a verification process in progress. Use this to check the current status of a verification including channel-by-channel delivery status. |
| messaging_send_smsC | Send an SMS message to a phone number. See docs://telesign/messaging-sms for message types and delivery codes. |
| docs_searchA | Search TeleSign documentation. Use for error codes, API details, best practices, etc. |
| docs_getB | Get complete documentation for a TeleSign topic. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| telesign-overview | TeleSign overview documentation |
| telesign-phone-id | TeleSign phone-id documentation |
| telesign-intelligence | TeleSign intelligence documentation |
| telesign-verify-api | TeleSign verify-api documentation |
| telesign-messaging-sms | TeleSign messaging-sms documentation |
| telesign-error-codes | TeleSign error-codes documentation |
| telesign-best-practices | TeleSign best-practices documentation |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mdp18/telesign-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server