Compatible with every major AI agent and IDE
What is the Country Data Resolver MCP Server?
When a CRM agent processes international contacts, it cannot guess that 'MK' is North Macedonia or that 'TL' is Timor-Leste. This MCP resolves any ISO 3166-1 alpha-2 code to its full name in English, Portuguese, Spanish, or French.
The Superpowers
- 249 Countries: Full ISO 3166-1 database with alpha-2, alpha-3, and numeric codes.
- 4 Languages: Country names in EN, PT, ES, and FR for multilingual CRM workflows.
Built-in capabilities (1)
Pass the alpha-2 code (e.g. "BR", "DE", "JP") and optionally a language for the name (en, pt, es, fr). Never guess country names for obscure codes. Resolves ISO country codes to full country names in 4 languages, plus alpha-3 and numeric codes. Essential for CRM and Martech agents handling international data
Why LlamaIndex?
LlamaIndex agents combine Country Data Resolver tool responses with indexed documents for comprehensive, grounded answers. Connect 1 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
- —
Data-first architecture: LlamaIndex agents combine Country Data Resolver tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain Country Data Resolver tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query Country Data Resolver, a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what Country Data Resolver tools were called, what data was returned, and how it influenced the final answer
Country Data Resolver in LlamaIndex
Country Data Resolver and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Country Data Resolver to LlamaIndex 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 Country Data Resolver in LlamaIndex
The Country Data Resolver 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 LlamaIndex 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
Country Data Resolver for LlamaIndex
Every tool call from LlamaIndex to the Country Data Resolver MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How many countries are supported?
All 249 countries and territories in the ISO 3166-1 standard, including overseas territories and special regions.
What languages are available for country names?
English (en), Portuguese (pt), Spanish (es), and French (fr). The engine defaults to English if the requested language is not available.
Does it validate country codes?
Yes. If you pass an invalid code like 'XX', the engine returns a clear error instead of guessing. This prevents data corruption in CRM systems.
How does LlamaIndex connect to MCP servers?
Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
Can I combine MCP tools with vector stores?
Yes. LlamaIndex agents can query Country Data Resolver tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
Does LlamaIndex support async MCP calls?
Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.
BasicMCPClient not found
Install: pip install llama-index-tools-mcp
Explore More MCP Servers
View all →
AMcards
7 toolsSend personalized greeting cards and handwritten notes to clients and prospects that feel genuinely personal at scale.

Elastic Security
10 toolsManage SIEM and SOC operations via Elastic Security — monitor detection rules, search security alerts (Signals), handle whitelisting, and audit threat coverage directly from any AI agent.

Odoo Sales
8 toolsCreate quotations, confirm sales orders, manage products and pricelists — Odoo Sales pipeline through natural conversation.

Gong
12 toolsUnlock revenue intelligence by analyzing calls, transcripts, and customer interactions.
