MCP.Market

Cure Cancer With AI MCP server

online · 100% uptime
by hifarrer·io.github.hifarrer/cure-cancer-with-ai·v1.0.0
No reviews yet

Free oncology data (research, trials, FDA approvals, news) plus IBM MAMMAL biomedical predictions.

B75/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B75/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Cure Cancer With AI yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Cure Cancer With AI tools (15, 1 write)

write = sends, deletes, buys or posts
  • get_blog_postwrite actionFree

    Fetch a single blog post by slug, including the full article content.

  • get_clinical_trialFree

    Fetch a single clinical trial by NCT id (or internal id), including eligibility criteria and locations.

  • get_research_paperFree

    Fetch a single research paper by its internal id or PubMed id.

  • list_blog_postsFree

    List editorial blog articles (excerpts). Use get_blog_post for full content. Filter by category, cancer-type tag, or keyword.

  • list_clinical_trialsFree

    List clinical trials from public registries (conditions, status, intervention type). Filter by condition, status (e.g. RECRUITING), or keyword.

  • list_compound_characteristicsFree

    List the pharmaceutical-compound characteristics (each scored on the −4…+4 scale) that can be used as preference keys in search_compounds.

  • list_fda_approvalsFree

    List FDA-approved oncology drugs with indication, company, approval date, and label links. Filter by cancer type, keyword, or approval date.

  • list_newsFree

    List curated cancer news articles aggregated from trusted sources. Filter by cancer type, keyword, or published date.

  • list_researchFree

    List peer-reviewed oncology research papers ingested from PubMed (abstracts, authors, journal, plain-language summaries). Filter by cancer type, treatment type, keyword, or publication date.

  • mammal_healthFree

    Check whether the IBM MAMMAL prediction model is loaded and ready. No API key required. Call this before predict_* tools if a prior prediction timed out.

  • predict_clintoxFree

    Predict clinical-trial toxicity for a compound using IBM MAMMAL. Returns pred 1 (toxic / likely to fail trials) or 0 (not toxic) plus a raw score. Inference is CPU-bound and may take up to ~60s.

  • predict_dtiFree

    Predict drug–target binding affinity as pKd (−log10 Kd; higher = stronger binding) using IBM MAMMAL. Inference is CPU-bound and may take up to ~60s.

  • predict_ppiFree

    Predict the binding-affinity class for a pair of proteins using the IBM MAMMAL biomedical foundation model. Returns label "1" (interacting) or "0" (non-interacting). Inference is CPU-bound and may take up to ~60s.

  • search_compoundsFree

    Find pharmaceutical compounds two ways: by example drugs you already know (fuzzy-matched), or by setting target characteristics on a −4…+4 scale. Provide exactly one of `examples` or `preferences`. Use list_compound_characteristics for the available preference names.

  • search_oncologyFree

    Search a keyword across every Cure Cancer With AI dataset at once — research papers, news, blog posts, FDA approvals, and clinical trials — with results grouped by type. Use this first for broad discovery, then fetch a single record by id/slug/nctId for full detail.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 2230ms17/20
  • Tool poisoning15 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 106 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 75/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Cure Cancer With AI compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
75/100
higher than 45% of 48,255 servers
Tools
15
the typical server has 7
Tools that change things
7%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
1,364 ms
faster than 6% of 30,031 servers

What its tools let an agent do: 14 read · 1 change

Install Cure Cancer With AI in Claude Code, Cursor or VS Code

claude mcp add --transport http cure-cancer-with-ai https://www.curecancerwithai.com/api/mcp
Add to Cursor

What the publisher says

From the Cure Cancer With AI repository's README, as published. We do not edit it. Read it on GitHub

Cure Cancer With AI — Public API

A free public REST API and MCP server for oncology data: peer-reviewed research papers (PubMed), curated cancer news, FDA-approved oncology drugs, clinical trials, and a cross-dataset keyword search — plus IBM MAMMAL biomedical foundation-model predictions (protein–protein interaction, drug–target affinity, and ClinTox clinical-trial toxicity).

Base URL: https://www.curecancerwithai.com · Docs: https://www.curecancerwithai.com/developers · OpenAPI 3.1 spec · Agent instructions

What it's for

If you need to programmatically access oncology research, clinical trials, FDA approvals, or cancer news, or to run biomedical model predictions (protein–protein interaction, drug–target binding affinity, drug toxicity), this API gives you clean JSON with a free API key. It's a good fit for research tools, dashboards, chatbots, and AI agents.

Quickstart

  1. Get a free API key — sign in at https://www.curecancerwithai.com/api-keys and click Create key (format ccwlive..., shown once).
  2. Send it on every request as a Bearer token:
curl "https://www.curecancerwithai.com/api/v1/search?q=osimertinib&types=research,fdaApprovals" \
  -H "Authorization: Bearer ccw_live_YOUR_KEY"
  • Auth: Authorization: Bearer ccwlive... (or x-api-key: ccwlive...)
  • Free tier: 100 requests/hour per key (rolling window). Watch X-RateLimit-Remaining; on HTTP 429 wait for Retry-After.
  • List endpoints return { data: [...], pagination: {...} }; single-record endpoints return { data: {...} }; errors return { error: "..." }.

Endpoints

Common query params on list endpoints: limit (1–100, default 20), offset, and usually cancerType, search, from/to. Full details and field lists are in the OpenAPI spec and AGENTS.md.

MCP server (for AI agents)

There's a remote Model Context Protocol server over Streamable HTTP that exposes every endpoint above as a tool, so Claude, ChatGPT, and other MCP clients can call the API directly.

  • Endpoint: https://www.curecancerwithai.com/api/mcp
  • Auth: send Authorization: Bearer ccwliveYOUR_KEY as a header.
{
  "mcpServers": {
    "cure-cancer-with-ai": {
      "url": "https://www.curecancerwithai.com/api/mcp",
      "headers": { "Authorization": "Bearer ccw_live_YOUR_KEY" }
    }
  }
}

Tools: searchoncology, listresearch, getresearchpaper, listnews, listblogposts, getblogpost, listfdaapprovals, listclinicaltrials, getclinicaltrial, predictppi, predictdti, predictclintox, mammal_health. See mcp/.

Examples

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Cure Cancer With AI: common questions

Is Cure Cancer With AI MCP server safe?
Mostly: it is graded B (75/100). Read the Cure Cancer With AI safety report
How do I install Cure Cancer With AI?
It runs remotely at www.curecancerwithai.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Cure Cancer With AI need an API key?
Yes. The registry entry asks for Authorization.
Is Cure Cancer With AI maintained?
The last commit was 145 days ago (2026-06-12). The latest release is v1.0.0.
Is Cure Cancer With AI up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Cure Cancer With AI compare with other MCP servers?
safety score 75/100 (higher than 45% of 48,255 servers); tools 15 (the typical server has 7); tools that change things 7% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.