JustOneAPI MCP Server
OfficialRelated Servers
Alternatives to JustOneAPI MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients to call the platform's full API as individual tools—covering evals, criteria, gates, logs, datasets, aliases, label sets, audit/proving, dedicated endpoints, and training—with validated inputs and raw API responses.81252 npmApache 2.0
- FlicenseCqualityDmaintenanceEnables interaction with the OpenData Platform API by dynamically exposing all endpoints as MCP tools with typed input schemas and HTTP handlers.99-
- FlicenseAqualityBmaintenanceExposes read-only GoCanvas API v3 endpoints as MCP tools, enabling listing and retrieval of forms, submissions, reports, and reference data.16-
- AlicenseNot gradedqualityDmaintenanceExposes the UniFi Network Integration API as MCP tools, dynamically loaded from JSON manifests, with read-only mode by default.MIT
- FlicenseNot gradedqualityDmaintenanceEnables users to expose arbitrary HTTP APIs as configurable MCP tools by defining tool specifications in a JSON configuration file.1,456 npm3-
- AlicenseNot gradedqualityDmaintenanceProvides a standardized MCP interface for interacting with Shopify tools and services, enabling unified API access and compatibility with MCP-compliant clients.1MIT
TDQS
Scored across 7 tools
Each tool has a clearly distinct role: discovery, schema retrieval, invocation, account balance, usage analytics, platform listing, and catalog refresh. The two account-related tools are separated by balance vs. spending trends, and the sequential workflow tools explicitly reference each other.
All tool names follow a consistent verb_noun snake_case pattern: search_, get_, call_, list_, refresh_. There are no mixed naming conventions or vague verbs, making the set predictable and easy to navigate.
Seven tools is well-scoped for an API aggregation/catalog service. Each tool supports a necessary part of the workflow or administrative/maintenance need without redundant or filler tools.
The core workflow is fully covered: search for endpoints, retrieve their schema, call them, and check account balance/usage afterward. Platform listing and catalog refresh round out the surface with no obvious dead ends or missing lifecycle steps.