Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Country By Api Ninjas MCP Server find countries with a population over 50 million and GDP growth above 3%"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
用于访问 Country By Api Ninjas API 的 MCP 服务器。
EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！
🌐 访问 EMCP 平台
📝 注册并登录账号
🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器
🔍 搜索或找到本服务器（bach-country_by_api_ninjas）
🎉 点击 "安装 MCP" 按钮
✅ 完成！即可在您的应用中使用
✨ 零配置：无需手动编辑配置文件
🎨 可视化管理：图形界面轻松管理所有 MCP 服务器
🔐 安全可靠：统一管理 API 密钥和认证信息
🚀 一键安装：MCP 广场提供丰富的服务器选择
📊 使用统计：实时查看服务调用情况
立即访问 EMCP 平台 开始您的 MCP 之旅！
Related MCP server: Country Info MCP Server
这是一个 MCP 服务器，用于访问 Country By Api Ninjas API。
PyPI 包名: bach-country_by_api_ninjas
版本: 1.0.0
传输协议: stdio
pip install bach-country_by_api_ninjaspip install -e .# 运行（uvx 会自动安装并运行）
uvx --from bach-country_by_api_ninjas bach_country_by_api_ninjas
# 或指定版本
uvx --from bach-country_by_api_ninjas@latest bach_country_by_api_ninjaspython server.py# 安装
pip install bach-country_by_api_ninjas
# 运行（命令名使用下划线）
bach_country_by_api_ninjas此 API 需要认证。请设置环境变量:
export API_KEY="your_api_key_here"变量名 | 说明 | 必需 |
| API 密钥 | 是 |
| 不适用 | 否 |
| 不适用 | 否 |
编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:
{
"mcpServers": {
"bach-country_by_api_ninjas": {
"command": "uvx",
"args": ["--from", "bach-country_by_api_ninjas", "bach_country_by_api_ninjas"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}编辑 Claude Desktop 配置文件 claude_desktop_config.json:
{
"mcpServers": {
"bach-country_by_api_ninjas": {
"command": "uvx",
"args": ["--from", "bach-country_by_api_ninjas", "bach_country_by_api_ninjas"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}此服务器提供以下工具:
v1countryAPI Ninjas Country API endpoint.
端点: GET /v1/country
参数:
name (string): Plain English name, 2-letter ISO-3166 alpha-2, or 3-letter ISO-3166 alpha-3 code of country.
currency (string): 3-letter currency code of country (e.g. USD).
min_gdp (number): Minimum gross domestic product (GDP) of country, in US Dollars.
max_gdp (number): Maximum gross domestic product (GDP) of country, in US Dollars.
min_population (number): Minimum population of country.
max_population (number): Maximum population of country.
min_area (number): Minimum surface area of country in km2.
max_area (number): Maximum surface area of country in km2.
min_unemployment (number): Minimum unemployment rate in %.
max_unemployment (number): Maximum unemployment rate in %.
min_gdp_growth (number): Minimum GDP growth rate in %.
max_gdp_growth (number): Maximum GDP growth rate in %.
min_infant_mortality (number): Minimum infant mortality rate in %.
max_infant_mortality (number): Maximum infant mortality rate in %.
min_fertility (number): Minimum fertility rate in %.
max_fertility (number): Maximum fertility rate in %.
min_urban_pop_rate (number): Minimum urban population rate in %.
max_urban_pop_rate (number): Maximum urban population rate in %.
limit (number): How many results to return. Must be between 1 and 30. Default is 5.
传输协议: stdio
HTTP 客户端: httpx
MIT License - 详见 LICENSE 文件。
此服务器由 API-to-MCP 工具生成。
版本: 1.0.0
API Ninjas Country API endpoint.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Plain English name, 2-letter ISO-3166 alpha-2, or 3-letter ISO-3166 alpha-3 code of country. | |
| currency | No | 3-letter currency code of country (e.g. USD). | |
| min_gdp | No | Minimum gross domestic product (GDP) of country, in US Dollars. | 0 |
| max_gdp | No | Maximum gross domestic product (GDP) of country, in US Dollars. | 0 |
| min_population | No | Minimum population of country. | 0 |
| max_population | No | Maximum population of country. | 0 |
| min_area | No | Minimum surface area of country in km2. | 0 |
| max_area | No | Maximum surface area of country in km2. | 0 |
| min_unemployment | No | Minimum unemployment rate in %. | 0 |
| max_unemployment | No | Maximum unemployment rate in %. | 0 |
| min_gdp_growth | No | Minimum GDP growth rate in %. | 0 |
| max_gdp_growth | No | Maximum GDP growth rate in %. | 0 |
| min_infant_mortality | No | Minimum infant mortality rate in %. | 0 |
| max_infant_mortality | No | Maximum infant mortality rate in %. | 0 |
| min_fertility | No | Minimum fertility rate in %. | 0 |
| max_fertility | No | Maximum fertility rate in %. | 0 |
| min_urban_pop_rate | No | Minimum urban population rate in %. | 0 |
| max_urban_pop_rate | No | Maximum urban population rate in %. | 0 |
| limit | No | How many results to return. Must be between 1 and 30. Default is 5. | 0 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure but provides none. It does not indicate this is a read-only search operation, does not describe return format, pagination behavior, rate limits, or whether filters use AND/OR logic.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is brief (6 words), avoiding verbosity, but the single sentence fails to earn its place by providing actionable information. It is appropriately sized in length but inadequately sized for the tool's complexity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with 19 filter parameters and no output schema, the description is grossly incomplete. It fails to explain return values, query semantics, or the relationship between min/max parameter pairs, leaving the agent without sufficient context to invoke the tool effectively.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, establishing a baseline score. However, the description adds no value beyond the schema—no explanation of query composition (e.g., whether name and currency can be combined), valid value formats beyond what's in schema, or examples of common use cases.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'API Ninjas Country API endpoint' identifies the provider and domain (country) but fails to specify the action (retrieve, search, list). It essentially restates the tool name with provider context, functioning as a tautology without clarifying what operation is performed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance provided on when to use this tool versus alternatives, or how to construct valid queries from the 19 available parameters. With zero required parameters, the description offers no hints about minimum viable query patterns.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.0v1countryWith only one tool, there is no possibility for ambiguity or overlap between tools. The tool 'v1country' has a singular, clear purpose as described.
A single tool inherently has consistent naming, as there are no other tools to compare it against. The name 'v1country' follows a predictable pattern for an API endpoint.
One tool is too few for a server named 'Country By Api Ninjas MCP Server', which suggests a broader scope for country-related operations. A single endpoint feels thin and underdeveloped for this domain.
The tool surface is severely incomplete for a country API server. It lacks basic operations like searching countries, getting details by name or code, filtering by region, or any CRUD-like functionality, leaving obvious gaps.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
490+ economic & demographic indicators for 218 countries from IMF, World Bank, UN, FRED.
Query 29,500+ World Bank development indicators for 200+ countries across 60+ years.
Access World Bank development indicators for 200+ countries.
Macro data for AI agents: GDP, inflation, unemployment and more (World Bank, US BLS). No keys.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BACH-AI-Tools/country_by_api_ninjas'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
