Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Hipa.ai Clinical Trials

REMOTE · HIPA.AI

Search recruiting US clinical trials by city, condition, phase and patient eligibility.

Available components

+3 this week 79 Trust /100

Last scanned (7 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability76
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2455 tokens (~306/item across 8 items; 8 tools + 0 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 Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 75% of tool parameters carry a description.Partial
  • 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 9 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
Changelog

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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.27 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 31 Oct 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Stability: 0.20 → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 24 Oct 26 73

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Probed https://hipa.ai/api/mcp/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=hipa.ai CN=WE1,O=Google Trust Services,C=US 24 Sept 2026 23 Dec 2026 ECDSA 256 ECDSA-SHA256 1d8093dc6189a1041395ae15ead1d7e9
SANs: hipa.ai, *.hipa.ai
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 insecure

Validation of hipa.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
hipa.ai. 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
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://static.cloudflareinsights.com https://www.googletagmanager.com https://www.google-analytics.com https://pagead2.googlesyndication.com https://*.adtrafficquality.google https://tpc.googlesyndication.com https://fundingchoicesmessages.google.com https://challenges.cloudflare.com https://get.microsoft.com; style-src 'self' 'unsafe-inline' https://unpkg.com; img-src 'self' data: https:; font-src 'self'; connect-src 'self' https://cloudflareinsights.com https://www.googletagmanager.com https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com https://www.google.com https://pagead2.googlesyndication.com https://*.adtrafficquality.google https://challenges.cloudflare.com; frame-src 'self' https://www.googletagmanager.com https://pagead2.googlesyndication.com https://googleads.g.doubleclick.net https://*.adtrafficquality.google https://tpc.googlesyndication.com https://challenges.cloudflare.com; frame-ance
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://hipa.ai/api/mcp/mcp Verified 200
http (plaintext) http://hipa.ai/api/mcp/mcp HTTPS enforced 301 https://hipa.ai/api/mcp/mcp
MCP tools · 8 exposed · ~2,248 tokens

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 →

Tool Tokens
clinicaltrials_count_trials ~411

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.

NameTypeReqDescription
agestring–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.
citystring–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.
conditionstring–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_li…
facilitystring–Exact facility name match. Scopes results to trials running at this named site.
healthyVolunteersOnlyboolean––
interventionTypearray––
phasearray––
sexstring–Biological sex eligibility filter. Use 'female' or 'male'. Trials open to both sexes are returned regardless of this filter.
statestringyesTwo-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.
statusarray––
studyTypearray––
NameTypeReqDescription
countintegeryesNumber of active US trials matching every applied filter.
searchCriteriaobjectyesEcho of the applied filter set so the caller can confirm what the server interpreted.

No examples provided.

clinicaltrials_find_eligible_trials ~408

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 is required; city is optional for facility-level narrowing.

NameTypeReqDescription
ageYearsintegeryesPatient age in years. Integer in [0, 120]. Maps to the AACT eligibility bucket: 0-17 child, 18-64 adult, 65+ senior.
citystring–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.
conditionsarrayyesOne or more conditions. Unrecognized values are rejected as invalid_input with suggested slugs.
cursorstring–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 cu…
pageSizeinteger–Number of results per page. Integer in [1, 50]. Default 20.
sexstring–Biological sex eligibility filter. Use 'female' or 'male'. Trials open to both sexes are returned regardless of this filter.
statestringyesTwo-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.
NameTypeReqDescription
nextCursorstring–Opaque cursor to fetch the next page. Absent when no more pages are available.
noMatchHintsarray–Actionable suggestions to broaden the eligibility match, present only when totalMatching is zero.
searchCriteriaobjectyesEcho of the applied eligibility criteria so the caller can confirm what the server interpreted.
totalMatchingintegeryesTotal eligible trials matching the criteria across all pages.
trialsarrayyesTrial records that match the eligibility filters, sorted newest first by start_date.

No examples provided.

clinicaltrials_get_data_freshness ~54

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
humanReadablestringyesHuman-readable rendering of the same timestamp in en-US.
refreshedAtIsostringyesISO-8601 UTC timestamp of the last AACT index refresh.

No examples provided.

clinicaltrials_get_trial ~171

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_search_trials surfaces a candidate NCT id and the caller needs the complete record - the search tool only returns a paginated summary.

NameTypeReqDescription
nctIdstringyesClinicalTrials.gov identifier. Canonical form: 'NCT' followed by exactly 8 digits (e.g. NCT12345678). Case-insensitive on input; normalized to uppercase. Surrounding whitespace is trimmed.
NameTypeReqDescription
studyobjectyesFull clinical trial record: protocol summary, design, eligibility criteria, primary outcomes, central contacts, and every US site location.

No examples provided.

clinicaltrials_list_conditions ~172

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') are roll-ups covering many conditions.

NameTypeReqDescription
limitinteger–Maximum conditions to return. Integer in [1, 250]. Default 50.
querystring–Case-insensitive search over condition labels, slugs and synonyms (the raw condition names trial records use). Omit to list the most common conditions.
NameTypeReqDescription
conditionsarrayyesMatching conditions, most-studied first.
totalMatchingintegeryesMatching conditions before the limit was applied.

No examples provided.

clinicaltrials_list_top_conditions ~260

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 come from AACT condition aggregations and refresh daily.

NameTypeReqDescription
citystring–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.
limitinteger–Maximum number of buckets to return from a top-N aggregation. Integer in [1, 25]. Default 10. Aggregator returns buckets sorted by descending count.
statestringyesTwo-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.
NameTypeReqDescription
conditionsarrayyesConditions sorted by descending trial count.
scopeobjectyesEcho of the resolved scope so the caller can confirm what the server interpreted.

No examples provided.

clinicaltrials_list_top_facilities ~244

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 filter.

NameTypeReqDescription
citystringyesUS 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.
limitinteger–Maximum number of buckets to return from a top-N aggregation. Integer in [1, 25]. Default 10. Aggregator returns buckets sorted by descending count.
statestringyesTwo-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.
NameTypeReqDescription
facilitiesarrayyesFacilities sorted by descending trial count.
scopeobjectyesEcho of the resolved scope so the caller can confirm what the server interpreted.

No examples provided.

clinicaltrials_search_trials ~528

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. Use state-only scope first when exploring a region, then narrow to city for facility-level detail.

NameTypeReqDescription
agestring–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.
citystring–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.
conditionstring–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_li…
cursorstring–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 cu…
facilitystring–Exact facility name match. Scopes results to trials running at this named site.
healthyVolunteersOnlyboolean––
interventionTypearray––
pageSizeinteger–Number of results per page. Integer in [1, 50]. Default 20.
phasearray––
sexstring–Biological sex eligibility filter. Use 'female' or 'male'. Trials open to both sexes are returned regardless of this filter.
statestringyesTwo-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.
statusarray––
studyTypearray––
NameTypeReqDescription
nextCursorstring–Opaque cursor to fetch the next page. Absent when no more pages are available.
noMatchHintsarray–Actionable suggestions to broaden the search, present only when totalMatching is zero.
searchCriteriaobjectyesEcho of the applied filter set so the caller can confirm what the server interpreted.
totalMatchingintegeryesTotal trials matching the filters across all pages.
trialsarrayyesTrial records for the current page, sorted newest first by start_date.

No examples provided.

Install

How do I install the Hipa.ai Clinical Trials MCP server?

Hipa.ai Clinical Trials is a hosted endpoint at https://hipa.ai/api/mcp/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 · hipa.ai

# add to Claude Code
claude mcp add --transport http ai-hipa-clinical-trials 'https://hipa.ai/api/mcp/mcp'
Common questions

What is the Hipa.ai Clinical Trials MCP server?

Hipa.ai Clinical Trials is an MCP server listed in the public MCP registry as ai.hipa/clinical-trials. Search recruiting US clinical trials by city, condition, phase and patient eligibility. This page covers its hosted endpoint (https://hipa.ai/api/mcp/mcp).

Is the Hipa.ai Clinical Trials MCP server safe to use?

Hipa.ai Clinical Trials scores 79 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 Hipa.ai Clinical Trials MCP server expose?

Hipa.ai Clinical Trials exposes 8 tools: clinicaltrials_count_trials, clinicaltrials_find_eligible_trials, clinicaltrials_get_data_freshness, clinicaltrials_get_trial, clinicaltrials_list_conditions, and 3 more. Their descriptions and schemas cost roughly 2,248 tokens of context every time the server is loaded.

Does the Hipa.ai Clinical Trials MCP server require authentication?

No. We connected to Hipa.ai Clinical Trials without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Hipa.ai Clinical Trials MCP server still maintained?

Hipa.ai Clinical Trials is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.