invompt-healthlisted

# Invompt MCP Health Treat the Invompt MCP provider already exposed by the host as the only runtime dependency. Never inspect a repository, configuration file, environment variable, process, or URL as a fallback, and never switch to another endpoint. ## Check the active provider 1. Find the active provider from host MCP provenance. Prefer the logical name `invompt`, but do not guess when more than one registration is plausible. 2. Let the host initialize the provider and discover its live tools. 3. Resolve the provider tool whose server-side name is `ping`, read its live schema, and invoke it with only schema-valid arguments. 4. Treat the result as healthy only when transport, protocol, and tool result all succeed and any explicit health status is positive. 5. If the initialized provider advertises resources, read `invompt://docs/getting-started` only when that exact public resource is listed. A missing optional resource does not fail a successful `ping`. Do not list or read invoices, clients, settings, or other business data for a health check. Do not call mutations. `ping` is required health evidence and is not a substitute for the separate user-acceptance test of a real read-only business operation. Health is intentionally not a creation preflight. A successful `ping` does not authorize `create_invoice`, and an advertised tool list does not prove call-time authorization. Creation requests must use the invoice skill's one-pass effective-provider and requ