Facts By API Ninjas MCP Server
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., "@Facts By API Ninjas MCP ServerGive me 3 interesting facts"
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.
Facts By Api Ninjas MCP Server
用于访问 Facts By Api Ninjas API 的 MCP 服务器。
🚀 使用 EMCP 平台快速体验
EMCP 是一个强大的 MCP 服务器管理平台,让您无需手动配置即可快速使用各种 MCP 服务器!
快速开始:
🌐 访问 EMCP 平台
📝 注册并登录账号
🎯 进入 MCP 广场,浏览所有可用的 MCP 服务器
🔍 搜索或找到本服务器(
bach-facts_by_api_ninjas)🎉 点击 "安装 MCP" 按钮
✅ 完成!即可在您的应用中使用
EMCP 平台优势:
✨ 零配置:无需手动编辑配置文件
🎨 可视化管理:图形界面轻松管理所有 MCP 服务器
🔐 安全可靠:统一管理 API 密钥和认证信息
🚀 一键安装:MCP 广场提供丰富的服务器选择
📊 使用统计:实时查看服务调用情况
立即访问 EMCP 平台 开始您的 MCP 之旅!
Related MCP server: Jokes By Api Ninjas
简介
这是一个 MCP 服务器,用于访问 Facts By Api Ninjas API。
PyPI 包名:
bach-facts_by_api_ninjas版本: 1.0.0
传输协议: stdio
安装
从 PyPI 安装:
pip install bach-facts_by_api_ninjas从源码安装:
pip install -e .运行
方式 1: 使用 uvx(推荐,无需安装)
# 运行(uvx 会自动安装并运行)
uvx --from bach-facts_by_api_ninjas bach_facts_by_api_ninjas
# 或指定版本
uvx --from bach-facts_by_api_ninjas@latest bach_facts_by_api_ninjas方式 2: 直接运行(开发模式)
python server.py方式 3: 安装后作为命令运行
# 安装
pip install bach-facts_by_api_ninjas
# 运行(命令名使用下划线)
bach_facts_by_api_ninjas配置
API 认证
此 API 需要认证。请设置环境变量:
export API_KEY="your_api_key_here"环境变量
变量名 | 说明 | 必需 |
| API 密钥 | 是 |
| 不适用 | 否 |
| 不适用 | 否 |
在 Cursor 中使用
编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:
{
"mcpServers": {
"bach-facts_by_api_ninjas": {
"command": "uvx",
"args": ["--from", "bach-facts_by_api_ninjas", "bach_facts_by_api_ninjas"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}在 Claude Desktop 中使用
编辑 Claude Desktop 配置文件 claude_desktop_config.json:
{
"mcpServers": {
"bach-facts_by_api_ninjas": {
"command": "uvx",
"args": ["--from", "bach-facts_by_api_ninjas", "bach_facts_by_api_ninjas"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}可用工具
此服务器提供以下工具:
v1facts
API Ninjas Facts API endpoint
端点: GET /v1/facts
参数:
limit(number): How many results to return. Must be between 1 and 30. Default is 1.
技术栈
传输协议: stdio
HTTP 客户端: httpx
许可证
MIT License - 详见 LICENSE 文件。
开发
此服务器由 API-to-MCP 工具生成。
版本: 1.0.0
Available Tools
1 toolv1factsC
API Ninjas Facts API endpoint
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many results to return. Must be between 1 and 30. Default is 1. | 0 |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose any behavioral traits such as whether this is a read-only operation, any rate limits, or side effects. It merely states it is an API endpoint.
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 very short but lacks substance. It is under-specified and does not convey sufficient information in a structured way. It is not concise in a helpful manner.
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?
Given the simplicity of the tool (one optional param, no output schema, no siblings), the description should at least mention the data returned or the purpose. It fails to provide complete context for an agent to use it 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?
The input schema has a single optional parameter 'limit' with full description coverage, so the baseline is 3. The tool description adds no additional meaning beyond what the schema already provides.
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 Facts API endpoint' indicates this is an endpoint for facts, but it is vague and does not specify the exact action (e.g., retrieve facts, manage facts). The tool name 'v1facts' suggests it is a versioned facts API, but the description lacks a clear verb.
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 is provided on when to use this tool. There are no sibling tools, so no differentiation is needed, but the description does not explain the context or benefits of using this endpoint.
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 tool update
v1.0.0- First observed
v1facts
TDQS
With only one tool, there is no possibility of confusion or overlap. The single tool 'v1facts' is uniquely defined.
The single tool name uses a consistent 'v1' prefix and descriptive noun. No inconsistency possible with one tool.
One tool is too few for a server named 'Facts By API Ninjas'. A facts API typically offers multiple endpoints (e.g., random, search, categories), making this feel undersized.
The server provides no CRUD operations, no categorization, no search. It simply fetches an undefined 'fact', leaving major gaps for any realistic fact-related task.
Maintenance
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
Check whether a real-world fact can be verified before an agent acts on it. Free, no auth.
Gateway between LLM agents and world data through eight tools and a bundled endpoint catalog.
- TalarionOAuthcom.talarion
Give LLMs an accurate, up-to-date picture of the world — the high-surprisal facts they miss.
A Model Context Protocol server for Wix AI tools
Related MCP Servers
- AlicenseCqualityDmaintenanceEnables access to the Chuck Norris API to retrieve Chuck Norris jokes and facts through a Model Context Protocol interface.1MIT
- AlicenseCqualityDmaintenanceEnables users to fetch random jokes from the API Ninjas Jokes API. Supports retrieving 1-30 jokes per request through a simple interface.1MIT
- FlicenseNot gradedqualityDmaintenanceProvides access to the Nager.Date API through the Model Context Protocol, allowing AI agents to query worldwide public holiday information. It enables seamless integration of holiday data into LLM workflows using standardized tools.-
- AlicenseNot gradedqualityCmaintenanceProvides natural language inference (NLI) capabilities via the Model Context Protocol, allowing AI agents to verify factual consistency and detect contradictions in text.3MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/facts_by_api_ninjas'
If you have feedback or need assistance with the MCP directory API, please join our Discord server