Skip to content

physician-review MCP server

health.anomaly/physician-reviewanomaly.healthstreamable-httpv0.5.0Scanned

Physicians for the agentic era. Book a US-licensed doctor: orders, prescribes, 90-day plan.

4 tools: 1 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 1 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the physician-review MCP server can do

The physician-review MCP server is published by anomaly.health, a domain the MCP Registry verified. It has 4 tools. It can create or change data (1 tool: anomaly_book_session), but cannot delete data. 3 tools only read.

2 tools bring in text other people can write (anomaly_check_availability and anomaly_book_session).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 0.5.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 1Claude Code: ask
  • anomaly_book_sessionBook a Physician Health Review with Anomaly Health (30 min $249, 60 min $349).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 3Show 3 read-only tools
  • anomaly_about_careRead this first when a user wants to move from AI to a real doctor.No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • anomaly_check_availabilityList open times for a Physician Health Review with Anomaly Health (30 min $249, 60 min $349).Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "list" and "review": it reads comments, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • anomaly_health_memoryExplain Anomaly's health memory and give the app link.No findings

    Why it is in this group

    • The description's first verb is "explain": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:54 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.anomaly.health/mcp: tools/list returned 4 tools to an anonymous client, including anomaly_book_session (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.5.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http physician-review https://mcp.anomaly.health/mcp
claude mcp add --transport http physician-review https://mcp.anomaly.health/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__physician-review__anomaly_about_care",
      "mcp__physician-review__anomaly_health_memory",
      "mcp__physician-review__anomaly_check_availability"
    ],
    "ask": [
      "mcp__physician-review__anomaly_book_session"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as physician-review. Review it before you use it.

Capability tags behind 2 rules
  • mcp__physician-review__anomaly_check_availability untrusted-input
  • mcp__physician-review__anomaly_book_session untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/health.anomaly/physician-review/verify?hash=af342cfcb53a5ba5944f71bf3cab190f0e95dc25075a22ced799f04e59bdd7d9" | jq -e '.changed == false'

Pinned hash af342cfcb53a, from Nov 15, 2026, 11:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/health.anomaly/physician-review/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for health.anomaly/physician-review
[![Anlyon Radar](https://radar.anlyon.com/badge/health.anomaly/physician-review.svg)](https://radar.anlyon.com/servers/health.anomaly/physician-review)

Source: MCP Registry. Synced Oct 21, 2026, 18:13 UTC.

physician-review MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the physician-review MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the physician-review MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the physician-review MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the physician-review MCP server have?

4 tools: 1 write, 3 read. anomaly_book_session, anomaly_about_care, anomaly_health_memory and anomaly_check_availability.

Does the physician-review MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the physician-review MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the physician-review MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.