Skip to main content
Glama
BACH-AI-Tools

Celebrity By Api Ninjas

by BACH-AI-Tools
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Celebrity By Api Ninjas MCP Server

English | 简体中文 | 繁體中文

用于访问 Celebrity By Api Ninjas API 的 MCP 服务器。

🚀 使用 EMCP 平台快速体验

EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！

快速开始：

  1. 🌐 访问 EMCP 平台

  2. 📝 注册并登录账号

  3. 🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器

  4. 🔍 搜索或找到本服务器（bach-celebrity_by_api_ninjas）

  5. 🎉 点击 "安装 MCP" 按钮

  6. ✅ 完成！即可在您的应用中使用

EMCP 平台优势：

  • ✨ 零配置：无需手动编辑配置文件

  • 🎨 可视化管理：图形界面轻松管理所有 MCP 服务器

  • 🔐 安全可靠：统一管理 API 密钥和认证信息

  • 🚀 一键安装：MCP 广场提供丰富的服务器选择

  • 📊 使用统计：实时查看服务调用情况

立即访问 EMCP 平台 开始您的 MCP 之旅！

Related MCP server: Exercises By Api Ninjas MCP Server

简介

这是一个 MCP 服务器，用于访问 Celebrity By Api Ninjas API。

  • PyPI 包名: bach-celebrity_by_api_ninjas

  • 版本: 1.0.0

  • 传输协议: stdio

安装

从 PyPI 安装:

pip install bach-celebrity_by_api_ninjas

从源码安装:

pip install -e .

运行

方式 1: 使用 uvx（推荐，无需安装）

# 运行（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: 直接运行（开发模式）

python server.py

方式 3: 安装后作为命令运行

# 安装
pip install bach-celebrity_by_api_ninjas

# 运行（命令名使用下划线）
bach_celebrity_by_api_ninjas

配置

API 认证

此 API 需要认证。请设置环境变量:

export API_KEY="your_api_key_here"

环境变量

变量名

说明

必需

API_KEY

API 密钥

是

PORT

不适用

否

HOST

不适用

否

在 Cursor 中使用

编辑 Cursor MCP 配置文件 ~/.cursor/mcp.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:

{
  "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 文件。

开发

此服务器由 API-to-MCP 工具生成。

版本: 1.0.0

Available Tools

1 tool
v1celebrityD

API Ninjas Celebrity API endpoint.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameNoName of the celebrity you wish to search. This field is case-insensitive.
min_net_worthNoMinimum net worth of celebrities.0
max_net_worthNoMaximum net worth of celebrities.0
nationalityNoNationality of celebrities. Must be an ISO 3166 Alpha-2 country code (e.g. US).
min_heightNoMinimum height of celebrities in meters (e.g. 1.65).
max_heightNoMaximum height of celebrities in meters (e.g. 1.80).

TDQS

D1.7/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden for behavioral disclosure. The description reveals nothing about how the tool behaves - no information about whether it's a read or write operation, what authentication is required, rate limits, error behavior, or what kind of data it returns. For a tool with 6 parameters and no annotations, this represents a complete failure to disclose behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While technically concise (only 5 words), this is under-specification rather than effective conciseness. The single sentence fails to convey essential information about the tool's purpose and usage. Every sentence should earn its place, but this sentence provides almost no value beyond what's already in the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a tool with 6 parameters, no annotations, and no output schema, the description is completely inadequate. It fails to explain what the tool does, how to use it, what it returns, or any behavioral characteristics. The description doesn't compensate for the lack of structured metadata, leaving the agent with insufficient information to effectively use this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, meaning all parameters are well-documented in the schema itself. The description adds zero additional information about parameters - it doesn't explain relationships between parameters, provide examples of combined usage, or clarify the overall search logic. With complete schema coverage, the baseline is 3 even without parameter information in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'API Ninjas Celebrity API endpoint' is tautological - it restates the tool name 'v1celebrity' without explaining what it actually does. It mentions 'Celebrity API' but doesn't specify the action (search, retrieve, list, etc.) or what resource it operates on beyond the generic 'endpoint' reference. There's no clear verb+resource combination that defines the tool's function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides absolutely no guidance on when to use this tool. There's no mention of use cases, prerequisites, or alternative approaches. With no sibling tools mentioned, the bar is lower, but the description fails to give any context about appropriate usage scenarios or limitations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool update
    • First observedv1celebrity
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.2/5.0
Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness2/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

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/celebrity_by_api_ninjas'

If you have feedback or need assistance with the MCP directory API, please join our Discord server