GPTProto MCP
OfficialRelated Servers
Alternatives to GPTProto MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables 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.2MIT

gliana-mcp-remoteofficial
AlicenseNot gradedqualityBmaintenanceHosted MCP server for browsing the GlianaAI model catalog with zero setup, providing model listings, pricing, and schema information via Streamable HTTP.MIT- AlicenseAqualityNot gradedmaintenanceEnables AI assistants to discover, retrieve details about, and manage MCP (Model Context Protocol) servers that provide additional tools and capabilities on demand.563 npm10-
- AlicenseNot gradedqualityAmaintenanceEnables local AI models to be used through MCP, exposing tools for coding assistance, code review, model listing, status checks, and benchmarking.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to access a unified catalog of tools from various APIs (OpenAPI, GraphQL, MCP, Google Discovery) through the MCP protocol.MIT
- FlicenseAqualityCmaintenanceEnables browsing Hedra's model catalog and managing AI generation jobs, including submitting, polling, and uploading files, through MCP clients.14-
TDQS
Scored across 9 tools
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.
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).
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.
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.