City By Api Ninjas MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | 不适用 (Not applicable) | |
| PORT | No | 不适用 (Not applicable) | |
| API_KEY | Yes | API 密钥 (API Key for City 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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| v1cityD | API Ninjas City 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 ambiguity or overlap between tools. The tool 'v1city' stands alone with a clear purpose, so agents cannot misselect between multiple options.
A single tool inherently has consistent naming, as there are no other tools to compare it against. The name 'v1city' follows a pattern that includes versioning and the resource, which is straightforward and predictable in isolation.
One tool is too few for a server named 'City By Api Ninjas MCP Server', which suggests a domain focused on city-related data. A single endpoint limits functionality and feels thin, as typical city APIs might include operations like search, get details, or list cities, not just one endpoint.
The server's purpose implies city data operations, but with only one tool ('v1city'), the surface is severely incomplete. There are obvious gaps, such as missing CRUD operations or specific queries, which will likely cause agent failures when trying to perform comprehensive city-related tasks.