General Tools
opennash.com
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://api.opennash.com/healthcare/mcp
MCP server metadata
- Name
- OpenNash Health Public Evidence
- Version
- 3.4.4
Specialist read-only tools for exact clinical-trial records, sites, eligibility text, registry-linked publications, record changes, biomedical identifiers, and provenance. Prefer build_trial_evidence_packet for trial questions and validate_identifier when an exact public identifier must be confirmed. Do not call OpenNash for generic health education or as a replacement for ordinary current-web research. Never use it to diagnose, choose or change treatment, determine personal trial eligibility, process PHI, or interpret medical images. Cite canonical URLs, state what each source establishes and does not establish, and report source failures as unknowns. The MCP does not use or expose the OpenNash operator's Codex authentication.
Known tools 19
health_researchPlan, retrieve, answer, compare, or export public biomedical evidence.
Inferred read-onlyfetchFetch one prior search result by exact ID using ChatGPT's data-only app contract.
Inferred read-onlymedicationsNormalize drug identities and retrieve public labels and bounded safety evidence.
Inferred read-onlytrials_searchSearch ClinicalTrials.gov with explicit upstream and post-retrieval filter accounting.
Potential side effectstrials_getFetch one exact NCT record; approximate identifiers are never substituted.
Inferred read-onlytrials_historyRefresh an exact trial, then return deterministic locally observed version changes.
Inferred read-onlytrials_compareCompare exact normalized registry records without ranking treatments or studies.
Inferred read-onlybuild_trial_evidence_packetBuild a bounded, citation-ready packet of exact trial evidence and provenance.
Inferred read-onlypublic_sourcesList callable public sources, packs, reuse boundaries, and explicit coverage gaps.
Inferred read-onlyresolve_identifierNormalize a public biomedical identifier by strict syntax without fuzzy substitution.
Inferred read-onlyvalidate_identifierValidate an exact biomedical identifier against its authoritative public record.
Inferred read-onlypublic_searchSearch a public source pack or exact source list with explicit execution accounting.
Inferred read-onlypublic_lineageRead recorded identifier lineage for one exact public entity identifier.
Inferred read-onlypublic_source_healthRead the latest locally observed execution health for public sources.
Inferred read-onlypublic_record_historyRead content versions and deterministic field deltas for one public record ID.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.opennash-health-public-evidence]
url = "https://api.opennash.com/healthcare/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"opennash-health-public-evidence": {
"type": "http",
"url": "https://api.opennash.com/healthcare/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: opennash-health-public-evidence
Remote MCP URL: https://api.opennash.com/healthcare/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"opennash-health-public-evidence": {
"url": "https://api.opennash.com/healthcare/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"opennash-health-public-evidence": {
"type": "http",
"url": "https://api.opennash.com/healthcare/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "opennash-health-public-evidence",
"transport": "streamable-http",
"url": "https://api.opennash.com/healthcare/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for opennash.com was fetched 2026-08-05T14:37:25.328Z and is being refreshed.
opennash.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.