Skip to main content
Glama
davidmosiah

99 MCP

by davidmosiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to 99 MCP

No user-submitted related servers found.

    Related Servers

    • robotaxi-mcp

      nathanielangafor
      A
      license
      A
      quality
      C
      maintenance
      Enables agents to search places, get live fares and route previews, list payment methods, book rides, monitor ride and vehicle status, preview and confirm cancellations, and retrieve ride history for Tesla Robotaxi rider accounts.
      8
      MIT

    • ifood-mcp

      davidmosiah
      A
      license
      C
      quality
      A
      maintenance
      Enables AI agents to access iFood orders, addresses, restaurants, and cart locally, with fail-closed checkout requiring explicit opt-in.
      33
      54 npm
      MIT

    • AgentPay MCP Server

      Rumblingb
      F
      license
      Not graded
      quality
      A
      maintenance
      Provides a trust and governance layer for AI agents, enabling secure API access, credential vaulting, paid execution with human approval, and automatic call resume.
      5 npm
      2
      -

    • AI Service Gateway MCP

      Yormede
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to securely access authenticated services (HTTP, SSH, SMTP) without exposing secrets, by acting as a server-side proxy that injects authentication.
      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

    B3.3/5.0

    Scored across 14 tools

    Disambiguation2/5

    Several tools have unclear boundaries: ninenine_estimate and ninenine_multi_estimate both provide fare estimates, while ninenine_track_ride, ninenine_active_ride, and ninenine_driver_track all relate to ride status tracking. Descriptions clarify some differences, but an agent could easily select the wrong tool.

    Naming Consistency3/5

    All tools share the ninenine_ prefix and snake_case style, but the pattern after the prefix is inconsistent: some are noun phrases like ninenine_ride_categories and ninenine_ride_history, while others are verb phrases like ninenine_track_ride and ninenine_request_ride. The naming is readable but not uniform.

    Tool Count4/5

    14 tools is within a reasonable range for a ride-hailing MCP server. A few tools overlap or feel redundant, like ninenine_active_ride duplicating ninenine_track_ride without an id, but overall the count is not excessive.

    Completeness4/5

    The server covers the core ride-hailing lifecycle: estimate, request, track, cancel, plus history, addresses, categories, and safety/audit tools. Minor gaps exist around payment methods and driver details, but these may be intentionally gated.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources