Compatible with every major AI agent and IDE
What is the 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.
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.
Built-in capabilities (1)
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
Why Google ADK?
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.
- —
Google ADK natively supports MCP tool servers. declare a tool provider and the framework handles discovery, validation, and execution
- —
Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with Phone Validator Engine
- —
Production-ready features like session management, evaluation, and deployment come built-in. not bolted on
- —
Seamless integration with Google Cloud services means you can combine Phone Validator Engine tools with BigQuery, Vertex AI, and Cloud Functions
Phone Validator Engine in Google ADK
Phone Validator Engine and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Phone Validator Engine to Google ADK through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Phone Validator Engine in Google ADK
The Phone Validator Engine 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. All 1 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Google ADK only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* 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
How Vinkius secures
Phone Validator Engine for Google ADK
Every tool call from Google ADK to the Phone Validator Engine MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Does it support Brazilian numbers?
Yes, perfectly handles the 9-digit rule.
Can it extract the country?
Yes, it returns the Alpha-2 country code.
Is it local?
Yes, 100% local regex/metadata evaluation.
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.
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.
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.
McpToolset not found
Update: pip install --upgrade google-adk
Explore More MCP Servers
View all →
Nifty (All-in-One Project Management)
10 toolsManage projects via Nifty — create tasks, track sprint milestones, and audit project portfolios.

Winevybe
10 toolsAutomate sommelier intelligence via Winevybe — search global wine catalogs, check vineyard ratings, and manage virtual cellars directly from any AI agent.

Postproxy
11 toolsManage your Google Business Profile posts, reviews, and local SEO presence across multiple locations from one dashboard.

Robly
12 toolsAutomate email marketing via Robly — manage contacts, subscriber lists, and campaign stats with AI.
