decixa-mcp
Related Servers
Alternatives to decixa-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to explore, search, and query API definitions from OpenAPI/Swagger JSON files.5 npmMIT
- AlicenseAqualityDmaintenanceMCP server for OmniStream marketplace that lets AI assistants discover and call any marketplace API directly.757 npmMIT
- 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.97 npm14Apache 2.0
- AlicenseNot gradedqualityCmaintenanceA unified MCP server providing AI agents with 40+ developer APIs including geolocation, crypto prices, DNS lookup, and web scraping. Enables natural language access to various tools through a single gateway.1MIT

opendexterofficial
AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to search, pay for, and call paid APIs using the x402 protocol, with automatic USDC settlement.2MIT
deAPI MCP Serverofficial
AlicenseAqualityBmaintenanceOfficial MCP server for deAPI. 39 tools for image and video generation, image editing, background removal and upscaling, text-to-speech, music generation, transcription of audio, video files and video links, OCR, video description and embeddings. Requires a deAPI API key.481MIT
TDQS
Scored across 6 tools
The core tools (discover, resolve, get_api_detail, get_index) have distinct purposes, but the presence of deprecated aliases (browse_apis, search_apis) that mirror functionalities introduces ambiguity. The deprecation notices help, but agents may still select the wrong tool without careful reading.
Tool names mix conventions: some are single verbs ('discover', 'resolve'), some use 'get_' prefix ('get_api_detail', 'get_index'), and others follow verb_noun pattern ('browse_apis', 'search_apis'). While still readable, the inconsistency could confuse agents expecting a uniform pattern.
With 6 tools (2 deprecated), the effective count is 4 core tools, which is appropriate for API discovery and details. The scope is well-focused, and the tools are not excessive.
The set covers key operations: listing (discover), best-match selection (resolve), detailed information (get_api_detail), and platform overview (get_index). There are no obvious gaps for the stated purpose of API discovery and inspection.