Celebrity By Api Ninjas
# Celebrity By Api Ninjas MCP Server
[English](./README_EN.md) | 简体中文 | [繁體中文](./README_ZH-TW.md)
用于访问 Celebrity By Api Ninjas API 的 MCP 服务器。
## 🚀 使用 EMCP 平台快速体验
**[EMCP](https://sit-emcp.kaleido.guru)** 是一个强大的 MCP 服务器管理平台,让您无需手动配置即可快速使用各种 MCP 服务器!
### 快速开始:
1. 🌐 访问 **[EMCP 平台](https://sit-emcp.kaleido.guru)**
2. 📝 注册并登录账号
3. 🎯 进入 **MCP 广场**,浏览所有可用的 MCP 服务器
4. 🔍 搜索或找到本服务器(`bach-celebrity_by_api_ninjas`)
5. 🎉 点击 **"安装 MCP"** 按钮
6. ✅ 完成!即可在您的应用中使用
### EMCP 平台优势:
- ✨ **零配置**:无需手动编辑配置文件
- 🎨 **可视化管理**:图形界面轻松管理所有 MCP 服务器
- 🔐 **安全可靠**:统一管理 API 密钥和认证信息
- 🚀 **一键安装**:MCP 广场提供丰富的服务器选择
- 📊 **使用统计**:实时查看服务调用情况
立即访问 **[EMCP 平台](https://sit-emcp.kaleido.guru)** 开始您的 MCP 之旅!
---
## 简介
这是一个 MCP 服务器,用于访问 Celebrity By Api Ninjas API。
- **PyPI 包名**: `bach-celebrity_by_api_ninjas`
- **版本**: 1.0.0
- **传输协议**: stdio
## 安装
### 从 PyPI 安装:
```bash
pip install bach-celebrity_by_api_ninjas
```
### 从源码安装:
```bash
pip install -e .
```
## 运行
### 方式 1: 使用 uvx(推荐,无需安装)
```bash
# 运行(uvx 会自动安装并运行)
uvx --from bach-celebrity_by_api_ninjas bach_celebrity_by_api_ninjas
# 或指定版本
uvx --from bach-celebrity_by_api_ninjas@latest bach_celebrity_by_api_ninjas
```
### 方式 2: 直接运行(开发模式)
```bash
python server.py
```
### 方式 3: 安装后作为命令运行
```bash
# 安装
pip install bach-celebrity_by_api_ninjas
# 运行(命令名使用下划线)
bach_celebrity_by_api_ninjas
```
## 配置
### API 认证
此 API 需要认证。请设置环境变量:
```bash
export API_KEY="your_api_key_here"
```
### 环境变量
| 变量名 | 说明 | 必需 |
|--------|------|------|
| `API_KEY` | API 密钥 | 是 |
| `PORT` | 不适用 | 否 |
| `HOST` | 不适用 | 否 |
### 在 Cursor 中使用
编辑 Cursor MCP 配置文件 `~/.cursor/mcp.json`:
```json
{
"mcpServers": {
"bach-celebrity_by_api_ninjas": {
"command": "uvx",
"args": ["--from", "bach-celebrity_by_api_ninjas", "bach_celebrity_by_api_ninjas"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}
```
### 在 Claude Desktop 中使用
编辑 Claude Desktop 配置文件 `claude_desktop_config.json`:
```json
{
"mcpServers": {
"bach-celebrity_by_api_ninjas": {
"command": "uvx",
"args": ["--from", "bach-celebrity_by_api_ninjas", "bach_celebrity_by_api_ninjas"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}
```
## 可用工具
此服务器提供以下工具:
### `v1celebrity`
API Ninjas Celebrity API endpoint.
**端点**: `GET /v1/celebrity`
**参数**:
- `name` (string): Name of the celebrity you wish to search. This field is case-insensitive.
- `min_net_worth` (number): Minimum net worth of celebrities.
- `max_net_worth` (number): Maximum net worth of celebrities.
- `nationality` (string): Nationality of celebrities. Must be an ISO 3166 Alpha-2 country code (e.g. US).
- `min_height` (string): Minimum height of celebrities in meters (e.g. 1.65).
- `max_height` (string): Maximum height of celebrities in meters (e.g. 1.80).
---
## 技术栈
- **传输协议**: stdio
- **HTTP 客户端**: httpx
## 许可证
MIT License - 详见 [LICENSE](./LICENSE) 文件。
## 开发
此服务器由 [API-to-MCP](https://github.com/BACH-AI-Tools/api-to-mcp) 工具生成。
版本: 1.0.0
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to compare it to. The single tool's purpose is clearly defined as accessing the Celebrity API endpoint, leaving no room for confusion.
Since there is only one tool, naming consistency is inherently perfect. There are no other tool names to compare against, so no inconsistencies can arise in patterns or conventions.
A single tool is generally too few for most server purposes, as it limits functionality and may indicate an incomplete or thin interface. For a celebrity API, one tool might cover basic queries but lacks operations like search, filtering, or detailed retrieval, making it feel under-scoped.
Inferring the domain as celebrity information access, a single endpoint is severely incomplete. It likely provides only basic data without support for operations like searching by name, filtering by category, or updating information, leading to significant gaps that could hinder agent workflows.