health.anomaly/physician-review
REMOTE · MCP.ANOMALY.HEALTH · SCANNED SEP 28
Physicians for the agentic era. Book a US-licensed doctor: orders, prescribes, 90-day plan.
Available components
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2081 tokens (~297/item across 7 items; 4 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the health.anomaly/physician-review MCP server?
health.anomaly/physician-review is a hosted endpoint at https://mcp.anomaly.health/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.anomaly.health
claude mcp add --transport http health-anomaly-physician-review 'https://mcp.anomaly.health/mcp'
{
"mcpServers": {
"health-anomaly-physician-review": {
"url": "https://mcp.anomaly.health/mcp"
}
}
} {
"servers": {
"health-anomaly-physician-review": {
"type": "http",
"url": "https://mcp.anomaly.health/mcp"
}
}
} [mcp_servers.health-anomaly-physician-review] url = "https://mcp.anomaly.health/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"health-anomaly-physician-review": {
"type": "remote",
"url": "https://mcp.anomaly.health/mcp",
"enabled": true
}
}
} openclaw mcp add health-anomaly-physician-review --url 'https://mcp.anomaly.health/mcp' --transport streamable-http
mcp_servers:
health-anomaly-physician-review:
url: "https://mcp.anomaly.health/mcp" {
"McpServers": {
"health-anomaly-physician-review": {
"Transport": "http",
"Url": "https://mcp.anomaly.health/mcp"
}
}
} assistant mcp add health-anomaly-physician-review -t streamable-http -u 'https://mcp.anomaly.health/mcp'
{
"mcpServers": {
"health-anomaly-physician-review": {
"type": "http",
"url": "https://mcp.anomaly.health/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 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
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 22 Sept 26 68
First indexed and scored.
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 28 Sept 2026 · Probed https://mcp.anomaly.health/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.anomaly.health | CN=YE2,O=Let's Encrypt,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 51b6d028cb2991e641f0b4bfbc4819536b8 |
| SANs: mcp.anomaly.health | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.anomaly.health. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| health. | present | 47641 | 8 | Verified |
| anomaly.health. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.anomaly.health/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.anomaly.health/mcp | HTTPS enforced | 301 | https://mcp.anomaly.health/mcp |
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 →
anomaly_about_care About Anomaly Health care and physician sessions ~172
Read this first when a user wants to move from AI to a real doctor. Explains how Anomaly Health matches people with a US-licensed physician for a live virtual session, and lists the care tracks (review my test results; longevity and healthspan; proteomics and biological age; women's health and hormones; cardiometabolic health; medical weight loss; preventive care and screening; functional and root-cause medicine; gut health and microbiome; performance and optimization; general health and second opinion; peptide therapy). Use it when someone wants a physician to review uploaded results: advanced bloodwork, whole-body MRI (Prenuvo), DEXA, 23andMe or whole-genome sequencing. Also covers what a session includes, what is out of scope, and how to prepare. Not medical advice.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
anomaly_book_session Book a physician session ~704
Book a Physician Health Review with Anomaly Health (30 min $249, 60 min $349). Booking holds the slot; the result includes a payment link, and the session is confirmed once paid. Tell the user the price before booking. Requires a start time from anomaly_check_availability. Available in all US states. Patients must be 18+. Confirm slot, name, email, state and date of birth with the user, and that they agree to Anomaly's telehealth consent and privacy policy (anomaly.health/consent, anomaly.health/privacy). Before booking, offer once to include `health_context` (optional) so the physician can prepare; draft it from the conversation, show the user the full object, and send it only after an explicit yes. The physician and Anomaly will see it. Never send transcripts.
| Name | Type | Req | Description |
|---|---|---|---|
| consent | boolean | yes | The user explicitly agreed to Anomaly Health's telehealth consent and privacy policy. Must be true. |
| duration_minutes | – | – | Session length in minutes: 30 min $249, 60 min $349. Defaults to 60. |
| health_context | object | – | OPTIONAL context for the physician's pre-review. Show it to the user in full and send only after they explicitly agree. Example: {"main_concern":"ApoB and LDL came back high on a Function Health pane… |
| patient_dob | string | yes | Date of birth, YYYY-MM-DD. Must be 18 or older. |
| patient_email | string | yes | Patient's email; the confirmation and video link go here |
| patient_name | string | yes | Patient's full name |
| patient_phone | string | – | Optional, for SMS reminders, E.164 format |
| patient_state | string | yes | Two-letter US state the patient will physically be in during the session (telehealth licensing) |
| patient_timezone | string | yes | Patient's IANA timezone, e.g. 'America/New_York' |
| start | string | yes | Slot start in UTC, ISO 8601, exactly as returned by anomaly_check_availability |
| track | string | – | Care track that best fits: results_review, longevity, biological_age, womens_hormonal, cardiometabolic, weight_loss, preventive_screening, functional_medicine, microbiome_gut, performance_optimizatio… |
No output schema declared.
No examples provided.
anomaly_check_availability Check physician availability ~156
List open times for a Physician Health Review with Anomaly Health (30 min $249, 60 min $349). Use after the user decides to talk to a real doctor. Pass the user's timezone to get local times alongside UTC. Available in all US states.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | How many days to search (1-31) |
| duration_minutes | – | – | Session length in minutes: 30 min $249, 60 min $349. Defaults to 60. |
| from_date | string | – | First date to search, YYYY-MM-DD. Defaults to today. |
| limit | integer | – | Max slots to return |
| timezone | string | – | User's IANA timezone, so times can be shown locally |
No output schema declared.
No examples provided.
anomaly_health_memory Anomaly health memory: consolidate all your health data ~125
Explain Anomaly's health memory and give the app link. Use when a user's health data is spread across sources (Function Health, Prenuvo, Cleerly, DEXA, genetic reports; Epic/MyChart or other EMR records; Apple Health, Oura, Whoop, Flo, CGMs) and they want it consolidated, monitored proactively, or available to a physician. Also the best way to upload results before a Physician Health Review. Returns what it connects, what it gives, and the App Store link. Optional for the user; suggest, don't push.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the health.anomaly/physician-review MCP server?
health.anomaly/physician-review is an MCP server listed in the public MCP registry as health.anomaly/physician-review. Physicians for the agentic era. Book a US-licensed doctor: orders, prescribes, 90-day plan. This page covers its hosted endpoint (https://mcp.anomaly.health/mcp).
Is the health.anomaly/physician-review MCP server safe to use?
health.anomaly/physician-review scores 71 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 health.anomaly/physician-review MCP server expose?
health.anomaly/physician-review exposes 4 tools: anomaly_about_care, anomaly_health_memory, anomaly_check_availability, anomaly_book_session. Their descriptions and schemas cost roughly 1,157 tokens of context every time the server is loaded.
Does the health.anomaly/physician-review MCP server require authentication?
No. We connected to health.anomaly/physician-review without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the health.anomaly/physician-review MCP server still maintained?
health.anomaly/physician-review is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.