A
licenseNot graded
qualityD
maintenanceAn MCP server that enables AI agents to explore, search, and query API definitions from OpenAPI/Swagger JSON files.
10 npm
MIT
decixa-mcp
Related Servers
Alternatives to decixa-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for OmniStream marketplace that lets AI assistants discover and call any marketplace API directly.739 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.60 npm12Apache 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- AlicenseAqualityAmaintenanceMCP server that gives AI agents paid access to Invoket APIs, with discovery-driven tools, spending caps, and non-custodial payments via x402.707 npm1MIT
TDQS
A4/5.0
Scored across 6 tools
Disambiguation3/5
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.
Naming Consistency3/5
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.
Tool Count4/5
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.
Completeness4/5
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.
Maintenance
ActivityInactive
ResponsivenessNo issues