CareClinic Health Tracker
REMOTE · MCP.CARECLINIC.IO
Review schedules, symptoms, mood, and explicitly confirmed CareClinic check-ins.
Available components
Last scanned (8 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 331 tokens (~41/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 4 Nov 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 3 Nov 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 2 Nov 26 0
- Stability: 0.97 → pass security
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 1 Nov 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 31 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 30 Oct 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Probed https://mcp.careclinic.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=careclinic.io | CN=WE1,O=Google Trust Services,C=US | 28 Oct 2026 | 26 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | f6f92c52d99d0e540ed8fbbfd50ba9c2 |
| SANs: careclinic.io, mcp.careclinic.io, *.mcp.careclinic.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.careclinic.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| careclinic.io. | DS published | 2371 | 13 | Verified |
| mcp.careclinic.io. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://mcp.careclinic.io/.well-known/oauth-protected-resource/mcp", scope="careclinic.wellness.read careclinic.symptoms.write careclinic.mood.write careclinic.sleep.write careclinic.medications.write"
Bearer realm="OAuth", resource_metadata="https://mcp.careclinic.io/.well-known/oauth-protected-resource/mcp", scope="careclinic.wellness.read careclinic.symptoms.write careclinic.mood.write careclinic.sleep.write careclinic.medications.write"| Header | Value |
|---|---|
| strict-transport-security | max-age=0; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Document | https://mcp.careclinic.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.careclinic.io/mcp |
| Authorisation server | https://mcp.careclinic.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.careclinic.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.careclinic.io/mcp | Inconclusive | 401 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
careclinic_account Get CareClinic account access ~25
Returns the connected CareClinic account’s plan and basic-versus-full insight entitlement.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| account | object | yes | – |
| accountLinks | object | – | – |
| kind | string | yes | – |
| premiumInfoUrl | string | yes | – |
No examples provided.
careclinic_capabilities Show CareClinic capabilities ~22
Shows the CareClinic data and actions available in this release.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | – |
| kind | string | yes | – |
No examples provided.
careclinic_commit_log Save a confirmed CareClinic check-in ~67
App-only write used by the CareClinic confirmation card. It writes only the exact entry represented by a valid signed preview after explicit confirmation. Replaying the same preview returns the original receipt instead of creating a duplicate.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmationToken | string | yes | – |
| confirmed | boolean | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| receipt | object | yes | – |
No examples provided.
careclinic_get_insights Summarize CareClinic wellness patterns ~48
Creates deterministic observational summaries. Free accounts receive basic counts; detailed reports and chart values are returned only for Premium accounts.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| include | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| access | – | yes | – |
| accountLinks | object | – | – |
| kind | string | yes | – |
No examples provided.
careclinic_preview_log Preview a CareClinic check-in ~50
Validates an exact owned symptom, mood or sleep entry and creates a short-lived confirmation preview. It never writes data. Scheduled medication and supplement taken/skipped events are enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| entry | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| expiresAt | string | yes | – |
| kind | string | yes | – |
| preview | object | yes | – |
| requiresExplicitConfirmation | boolean | yes | – |
No examples provided.
careclinic_recent_wellness Get recent CareClinic wellness logs ~45
Returns minimized symptom, mood, medication and sleep activity. Notes and internal record IDs are excluded.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| include | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| snapshot | object | yes | – |
No examples provided.
careclinic_search_catalog Search the connected CareClinic catalog ~45
Finds an owned medication, symptom or sleep care plan before preparing a log. Never invent an item ID.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| items | array | yes | – |
| kind | string | yes | – |
No examples provided.
careclinic_today_schedule Show today’s CareClinic medication schedule ~29
Returns today’s owned medication and supplement occurrences with time, dose, reminder identity, and status.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| kind | string | yes | – |
No examples provided.
How do I install the CareClinic Health Tracker MCP server?
CareClinic Health Tracker is a hosted endpoint at https://mcp.careclinic.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.careclinic.io
claude mcp add --transport http io-careclinic-health-tracker 'https://mcp.careclinic.io/mcp'
What is the CareClinic Health Tracker MCP server?
CareClinic Health Tracker is an MCP server listed in the public MCP registry as io.careclinic/health-tracker. Review schedules, symptoms, mood, and explicitly confirmed CareClinic check-ins. This page covers its hosted endpoint (https://mcp.careclinic.io/mcp).
Is the CareClinic Health Tracker MCP server safe to use?
CareClinic Health Tracker scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CareClinic Health Tracker MCP server expose?
CareClinic Health Tracker exposes 8 tools: careclinic_capabilities, careclinic_account, careclinic_today_schedule, careclinic_search_catalog, careclinic_recent_wellness, and 3 more. Their descriptions and schemas cost roughly 331 tokens of context every time the server is loaded.
Does the CareClinic Health Tracker MCP server require authentication?
Yes. CareClinic Health Tracker asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the CareClinic Health Tracker MCP server still maintained?
CareClinic Health Tracker is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the CareClinic Health Tracker MCP server?
VerifyMCP ran 13 checks on CareClinic Health Tracker, covering TLS certificate, Authorization, HSTS header, DNSSEC and 9 more. One item could not be completed, a gap on our side rather than a finding about CareClinic Health Tracker: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.