Documentation
Connecting to PolarisRay
PolarisRay serves each dataset as an MCP server over HTTP. Point any MCP-capable client at the endpoint — public sources need no API key.
Endpoints
Every live source lives under a path on mcp.polarisray.com:
https://mcp.polarisray.com/maudehttps://mcp.polarisray.com/faershttps://mcp.polarisray.com/recallshttps://mcp.polarisray.com/clinical_trialshttps://mcp.polarisray.com/dailymedhttps://mcp.polarisray.com/splhttps://mcp.polarisray.com/federated
https://mcp.polarisray.com/<source>
Browse the catalog for tools, examples, and
disclaimers. /federated searches MAUDE, ClinicalTrials.gov,
DailyMed, openFDA SPL, and FDA recalls in one call;
FAERS is a separate live server (not included
in federated). Conference search is planned under /conferences.
Sourced results
Search and get tools return a url when a public detail page
exists — DailyMed and openFDA drug labels, ClinicalTrials.gov studies, FDA
MAUDE device reports, and FDA iRES recall records — so you can open the
primary source. FAERS is different: FDA does
not publish a per-case web page, so hits link to the quarterly extract,
not an individual case.
Claude Desktop / Claude Code
Add the server to your MCP config (claude_desktop_config.json,
or via claude mcp add):
{
"mcpServers": {
"polarisray-maude": {
"url": "https://mcp.polarisray.com/maude"
},
"polarisray-faers": {
"url": "https://mcp.polarisray.com/faers"
},
"polarisray-recalls": {
"url": "https://mcp.polarisray.com/recalls"
},
"polarisray-clinical-trials": {
"url": "https://mcp.polarisray.com/clinical_trials"
},
"polarisray-dailymed": {
"url": "https://mcp.polarisray.com/dailymed"
},
"polarisray-spl": {
"url": "https://mcp.polarisray.com/spl"
},
"polarisray-federated": {
"url": "https://mcp.polarisray.com/federated"
}
}
} Other clients
Any client that supports remote MCP over HTTP works the same way — supply the endpoint URL. This includes Cursor, VS Code (MCP extension), and custom agents built on the MCP SDKs.
Authentication
Public datasets are open and require no credentials. Sources that wrap
rate-limited or licensed data will document an api-key flow on
their individual pages.