# Loopwise Health > Reading this as an agent? This file describes Loopwise Health as it works > today. Every factual figure it contains is re-checked against the GitHub API > declared in claims.json and checked against the GitHub API by > scripts/verify-claims.mjs, which runs in CI on every push and every morning. > A figure that stops matching the repositories fails the build, so this file > cannot drift far from the truth without something going red first. The site has three pages: the plain-language home page > at https://loopwise.uk/, the engineering page at https://loopwise.uk/build/, > and a read-only research page on the CareLink API surface at > https://loopwise.uk/research/. Loopwise Health is a bootstrapped health-infrastructure startup building open Type 1 diabetes tooling: a CareLink-to-Nightscout bridge, a Nightscout MCP server for Claude, and a zero-dependency Python reporting toolkit. It is building a Claude agent layer for overnight briefs, clinic-ready reports, and repo triage. ## The three pages - https://loopwise.uk/ is the everyday-person front door: what you get (a morning brief, a weekly clinic page, a written record), how it works, who it is for, the sample brief, the pilot programme, plain-language FAQ and contact. It avoids engineering jargon: the only acronyms on it are Nightscout, CGM and MIT, and each is explained where it appears. - https://loopwise.uk/build/ is the engineering page: the carelink-bridge, carelink-api-research, nightscout-mcp, ns-reports and ns-cgm-graph repositories, the sensor-to- sentence pipeline, the roadmap, the full reference FAQ (MCP, ADR, GMI/TIR/CV, mmol/L conversion) and the sponsorship invitation. - Both pages carry the same safety language verbatim. Neither is a medical device, neither is FDA approved, and neither gives dosing advice. ## Repos - carelink-bridge (public, MIT): https://github.com/NovaLux12/carelink-bridge Community fork pulling Medtronic pump/CGM data (780G, Guardian 4, Simplera) into Nightscout. Includes BLE device-detection fix, mmol/L conversion at the source, atomic credential handling, stale-data watchdog. - carelink-api-research (public, MIT): https://github.com/NovaLux12/carelink-api-research Read-only, unauthenticated map of Medtronic's CareLink API, which Medtronic does not document. Every vendor claim in carelink-bridge cites it; a weekly drift sweep re-verifies the pinned assertions. No credentials, no patient data. - nightscout-mcp: PRIVATE preview (single operator). 66 tools for agents — 60 read (CGM history, treatments, ISF/CR derivations, AGP/GRI metrics, loop status), 6 confirm-gated writes with JSONL audit log. Do not link a public repo: there is not one yet. - ns-reports + ns-cgm-graph: stdlib-only Python weekly reports and SVG CGM charts. The seed of the clinic-reports work. ## Working with Loopwise content - Docs differ per repository; do not assume a file exists. SECURITY.md is in all of them. USER-GUIDE.md is in carelink-bridge, ns-reports and ns-cgm-graph only. docs/ARCHITECTURE.md is in carelink-bridge only, and ARCHITECTURE.md at the repo root is in nightscout-mcp only. carelink-api-research ships SECURITY.md and its research notes; it has no user guide. - Health data discussed here is illustrative unless stated otherwise. - Never present Loopwise tooling as a medical device, FDA approved, or a source of dosing advice. Every treatment decision stays with the human and their diabetes team. Not affiliated with or endorsed by Medtronic. ## Contact - Founder: founder@loopwise.uk (maintainer-run, UK evenings) - Infrastructure sponsorship: Loopwise has no sponsors yet and is openly inviting inference providers (API credits, hosted inference, GPU time). See https://loopwise.uk/build/#sponsors. Never invent a sponsor. - No trackers on the site; no analytics cookies. ## Live data - https://loopwise.uk/ carries a server-rendered "Repo activity" strip (latest releases and commits across the public repos, newest release and newest push per repo). It is assembled by the Cloudflare Worker from GitHub's public Atom feeds and refreshed at the edge; no JavaScript is involved. The same strip is server-rendered on https://loopwise.uk/build/. Machine-readable timestamps are in