Facts By API Ninjas MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host configuration (Not applicable/Optional) | |
| PORT | No | Port configuration (Not applicable/Optional) | |
| API_KEY | Yes | API 密钥 (API Key for Facts By Api Ninjas) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| v1factsC | API Ninjas Facts API endpoint |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.