Vinkius
TeleSign logo
Vinkius
Vinkius runs on Claude Code

How to Use the TeleSign MCP in Claude Code

Build CI/CD pipelines with Claude Code and TeleSign identity verification protocol.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

TeleSign MCP on Cursor AI Code Editor MCP Client TeleSign MCP on Claude Desktop App MCP Integration TeleSign MCP on OpenAI Agents SDK MCP Compatible TeleSign MCP on Visual Studio Code MCP Extension Client TeleSign MCP on GitHub Copilot AI Agent MCP Integration TeleSign MCP on Google Gemini AI MCP Integration TeleSign MCP on Lovable AI Development MCP Client TeleSign MCP on Mistral AI Agents MCP Compatible TeleSign MCP on Amazon AWS Bedrock MCP Support
MCP Servers - Free for Subscribers
Vinkius runs on Claude Code

Connect TeleSign MCP to Claude Code

Create your Vinkius account to connect TeleSign to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Key Capabilities

Programmatic Risk Scoring

The `score_phone` tool lets you programmatically check the risk of a phone number in your scripts. You pipe the number into this function, and it outputs an integer score. You can then use standard shell logic to fail a build or generate a record based on that score's threshold.

Automated Verification Status Checks

Use `check_verification` in your scripts to get the latest status of a verification attempt. This is key for job runners, as it confirms if an SMS was successfully processed or if the user never responded. It prevents jobs from hanging because they think a step succeeded when it actually timed out.

Execute Multi-Method Verification

Your scripts can trigger multiple checks using `send_sms` and `send_voice_verification`. This is perfect for setting up failover logic—if SMS fails, the script automatically tries voice. This level of control ensures your CI/CD jobs aren't blocked by a single failure point.

Setup guide

Set up TeleSign MCP in Claude Code

Prerequisites

  • Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
  • Active Vinkius subscription with a valid endpoint token
  1. 1

    Run the add command

    Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.

  2. 2

    Verify the connection

    Start a Claude Code session and type /mcp to list connected servers. You should see telesign-mcp with a green status indicator.

  3. 3

    Start using tools

    Ask Claude Code something like "Check my latest TeleSign transactions." It will automatically discover and invoke the available TeleSign tools.

Terminal
claude mcp add --transport http telesign-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about TeleSign MCP in Claude Code

Claude Code runs `score_phone` as part of the pipeline. You can enforce that no code deployment or record creation happens unless the phone number passes a minimum risk score, stopping bad data at the source.
The server exposes raw identity metrics and numerical scores from tools like `score_phone`. This structured data is designed to be easily parsed and used in shell scripts or job runners.
Yes. Your pipeline can call `send_push_verification` first, and if that fails, it can fall back to calling `send_sms`. It’s all about scripting robust failover logic.
You can check activation status using `check_deactivation` before trying any messaging tool. Running `check_telesign_status` first confirms that your entire server connection is up for the job.
Check the logs of the specific API call. If you're dealing with phone numbers, running `get_phone_type` can tell you if the number format is the source of your pipeline failure.

Start using the TeleSign MCP today

We host it, we monitor it, we maintain it. You just paste one token.

Built & Managed by Vinkius 30s setup 10 tools

We've already built the connector for TeleSign. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting. You're up and running in seconds.

Vinkius runs on Claude Claude
Vinkius runs on ChatGPT ChatGPT
Vinkius runs on Cursor Cursor
Vinkius runs on Gemini Gemini
Vinkius runs on Windsurf Windsurf
Vinkius runs on VS Code VS Code
Vinkius runs on JetBrains JetBrains
Vinkius runs on Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.