Skip to main content
Glama
j7018515

ibronevik-taxi-mcp

by j7018515
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ibronevik-taxi-mcp

No user-submitted related servers found.

    Related Servers

    • relay

      future-beat
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to drive Relay, an AI support-triage agent, by exposing tools for customer lookup, documentation search, ticket classification, reply, and escalation, with full guardrails and read-only mode option.
      7
      MIT

    • ubeats-bo-mcp

      naranmunkh
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides tool-based access to the UBEats Backoffice API (reports, orders, and catalog) with automatic Keycloak SSO authentication, enabling users to query delivery and financial data via natural language.
      -

    • Agentic Travel Recommendations

      Varma904
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for agentic travel recommendations, exposing tools to retrieve member profiles and personalized travel recommendations with partner-specific rules and policies.
      -

    • mendix-mcp-server

      dhanavel-013
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to read and modify Mendix application models through MCP tools for creating modules, entities, pages, microflows, deploying, and querying runtime data.
      1
      -

    • nexwave-mcp-remote

      Sidarau
      F
      license
      A
      quality
      B
      maintenance
      Enables AI agents to rent cars and manage a Sketchy Rides fleet via MCP, with public read-only tools and OAuth-gated operator tools.
      5
      -
    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

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool addresses a separate concern: backend status, reference catalog listing, reference content retrieval, and authentication. There is no functional overlap between them.

    Naming Consistency3/5

    All tools share the taxi_ prefix bind underscores, but the structure varies: taxi_status is a plain noun, taxi_reference_list is a noun compound, and taxi_reference_get puts the verb after the noun. This is readable but not a consistent verb_noun convention.

    Tool Count5/5

    Four tools cover the narrow scope of the server without redundancy. Each one has a clear role, and the count feels neither thin nor bloated.

    Completeness3/5

    The reference data use-case is covered with list and get operations, but authenticate is a standalone capability that no other tool consumes, since all references are public. The set feels slightly incomplete around authenticated actions.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources