Skip to main content
Glama
gptproto-ai

GPTProto MCP

Official
by gptproto-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to GPTProto MCP

No user-submitted related servers found.

    Related Servers

    • McpHub

      John0King
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI tools to uniformly discover, inspect, and call tools, prompts, and resources from multiple upstream MCP servers through a small set of fixed MCP tools, over stdio or HTTP.
      2
      MIT

    • Kyma API MCP Server

      kyma-api
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to browse a live catalog of 100+ models with pricing, rankings and measured uptime, check credits and spend, and send chat completions through an OAuth-authenticated, per-connection key capped by a spend limit. Read tools are free, and paid calls are priced and approved before any credit is used.
      MIT

    • Relay

      adarshp14
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to access a unified catalog of tools from various APIs (OpenAPI, GraphQL, MCP, Google Discovery) through the MCP protocol.
      6 npm
      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

    A3.7/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools are clearly distinct, but task_get and task_wait both handle interrupted operations and could be confused at a glance. custom_create and request also overlap in submitting native API bodies, though descriptions clarify the specific use case.

    Naming Consistency4/5

    All tools share the gptproto_ prefix, which is consistent, but the remaining pattern mixes noun-only names (status, pricing, request) with noun_action names (models_list, model_describe, task_get). Singular/plural usage is inconsistent (models_list vs task_get vs tasks_list).

    Tool Count5/5

    Nine tools is well-scoped for an API client covering status, models, pricing, request execution, and task management. Each tool has a clear role and none feel redundant.

    Completeness4/5

    The tool surface covers the core lifecycle of discovering models, pricing, making requests, and managing async tasks. Minor gaps exist, such as no explicit task cancellation or file upload tool, despite status checking upload capability.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources