API-Market MCP Server
Related Servers
Alternatives to API-Market MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA server that enables Large Language Models to discover and interact with REST APIs defined by OpenAPI specifications through the Model Context Protocol.3,228 npm294MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol Server that enables LLMs to interact with and execute REST API calls through natural language prompts, supporting GET/PUT/POST/PATCH operations on configured APIs.318 PyPI6Apache 2.0
- AlicenseNot gradedqualityBmaintenanceAn MCP server for API discovery and execution with a token-efficient search -> execute workflow over OpenAPI, Google Discovery, and optional native GraphQL and gRPC sources.69 npm12Apache 2.0
- AlicenseDqualityDmaintenanceA Model Context Protocol server that enables LLMs to explore and interact with API specifications by providing tools for loading, browsing, and getting detailed information about API endpoints.412 npm14ISC
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) Server that provides unified access to multiple external APIs (weather, news, financial data) through a single, consistent interface for AI agents and LLMs.1-
- AlicenseAqualityDmaintenanceA generic MCP server that dynamically exposes any OpenAPI-documented REST API to LLMs by auto-discovering endpoints. It provides tools for exploring API capabilities and making authenticated requests directly through natural language interfaces.25 npmMIT
TDQS
Scored across 34 tools
Multiple tools have overlapping or unclear boundaries, causing confusion. For example, 'best_route_bw_start_and_stop' and 'best_route_for_multiple_stops' both handle routing with similar purposes, while 'BridgeML_API', 'Coding_Assistant', and 'text-to-image' are vague and could be misselected. The set mixes distinct APIs (e.g., geocoding, search) with redundant or poorly differentiated tools.
Naming conventions are highly inconsistent, mixing styles like snake_case ('best_route_bw_start_and_stop'), CamelCase ('Get_ageing_gif_URL'), and kebab-case ('text-to-image'). Verbs vary widely (e.g., 'Check_domain_availability', 'Search_for_nearby_places', 'getWhoisInfo'), and some names are overly verbose or cryptic, lacking a predictable pattern across the toolset.
With 34 tools, the count is excessive for a single server, suggesting poor scoping. The tools cover disparate domains like routing, image processing, search, and APIs, making the set feel bloated and unfocused. A more coherent server would split these into multiple specialized servers, as the current scope is too broad for effective agent use.
The toolset covers various domains but has notable gaps in lifecycle coverage. For instance, in image processing, tools like 'Deblurer' and 'Get_Unblurred_Image_URL' exist, but other operations (e.g., image deletion or updates) are missing. Similarly, search tools are present but lack filtering or pagination options. While agents can perform basic tasks, the surface is incomplete for robust workflows.