Recipe By Api Ninjas MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Optional host (not applicable for stdio transport) | |
| PORT | No | Optional port (not applicable for stdio transport) | |
| API_KEY | Yes | API 密钥 (API key required for authentication) |
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 |
|---|---|
| v1recipeA | Get a list of recipes for a given search query. Returns at most 10 results. To access more than the first 10 results, use the offset parameter to offset results in multiple API calls. |
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 a single tool, there is no possibility of confusion or overlap. The tool's purpose is uniquely defined.
There is only one tool, so naming consistency is trivially perfect. The name 'v1recipe' is a single, clear identifier without mixed conventions.
Having only one tool is too few for the apparent scope of a recipe server. Typical recipe APIs require multiple endpoints (search, get by ID, etc.), and a single tool feels thin and insufficient.
The server only provides a search/list function. Missing essential operations like getting a specific recipe, creating, updating, or deleting recipes. This is a significant gap for a recipe management server.