Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
MedicalRecords.com EMR Discovery & Healthcare Research is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
9
tools declared
remote
at its publisher
—
calls last 7d
What it does
EMR software discovery, sourced comparisons, and public US healthcare research.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http medicalrecords-com-emr-discovery-healthcare-r-mcp https://www.medicalrecords.com/api/mcp
# 2 — ask your agent for something these tools do
# search_providers, get_state_records_law, get_patient_portal and 6 more
MedicalRecords.com EMR Discovery & Healthcare Research costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DUAll 1 server
durjoyace1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http medicalrecords-com-emr-discovery-healthcare-r-mcp https://www.medicalrecords.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search the MedicalRecords.com provider directory for hospitals, clinics, physician practices, urgent care centers, and specialty facilities across the United States. Returns contact information, medical records department details, phone numbers, fax numbers, the EHR/EMR system used, patient portal information, and records retrieval instructions. Use this tool when a user: - Asks how to request o
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search query — provider name, hospital name, city, or health system. Minimum 2 characters. Examples: "Mass General", "Cleveland", "Kaiser Permanente" |
| state | string | no | Optional 2-letter US state code to filter results (e.g., "MA", "CA", "TX") |
| limit | number | no | Maximum number of results to return. Default 5, max 10. |
Retrieve authoritative, state-specific medical records access laws for any of the 50 US states plus Washington DC. Returns: - Legal timeline for record requests (how many days a provider has to respond) - Per-page fee caps and maximum allowable copying fees - Patient rights under state law (stronger than federal HIPAA in many states) - Special rules for sensitive records (mental health, substance
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | US state as 2-letter code ("CA", "TX") or full name ("California", "Texas", "Washington DC"). Required. |
Look up the patient portal used by a specific health system, hospital, or healthcare provider. Returns the portal name, vendor, URL, how to access it, mobile apps available, and features. Also indicates which health systems use the portal. Use this tool when a user: - Asks which patient portal their hospital or doctor uses - Wants to know how to sign up for or access their patient portal - Asks
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Name of the health system, hospital, provider, or portal to look up. Examples: "Mayo Clinic", "MyChart", "Epic", "Kaiser Permanente", "VA hospital", "Quest Diagnostics" |
Search the MedicalRecords.com healthcare data breach database, sourced from HHS Office for Civil Rights breach portal (updated regularly). Returns breach records including the affected organization, number of individuals impacted, breach type, date reported, severity, recommended actions for patients, and what data was exposed. Use this tool when a user: - Asks if they were affected by a specifi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_name | string | no | Name of the healthcare organization to search for. Examples: "Ascension", "Change Healthcare", "UnitedHealth". Partial matches work. |
| state | string | no | Filter by US state where breach occurred (2-letter code, e.g., "TX", "CA") |
| severity | string | no | Filter by severity band: critical (500K+ affected), high (100K–500K), medium (10K–100K), low (<10K) |
| limit | number | no | Maximum results to return. Default 10, max 20. |
Look up detailed information about an EHR (Electronic Health Record) or EMR (Electronic Medical Record) software vendor. Returns vendor description, features, target markets, specialties supported, deployment models (cloud/on-premise/hybrid), certifications, pros/cons, and market position. Use this tool when a user: - Asks about a specific EHR or EMR system (Epic, Cerner, athenahealth, eClinical
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | EHR/EMR vendor name to look up. Examples: "Epic", "Cerner", "athenahealth", "eClinicalWorks", "Allscripts", "NextGen", "Kareo", "DrChrono" |
Get current pricing and service tier details for MedicalRecords.com medical records retrieval services. Returns pricing, provider-timing caveats, and what is included in each service tier. Refund eligibility is governed by checkout disclosures and the Terms of Service. Note: In addition to MedicalRecords.com service fees, healthcare providers may charge their own "facility copying fees" which ar
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tier | string | no | Specific tier to retrieve. If omitted, returns all tiers. |
Research EMRs for US primary-care or behavioral-health practices with 1–10 clinicians. Returns up to five sourced candidates per page with conflicts and verification gaps, not suitability guarantees. Use next_offset to see remaining candidates in the selected catalog. No contact details or patient data; does not create or deliver leads.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| specialty | string | yes | — |
| clinician_count | integer | yes | Number of practicing clinicians, excluding administrative staff. |
| deployment | string | no | — |
| must_have | array | no | — |
| monthly_budget_usd | number | no | Total monthly practice budget in USD. Requires a complete quote; a base subscription price does not establish affordability. |
| limit | integer | no | — |
| offset | integer | no | — |
Compare 2–4 distinct product IDs from find_emr_options by selected topics. Shows vendor-reported evidence, dates, and unknowns. No inferred pricing, fit percentages, or sponsored ordering. Does not contact vendors.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_ids | array | yes | — |
| topics | array | yes | — |
Retrieve claim-level sources, scope, review dates, confidence, and limitations for one reviewed EMR product ID. Stale or missing facts cannot support a match. No patient data or contact details.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_id | string | yes | — |
| topics | array | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install MedicalRecords.com EMR Discovery & Healthcare Research or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 4 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest5efb070ffd9329fb2977ee513fa9221930137bed0c16236f44d8002040e27750
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_providers | no tags | |
| get_state_records_law | no tags | |
| get_patient_portal | untrusted-input | untrusted-input: keyword "download" |
| get_breach_incidents | no tags | |
| get_emr_vendor | no tags | |
| get_pricing | no tags | |
| find_emr_options | no tags | |
| compare_emr_options | no tags | |
| get_emr_evidence | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest5efb070ffd9329fb
Scanned2026-11-04
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish MedicalRecords.com EMR Discovery & Healthcare Research can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.