Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Hipa.ai Clinical Trials 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
8
tools declared
remote
at its publisher
—
calls last 7d
What it does
Search recruiting US clinical trials by city, condition, phase and patient eligibility.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http hipa-ai-clinical-trials-mcp https://hipa.ai/api/mcp/mcp
# 2 — ask your agent for something these tools do
# clinicaltrials_count_trials, clinicaltrials_find_eligible_trials, clinicaltrials_get_data_freshness and 5 more
Hipa.ai Clinical Trials costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
HIAll 1 server
hipa1 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 hipa-ai-clinical-trials-mcp https://hipa.ai/api/mcp/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
8 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.
Return only the count of active US clinical trials matching the same filter set accepted by clinicaltrials_search_trials. Use this when the caller needs a population estimate (e.g. 'how many trials are recruiting in California for type 2 diabetes?') without fetching trial records. Far cheaper than calling search and discarding the results.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | Two-letter US state code (e.g. CA, NY, TX, FL). Case-insensitive on input; normalized to uppercase. DC is accepted. Full state names like 'California' are not accepted - use 'CA' instead. |
| city | string | no | US city name. Allows letters, spaces, hyphens, apostrophes, and periods. Examples: "San Francisco", "St. Louis", "O'Fallon", "Wilkes-Barre". Surrounding whitespace is trimmed; maximum 100 characters. |
| condition | string | no | Condition to filter by: a curated slug ('breast-cancer'), its label ('Breast Cancer') or a condition name as it appears in trial records ('Breast Neoplasms'). Case-insensitive. Call clinicaltrials_lis |
| phase | array | no | — |
| studyType | array | no | — |
| interventionType | array | no | — |
| status | array | no | — |
| sex | string | no | Biological sex eligibility filter. Use 'female' or 'male'. Trials open to both sexes are returned regardless of this filter. |
| age | string | no | Age bucket for eligibility matching. 'child' = 0-17 years, 'adult' = 18-64 years, 'senior' = 65+ years. Maps to AACT minimum_age/maximum_age boundaries server-side. |
| healthyVolunteersOnly | boolean | no | — |
| facility | string | no | Exact facility name match. Scopes results to trials running at this named site. |
Match patient demographics (age, sex, conditions, location) to currently recruiting US clinical trials. Conditions are curated slugs, labels or trial-record condition names (discover them via clinicaltrials_list_conditions). Maps ageYears to the AACT eligibility bucket (child 0-17, adult 18-64, senior 65+). Returns up to 50 trials per page with an opaque cursor for further pagination. State scope
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ageYears | integer | yes | Patient age in years. Integer in [0, 120]. Maps to the AACT eligibility bucket: 0-17 child, 18-64 adult, 65+ senior. |
| sex | string | no | Biological sex eligibility filter. Use 'female' or 'male'. Trials open to both sexes are returned regardless of this filter. |
| conditions | array | yes | One or more conditions. Unrecognized values are rejected as invalid_input with suggested slugs. |
| state | string | yes | Two-letter US state code (e.g. CA, NY, TX, FL). Case-insensitive on input; normalized to uppercase. DC is accepted. Full state names like 'California' are not accepted - use 'CA' instead. |
| city | string | no | US city name. Allows letters, spaces, hyphens, apostrophes, and periods. Examples: "San Francisco", "St. Louis", "O'Fallon", "Wilkes-Barre". Surrounding whitespace is trimmed; maximum 100 characters. |
| pageSize | integer | no | Number of results per page. Integer in [1, 50]. Default 20. |
| cursor | string | no | Opaque pagination cursor returned by a previous call's nextCursor field. Omit to start from the beginning of the result set. Cursors are tied to the exact filter set used to issue them - reusing a cur |
Returns the timestamp at which the underlying ClinicalTrials.gov dataset was last refreshed on the server. Use this to disclose the data age to end users or to decide whether to re-query for fresher results.
No parameter schema on file.
Fetch the full clinical trial record by NCT ID. Returns title, status, sponsor, summary, conditions, interventions, arms, design, eligibility (age, sex, healthy volunteers and the full inclusion/exclusion criteria text), primary outcomes, central contacts, every US site location with its contacts, and links to the trial's Hipa.ai page and ClinicalTrials.gov record. Use this after clinicaltrials_se
| Parameter | Type | Required | Notes |
|---|---|---|---|
| nctId | string | yes | ClinicalTrials.gov identifier. Canonical form: 'NCT' followed by exactly 8 digits (e.g. NCT12345678). Case-insensitive on input; normalized to uppercase. Surrounding whitespace is trimmed. |
List the curated conditions the trial search tools filter on, with the slug to pass as condition (clinicaltrials_search_trials, clinicaltrials_count_trials) or in conditions (clinicaltrials_find_eligible_trials). Pass query to find a condition by name or synonym (e.g. 'lung', 'diabetes', 'NSCLC'). Ordered by how many recruiting US trials study the condition. Specialty entries (e.g. 'oncology
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Case-insensitive search over condition labels, slugs and synonyms (the raw condition names trial records use). Omit to list the most common conditions. |
| limit | integer | no | Maximum conditions to return. Integer in [1, 250]. Default 50. |
List the most common conditions across active US clinical trials in a US state or city, with trial counts. Use this when the caller wants to see what is well-represented in a region before searching. Each entry carries the curated slug to pass to clinicaltrials_search_trials as condition (null when the label has no curated match - use clinicaltrials_list_conditions to find a close one). Counts
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | Two-letter US state code (e.g. CA, NY, TX, FL). Case-insensitive on input; normalized to uppercase. DC is accepted. Full state names like 'California' are not accepted - use 'CA' instead. |
| city | string | no | US city name. Allows letters, spaces, hyphens, apostrophes, and periods. Examples: "San Francisco", "St. Louis", "O'Fallon", "Wilkes-Barre". Surrounding whitespace is trimmed; maximum 100 characters. |
| limit | integer | no | Maximum number of buckets to return from a top-N aggregation. Integer in [1, 25]. Default 10. Aggregator returns buckets sorted by descending count. |
List named research facilities running active US clinical trials in a city, ranked by trial count. Returns each facility's name, ZIP, the top conditions they study, and one example NCT ID for quick verification. Use this when the caller asks where studies are happening in a specific city, or wants to surface named local clinics for a downstream clinicaltrials_search_trials call with the facility f
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | Two-letter US state code (e.g. CA, NY, TX, FL). Case-insensitive on input; normalized to uppercase. DC is accepted. Full state names like 'California' are not accepted - use 'CA' instead. |
| city | string | yes | US city name. Allows letters, spaces, hyphens, apostrophes, and periods. Examples: "San Francisco", "St. Louis", "O'Fallon", "Wilkes-Barre". Surrounding whitespace is trimmed; maximum 100 characters. |
| limit | integer | no | Maximum number of buckets to return from a top-N aggregation. Integer in [1, 25]. Default 10. Aggregator returns buckets sorted by descending count. |
Search active US clinical trials by location, condition slug, phase, study type, intervention type, recruitment status, sex eligibility, age bucket, healthy-volunteer flag, and facility name. Returns up to 50 trials per page with an opaque cursor for further pagination. Cursors are tied to the exact filter set used to issue them - reusing a cursor with a different filter set returns invalid_cursor
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | Two-letter US state code (e.g. CA, NY, TX, FL). Case-insensitive on input; normalized to uppercase. DC is accepted. Full state names like 'California' are not accepted - use 'CA' instead. |
| city | string | no | US city name. Allows letters, spaces, hyphens, apostrophes, and periods. Examples: "San Francisco", "St. Louis", "O'Fallon", "Wilkes-Barre". Surrounding whitespace is trimmed; maximum 100 characters. |
| condition | string | no | Condition to filter by: a curated slug ('breast-cancer'), its label ('Breast Cancer') or a condition name as it appears in trial records ('Breast Neoplasms'). Case-insensitive. Call clinicaltrials_lis |
| phase | array | no | — |
| studyType | array | no | — |
| interventionType | array | no | — |
| status | array | no | — |
| sex | string | no | Biological sex eligibility filter. Use 'female' or 'male'. Trials open to both sexes are returned regardless of this filter. |
| age | string | no | Age bucket for eligibility matching. 'child' = 0-17 years, 'adult' = 18-64 years, 'senior' = 65+ years. Maps to AACT minimum_age/maximum_age boundaries server-side. |
| healthyVolunteersOnly | boolean | no | — |
| facility | string | no | Exact facility name match. Scopes results to trials running at this named site. |
| pageSize | integer | no | Number of results per page. Integer in [1, 50]. Default 20. |
| cursor | string | no | Opaque pagination cursor returned by a previous call's nextCursor field. Omit to start from the beginning of the result set. Cursors are tied to the exact filter set used to issue them - reusing a cur |
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 Hipa.ai Clinical Trials 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 24 Oct 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 digest62365fa3a2de4bfdf5a0feef11752b3cefaf6622d8f899731d09da5e323132a5
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 |
|---|---|---|
| clinicaltrials_count_trials | no tags | |
| clinicaltrials_find_eligible_trials | no tags | |
| clinicaltrials_get_data_freshness | no tags | |
| clinicaltrials_get_trial | untrusted-input | untrusted-input: keyword "fetch" |
| clinicaltrials_list_conditions | no tags | |
| clinicaltrials_list_top_conditions | no tags | |
| clinicaltrials_list_top_facilities | no tags | |
| clinicaltrials_search_trials | 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 digest62365fa3a2de4bfd
Scanned2026-10-24
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 Hipa.ai Clinical Trials 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.