4,000+ servers built on vurb.ts
Vinkius

Phone Validator Engine MCP Server for Google ADKGive Google ADK instant access to 1 tools to Validate Phone

MCP Inspector GDPR Free for Subscribers

Google Agent Development Kit (ADK) is Google's framework for building production AI agents. Add Phone Validator Engine as an MCP tool provider through Vinkius and your ADK agents can call every tool with full schema introspection.

Ask AI about this MCP Server for Google ADK

The Phone Validator Engine MCP Server for Google ADK is a standout in the Developer Tools category — giving your AI agent 1 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from google.adk.agents import Agent
from google.adk.tools.mcp_tool import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import (
    StreamableHTTPConnectionParams,
)

# Your Vinkius token. get it at cloud.vinkius.com
mcp_tools = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    )
)

agent = Agent(
    model="gemini-2.5-pro",
    name="phone_validator_engine_agent",
    instruction=(
        "You help users interact with Phone Validator Engine "
        "using 1 available tools."
    ),
    tools=[mcp_tools],
)
Phone Validator Engine
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Phone Validator Engine MCP Server

LLMs often accept chaotic phone number inputs or try to format them incorrectly before sending to Twilio or Zenvia. This MCP brings Google's libphonenumber-js to the Edge.

Google ADK natively supports Phone Validator Engine as an MCP tool provider. declare Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 1 tools with Gemini's long-context reasoning for complex multi-tool workflows, with production-ready session management and evaluation built in.

The Superpowers

  • E.164 Strict Format: Cleans and formats chaotic inputs into mathematically perfect E.164 strings.
  • Country Validation: Validates the exact country code and identifies fake numbers immediately.

The Phone Validator Engine MCP Server exposes 1 tools through the Vinkius. Connect it to Google ADK in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 1 Phone Validator Engine tools available for Google ADK

When Google ADK connects to Phone Validator Engine through Vinkius, your AI agent gets direct access to every tool listed below — spanning phone-validation, e164, data-cleaning, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

validate

Validate phone on Phone Validator Engine

Pass the raw phone string and optionally a country code. The engine uses libphonenumber to validate structure, detect carrier type, and format to E.164 standard. Validates and formats a phone number deterministically to E.164 standard using Google libphonenumber-js

Connect Phone Validator Engine to Google ADK via MCP

Follow these steps to wire Phone Validator Engine into Google ADK. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Install Google ADK

Run pip install google-adk
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token
03

Create the agent

Save the code above and integrate into your ADK workflow
04

Explore tools

The agent will discover 1 tools from Phone Validator Engine via MCP

Why Use Google ADK with the Phone Validator Engine MCP Server

Google ADK provides unique advantages when paired with Phone Validator Engine through the Model Context Protocol.

01

Google ADK natively supports MCP tool servers. declare a tool provider and the framework handles discovery, validation, and execution

02

Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with Phone Validator Engine

03

Production-ready features like session management, evaluation, and deployment come built-in. not bolted on

04

Seamless integration with Google Cloud services means you can combine Phone Validator Engine tools with BigQuery, Vertex AI, and Cloud Functions

Phone Validator Engine + Google ADK Use Cases

Practical scenarios where Google ADK combined with the Phone Validator Engine MCP Server delivers measurable value.

01

Enterprise data agents: ADK agents query Phone Validator Engine and cross-reference results with internal databases for comprehensive analysis

02

Multi-modal workflows: combine Phone Validator Engine tool responses with Gemini's vision and language capabilities in a single agent

03

Automated compliance checks: schedule ADK agents to query Phone Validator Engine regularly and flag policy violations or configuration drift

04

Internal tool platforms: build self-service agent platforms where teams connect their own MCP servers including Phone Validator Engine

Example Prompts for Phone Validator Engine in Google ADK

Ready-to-use prompts you can give your Google ADK agent to start working with Phone Validator Engine immediately.

01

"Clean and format this messy user input into an E.164 phone number: '+44 (0) 20 7946 0958'"

02

"Check if the input `11 98888-0000` is structurally valid, assuming the default country is Brazil (`BR`)."

03

"Extract the Alpha-2 Country Code from this international number: `+1-415-555-2671`."

Troubleshooting Phone Validator Engine MCP Server with Google ADK

Common issues when connecting Phone Validator Engine to Google ADK through Vinkius, and how to resolve them.

01

McpToolset not found

Update: pip install --upgrade google-adk

Phone Validator Engine + Google ADK FAQ

Common questions about integrating Phone Validator Engine MCP Server with Google ADK.

01

How does Google ADK connect to MCP servers?

Import the MCP toolset class and pass the server URL. ADK discovers and registers all tools automatically, making them available to your agent's tool-use loop.
02

Can ADK agents use multiple MCP servers?

Yes. Declare multiple MCP tool providers in your agent configuration. ADK merges all tool schemas and the agent can call tools from any server in a single turn.
03

Which Gemini models work best with MCP tools?

Gemini 2.0 Flash and Pro models both support function calling required for MCP tools. Flash is recommended for latency-sensitive use cases, Pro for complex reasoning.

Explore More MCP Servers

View all →