Skip to main content
Glama
BACH-AI-Tools

City By Api Ninjas MCP Server

by BACH-AI-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to City By Api Ninjas MCP Server

No user-submitted related servers found.

    Related Servers

    • Geodb Cities MCP Server

      BACH-AI-Tools
      A
      license
      B
      quality
      D
      maintenance
      Provides access to the GeoDB Cities API for retrieving global geographic data including city details, populations, and local time. It enables users to find nearby locations, calculate distances between places, and browse administrative divisions across countries.
      18
      MIT

    • Country By Api Ninjas MCP

      BACH-AI-Tools
      A
      license
      C
      quality
      D
      maintenance
      Provides access to the API Ninjas Country API, allowing users to query detailed country data including GDP, population, area, and other demographic metrics. It enables filtering countries by specific economic and geographic criteria through natural language commands.
      1
      MIT

    • weather_mcp_server

      Manish-Kumar148
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time and historical weather data for any city worldwide, including forecasts, air quality, and marine conditions, using the free Open-Meteo API.
      5 npm
      MIT

    • Weather By Api Ninjas

      BACH-AI-Tools
      A
      license
      C
      quality
      D
      maintenance
      Provides access to weather information by location using the API Ninjas Weather API, supporting queries by coordinates, zip code, city, state, and country.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.2/5.0

    Scored across 1 tool

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources