No user-submitted related servers found.
Scored across 34 tools
The 18 qm_data_* endpoints are clearly distinct by subject (weather, time, dns, fx, etc.), but several non-data clusters overlap: qm_probe_endpoint (free liveness probe) vs qm_data_httpcheck (paid status/headers/timing) do essentially the same job, and qm_scrub / qm_second_opinion / qm_clinic_diagnose / qm_clinic_checkup all occupy the 'check this for risk' space. The thorough descriptions do a good job steering selection, and qm_helped vs qm_clinic_stats is explicitly disambiguated, but the boundaries require reading prose rather than being self-evident from names.
Nearly everything is qm_ + snake_case, which is predictable and readable. The one inconsistency is structural: the paid data endpoints add a qm_data_ namespace tier while the sleep/lyrics tools do not (qm_sleep_queue, qm_lyrics_get vs qm_data_weather), and verb/noun order varies (qm_lyrics_get vs qm_validate_machine_files). Minor deviations rather than chaos.
34 tools is well past the comfortable range and reflects several distinct products bundled into one server (free clinic/attest utilities, a 18-endpoint paid data marketplace, a music/sleep catalog, and payment plumbing). Each tool does earn its place individually, but the sheer surface makes it hard to hold the whole set in context and invites misfires.
Core lifecycles are covered: discovery (qm_catalog), payment (qm_buy), fulfillment via the two-phase data/purchase tools, the attest/verify pair, and clinic diagnose/checkup/stats. Gaps are minor — the two-phase payment tools have no discoverable 'fulfill' companion beyond re-calling with payment, and there is no update/delete analog for catalog items, but that is by design for a read-only commerce surface.
