Riddles 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., "@Riddles By Api Ninjas MCP Servergive me 5 riddles to solve"
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.
Riddles By Api Ninjas MCP Server
用于访问 Riddles By Api Ninjas API 的 MCP 服务器。
🚀 使用 EMCP 平台快速体验
EMCP 是一个强大的 MCP 服务器管理平台,让您无需手动配置即可快速使用各种 MCP 服务器!
快速开始:
🌐 访问 EMCP 平台
📝 注册并登录账号
🎯 进入 MCP 广场,浏览所有可用的 MCP 服务器
🔍 搜索或找到本服务器(
bach-riddles_by_api_ninjas)🎉 点击 "安装 MCP" 按钮
✅ 完成!即可在您的应用中使用
EMCP 平台优势:
✨ 零配置:无需手动编辑配置文件
🎨 可视化管理:图形界面轻松管理所有 MCP 服务器
🔐 安全可靠:统一管理 API 密钥和认证信息
🚀 一键安装:MCP 广场提供丰富的服务器选择
📊 使用统计:实时查看服务调用情况
立即访问 EMCP 平台 开始您的 MCP 之旅!
Related MCP server: Quotes By Api Ninjas MCP Server
简介
这是一个 MCP 服务器,用于访问 Riddles By Api Ninjas API。
PyPI 包名:
bach-riddles_by_api_ninjas版本: 1.0.0
传输协议: stdio
安装
从 PyPI 安装:
pip install bach-riddles_by_api_ninjas从源码安装:
pip install -e .运行
方式 1: 使用 uvx(推荐,无需安装)
# 运行(uvx 会自动安装并运行)
uvx --from bach-riddles_by_api_ninjas bach_riddles_by_api_ninjas
# 或指定版本
uvx --from bach-riddles_by_api_ninjas@latest bach_riddles_by_api_ninjas方式 2: 直接运行(开发模式)
python server.py方式 3: 安装后作为命令运行
# 安装
pip install bach-riddles_by_api_ninjas
# 运行(命令名使用下划线)
bach_riddles_by_api_ninjas配置
API 认证
此 API 需要认证。请设置环境变量:
export API_KEY="your_api_key_here"环境变量
变量名 | 说明 | 必需 |
| API 密钥 | 是 |
| 不适用 | 否 |
| 不适用 | 否 |
在 Cursor 中使用
编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:
{
"mcpServers": {
"bach-riddles_by_api_ninjas": {
"command": "uvx",
"args": ["--from", "bach-riddles_by_api_ninjas", "bach_riddles_by_api_ninjas"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}在 Claude Desktop 中使用
编辑 Claude Desktop 配置文件 claude_desktop_config.json:
{
"mcpServers": {
"bach-riddles_by_api_ninjas": {
"command": "uvx",
"args": ["--from", "bach-riddles_by_api_ninjas", "bach_riddles_by_api_ninjas"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}可用工具
此服务器提供以下工具:
v1riddles
API Ninjas Riddles API endpoint. Returns one or more random riddles.
端点: GET /v1/riddles
参数:
limit(number): Number of results to return. Must be between 1 and 20. Default is 1.
技术栈
传输协议: stdio
HTTP 客户端: httpx
许可证
MIT License - 详见 LICENSE 文件。
开发
此服务器由 API-to-MCP 工具生成。
版本: 1.0.0
Available Tools
1 toolv1riddlesC
API Ninjas Riddles API endpoint. Returns one or more random riddles.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of results to return. Must be between 1 and 20. Default is 1. | 0 |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions returning random riddles but fails to describe key traits like rate limits, authentication needs, error handling, or the randomness mechanism. This leaves significant gaps for a tool that interacts with an external API.
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 and front-loaded, consisting of two sentences that directly state the tool's purpose. It avoids unnecessary details, though it could be slightly more structured by explicitly mentioning the parameter or output, but overall it's efficient.
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 lack of annotations and output schema, the description is incomplete. It does not explain return values, error cases, or behavioral aspects like API constraints. For a tool with external dependencies, this leaves the agent under-informed about how 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 schema description coverage is 100%, with the 'limit' parameter fully documented in the schema. The description does not add any meaning beyond the schema, such as explaining the impact of 'limit' on randomness or output format. Baseline 3 is appropriate as the schema handles parameter documentation adequately.
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 clearly states the action ('Returns') and resource ('one or more random riddles'), specifying it's from the 'API Ninjas Riddles API endpoint'. It's specific about what the tool does, though there are no sibling tools to differentiate from, which prevents a perfect score.
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?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or context for invocation. It lacks explicit usage instructions, such as scenarios for fetching riddles or handling the 'limit' parameter, leaving the agent without operational context.
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
v1riddles
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as fetching random riddles, leaving no room for confusion or misselection.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'v1riddles' follows a single pattern, and there are no other tools to compare it against for inconsistency.
A single tool is too few for a server focused on riddles, as it lacks basic operations like getting riddles by category, difficulty, or ID. This minimal scope limits functionality and makes the server feel incomplete for its apparent domain.
The tool surface is severely incomplete for a riddles domain. It only supports fetching random riddles, missing essential operations such as retrieving specific riddles, filtering by parameters, or managing user interactions. This creates significant gaps that will hinder agent workflows.
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
Get a random dad joke or search by keyword to fit any moment. Retrieve specific jokes by ID for re…
API Ninjas MCP — wraps the multi-endpoint API Ninjas data API (api-ninjas.com)
Build, publish and analyze quizzes, polls, forms and personality tests. Riddle account required.
NumbersAPI MCP — wraps numbersapi.com (free, no auth)
Related MCP Servers
- AlicenseBqualityDmaintenanceProvides access to API Ninjas Random Word API to generate random words by type (noun, verb, adjective, adverb) for creative writing, games, and language learning applications.1MIT
- AlicenseBqualityDmaintenanceEnables retrieval of random inspirational quotes from various categories including age, art, business, courage, education, friendship, happiness, leadership, and many more through the API Ninjas Quotes API.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 tools to fetch random or categorized riddles, verify answers, and view riddle statistics. It supports communication via HTTP and SSE for seamless integration with AI agents.-
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/bachai-riddles-by-api-ninjas'
If you have feedback or need assistance with the MCP directory API, please join our Discord server