search_oncologyLABSCO SUMMARY
Cross-dataset search is the query the separate sources cannot answer.
PubMed, ClinicalTrials.gov and the FDA approvals list each have their own interface and their own idea of what a query means. Asking one question across all of them — what does the literature say about this drug, is it in trials, has it been approved — is the thing this makes cheap. The MAMMAL predictions are a different kind of output and should be read as model estimates with the confidence that implies, not as findings; the free tier's 100 requests an hour is enough for research and not enough for a batch job.
What it is
A remote MCP server over the Cure Cancer With AI public API. It puts five oncology datasets behind one connection — peer-reviewed papers from PubMed, curated news, FDA-approved oncology drugs, clinical trials from public registries, and a cross-dataset search — and adds three IBM MAMMAL foundation-model predictions on top.
What you get
- A keyword search across every dataset at once, rather than four separate queries —
search_oncology - Peer-reviewed oncology papers listed and fetched individually —
list_research,get_research_paper - Curated cancer news and editorial blog posts, with excerpts on the list and full content on the single item —
list_news,list_blog_posts,get_blog_post - FDA-approved oncology drugs, and clinical trials with eligibility and locations on the single-trial call —
list_fda_approvals,list_clinical_trials,get_clinical_trial - Three MAMMAL model predictions: protein–protein interaction, drug–target binding affinity as pKd, and ClinTox clinical-trial toxicity, with a health check for the engine —
predict_ppi,predict_dti,predict_clintox,mammal_health - List endpoints that page properly, with
limitbetween 1 and 100 defaulting to 20, anoffset, and filters on cancer type, search text and a date range
Requirements
A free API key — sign in at curecancerwithai.com/api-keys and create one; it is shown once and looks like ccw_live_.... Connect to https://www.curecancerwithai.com/api/mcp over Streamable HTTP with the key as a bearer token in the Authorization header. The free tier allows 100 requests per hour per key on a rolling window; watch the remaining-requests header and wait for Retry-After on a 429. Everything returned is informational and not medical advice, and the vendor asks that source URLs be cited when results are shown to a user.
Setup effort
Paste a URL with a key — add the endpoint to your client
USE CASES
Getting the whole picture on one drug
Run the cross-dataset search on the name and read research, approvals, trials and news together instead of four separate lookups.
Finding trials a patient might match
List trials filtered by cancer type, then fetch the single trial for its eligibility criteria and locations.
Checking what has actually been approved
List FDA-approved oncology drugs with a date range, rather than inferring approval status from press coverage.
Screening a compound before wet-lab work
Run the drug–target affinity and toxicity predictions to prioritise candidates, treating the output as a screen rather than a result.
Keeping up with a specific cancer type
Filter research and news by cancer type with a date range, and page through with the limit and offset.
13 tools
Listed in project docs. Your client may show a different list.
list_researchget_research_paperlist_newslist_blog_postsget_blog_postlist_fda_approvalslist_clinical_trialsget_clinical_trialpredict_ppipredict_dtipredict_clintoxmammal_healthBEFORE YOU INSTALL
What to know first
Tools you get
13 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
INSTALLATION
Connect your client
Add the endpoint to your client.
Server setup
https://www.curecancerwithai.com/api/mcp