4,000+ servers built on vurb.ts
Vinkius
LlamaIndexFramework
LlamaIndex
Country Data Resolver MCP Server

Bring Country
to LlamaIndex

Learn how to connect Country Data Resolver to LlamaIndex and start using 1 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Resolve Country

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Country Data Resolver

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)

resolve_country

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

L
See it in action

Country Data Resolver in LlamaIndex

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

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.

Country Data Resolver
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

The Vinkius Advantage

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.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

How many countries are supported?

All 249 countries and territories in the ISO 3166-1 standard, including overseas territories and special regions.

02

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.

03

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.

04

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.

05

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.

06

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

07

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

Explore More MCP Servers

View all →