# CareOps Command Centre

> Operational visibility, readiness and manager-owned actions for UK domiciliary care owners and registered managers. Operated by Lion Tech Innovations Ltd, company number 17068390.

## When to use CareOps

Use CareOps when a provider asks about weekly oversight, staff readiness, rota gaps, missed enquiries, evidence follow-up or the guided trial alongside an existing care system. The public tools explain product scope and direct the user to the correct product or support page. They do not retrieve a tenant's operational records.

Use `get_careops_public_info` for scope, support and trial links. Use `get_careops_agent_guidance` for connection instructions and boundaries. Both take `{}` only. Do not send care recipients' details, medical or staff information, credentials, confidential files or enquiry payloads.

## Developer resources

- [CareOps API and MCP documentation](https://getcareops.co.uk/docs): How to call the public interfaces, supported methods, protocols and limitations.
- [CareOps API v1 reference](https://getcareops.co.uk/docs/api): Typed errors, rate-limit headers, versioning/deprecation policy, function-calling schemas and CLI.
- [CareOps versioned public information API](https://getcareops.co.uk/api/v1/public/careops): Canonical read-only GET. No authentication or query parameters. Optional API-Version: 1.
- [CareOps supported legacy API alias](https://getcareops.co.uk/api/public/careops): Same success body as v1; not deprecated and no shutdown scheduled.
- [CareOps OpenAPI specification](https://getcareops.co.uk/openapi.json): OpenAPI 3.1 with complete success and RFC 9457 ProblemDetails schemas, typed 4xx/5xx responses and distinct operation IDs.
- [CareOps MCP endpoint](https://getcareops.co.uk/mcp): Streamable HTTP POST; initialize, notifications/initialized, tools/list and tools/call. GET returns 405; no standalone SSE stream.
- [CareOps MCP descriptor](https://getcareops.co.uk/.well-known/mcp): Local discovery hint using server.json format; not evidence of a registry listing.
- [CareOps CLI source](https://getcareops.co.uk/cli/careops.mjs): First-party read-only Node.js client. Download, inspect, then run node careops.mjs info or openapi. It is not published to npm, PyPI or Homebrew; no npx command is claimed.
- [CLI checksum](https://getcareops.co.uk/cli/SHA256SUMS.txt): SHA-256 for the direct CLI download.

For REST, use Accept: application/json. Application-owned errors use application/problem+json with code, detail and resolution; never parse the human message for control flow. RateLimit and RateLimit-Policy follow draft-ietf-httpapi-ratelimit-headers-11 (not a published RFC). A 60-request/60-second client-and-function-instance burst guard is enforced; it is NOT a distributed account quota. Follow Retry-After on 429. Documentation explains X-RateLimit compatibility fields, expiry semantics and hosting-layer error limitations.

For MCP send Content-Type: application/json and Accept: application/json, text/event-stream. Negotiate protocol version with initialize; send MCP-Protocol-Version afterwards. No session ID is issued. The public tools need no token and grant no private access. MCP retains its JSON-RPC error format. Prefer Markdown on /, /docs, /about and /contact using Accept: text/markdown. Browsers still receive HTML.

## Product pages

- [CareOps home](https://getcareops.co.uk/): Product scope and published options.
- [Guided trial](https://getcareops.co.uk/trial): Explore the existing trial; no sensitive upload needed.
- [Readiness Diagnostic](https://getcareops.co.uk/diagnostic): Focused branch or service review.
- [Request a walkthrough](https://getcareops.co.uk/request-walkthrough): Human-assisted setup enquiry.
- [Rota gaps](https://getcareops.co.uk/problems/rota-gaps): Uncovered visits and late cover pressure.
- [Missed enquiries](https://getcareops.co.uk/problems/missed-enquiries): Referral and private-pay follow-up.
- [Staff readiness](https://getcareops.co.uk/problems/staff-readiness): Checks and documents.
- [Compliance evidence](https://getcareops.co.uk/problems/compliance-evidence): Evidence ownership and review.
- [Weekly command view](https://getcareops.co.uk/use-cases/weekly-command-view): Visibility, readiness and action.
- [Registered managers](https://getcareops.co.uk/for/registered-managers): Manager use cases.
- [Care owners](https://getcareops.co.uk/for/care-owners): Owner use cases.

## Trust and contact

- [About CareOps](https://getcareops.co.uk/about): Operator, purpose and product boundaries.
- [Contact CareOps](https://getcareops.co.uk/contact): operations@getcareops.co.uk; business enquiries and support.
- [Privacy notice](https://getcareops.co.uk/privacy): Data handling and privacy contact.
- [Data protection](https://getcareops.co.uk/data-protection): Access and security information.
- [Terms](https://getcareops.co.uk/terms): Service terms.
- [Sitemap](https://getcareops.co.uk/sitemap.xml): Public pages.

## Boundaries

CareOps supports operational visibility and action planning. It does not guarantee compliance, inspection outcomes or regulatory results. It is not a clinical decision system or an emergency service. The current operational UI is read-only and remains behind existing authenticated tenant access.

No public provider-capacity, care-referral, assessment-booking, record-editing or payment tool is available in this release. Do not infer live capacity from illustrative dashboard figures. No Muse, Grok or registry approval is claimed. A scanner reference to another business's MCP server is not a CareOps integration.