Cure Cancer With AI
REMOTE · WWW.CURECANCERWITHAI.COM
Free oncology data (research, trials, FDA approvals, news) plus IBM MAMMAL biomedical predictions.
Available components
Last scanned (1 hour ago)
Scores higher than 79% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category Health and Science
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://www.curecancerwithai.com/api/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.curecancerwithai.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| curecancerwithai.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.curecancerwithai.com/api/mcp | Unreachable | ||
| http (plaintext) | http://www.curecancerwithai.com/api/mcp | HTTPS enforced |
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 →
get_blog_post Get a blog post ~44
Fetch a single blog post by slug, including the full article content.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Blog post slug, e.g. "immunotherapy-breakthroughs". |
No output schema declared.
No examples provided.
get_clinical_trial Get a clinical trial ~56
Fetch a single clinical trial by NCT id (or internal id), including eligibility criteria and locations.
| Name | Type | Req | Description |
|---|---|---|---|
| nctId | string | yes | NCT id or internal id, e.g. "NCT01234567". |
No output schema declared.
No examples provided.
get_research_paper Get a research paper ~50
Fetch a single research paper by its internal id or PubMed id.
| Name | Type | Req | Description |
|---|---|---|---|
| idOrPubmedId | string | yes | Internal id or PubMed id, e.g. "38123456". |
No output schema declared.
No examples provided.
list_blog_posts List blog posts ~110
List editorial blog articles (excerpts). Use get_blog_post for full content. Filter by category, cancer-type tag, or keyword.
| Name | Type | Req | Description |
|---|---|---|---|
| cancerType | string | – | Filter by cancer-type tag. |
| category | string | – | Filter by primary category. |
| limit | integer | – | Results per page (1–100, default 20). |
| offset | integer | – | Number of results to skip (default 0). |
| search | string | – | Keyword search across title, excerpt, and content. |
No output schema declared.
No examples provided.
list_clinical_trials List clinical trials ~119
List clinical trials from public registries (conditions, status, intervention type). Filter by condition, status (e.g. RECRUITING), or keyword.
| Name | Type | Req | Description |
|---|---|---|---|
| condition | string | – | Filter by condition. |
| limit | integer | – | Results per page (1–100, default 20). |
| offset | integer | – | Number of results to skip (default 0). |
| search | string | – | Keyword search across title and description. |
| status | string | – | Filter by trial status, e.g. RECRUITING. |
No output schema declared.
No examples provided.
list_compound_characteristics List compound characteristics ~41
List the pharmaceutical-compound characteristics (each scored on the −4…+4 scale) that can be used as preference keys in search_compounds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_fda_approvals List FDA approvals ~165
List FDA-approved oncology drugs with indication, company, approval date, and label links. Filter by cancer type, keyword, or approval date.
| Name | Type | Req | Description |
|---|---|---|---|
| cancerType | string | – | Filter by cancer type, e.g. lung, breast, prostate, colorectal, melanoma, leukemia, lymphoma. |
| from | string | – | ISO date lower bound (e.g. 2024-01-01). |
| limit | integer | – | Results per page (1–100, default 20). |
| offset | integer | – | Number of results to skip (default 0). |
| search | string | – | Keyword search across drug name, generic name, and indication. |
| to | string | – | ISO date upper bound (e.g. 2024-12-31). |
No output schema declared.
No examples provided.
list_news List cancer news ~152
List curated cancer news articles aggregated from trusted sources. Filter by cancer type, keyword, or published date.
| Name | Type | Req | Description |
|---|---|---|---|
| cancerType | string | – | Filter by cancer type, e.g. lung, breast, prostate, colorectal, melanoma, leukemia, lymphoma. |
| from | string | – | ISO date lower bound (e.g. 2024-01-01). |
| limit | integer | – | Results per page (1–100, default 20). |
| offset | integer | – | Number of results to skip (default 0). |
| search | string | – | Keyword search across title, summary, and content. |
| to | string | – | ISO date upper bound (e.g. 2024-12-31). |
No output schema declared.
No examples provided.
list_research List research papers ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cancerType | string | – | Filter by cancer type, e.g. lung, breast, prostate, colorectal, melanoma, leukemia, lymphoma. |
| from | string | – | ISO date lower bound (e.g. 2024-01-01). |
| limit | integer | – | Results per page (1–100, default 20). |
| offset | integer | – | Number of results to skip (default 0). |
| search | string | – | Keyword search across title and abstract. |
| to | string | – | ISO date upper bound (e.g. 2024-12-31). |
| treatmentType | string | – | Filter by treatment type. |
No output schema declared.
No examples provided.
mammal_health Check MAMMAL model health ~42
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
predict_clintox Predict clinical-trial toxicity (ClinTox) ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| smiles | string | yes | Compound structure in SMILES notation. |
No output schema declared.
No examples provided.
predict_dti Predict drug–target interaction (pKd) ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| drug_seq | string | yes | Drug structure in SMILES notation. |
| norm_y_mean | number | – | Optional normalization mean override. |
| norm_y_std | number | – | Optional normalization standard-deviation override. |
| target_seq | string | yes | Target protein amino-acid sequence (single-letter codes). |
No output schema declared.
No examples provided.
predict_ppi Predict protein–protein interaction ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| protein_a | string | yes | Amino-acid sequence, single-letter codes (ACDEFGHIKLMNPQRSTVWY), no FASTA header. |
| protein_b | string | yes | Amino-acid sequence, single-letter codes. |
No output schema declared.
No examples provided.
search_compounds Search pharmaceutical compounds ~184
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.
| Name | Type | Req | Description |
|---|---|---|---|
| examples | array | – | Known drug names to find similar compounds for, e.g. ["aspirin","ibuprofen"]. Mutually exclusive with preferences. |
| include_characteristics | boolean | – | Include each result’s characteristic scores in the response. |
| limit | integer | – | Max results (1–100, default 20). |
| preferences | object | – | Map of characteristic name to desired value on the −4…+4 scale, e.g. {"Neuroactive":3,"Immunoactive":-2}. Omit a characteristic to ignore it. Mutually exclusive with examples. |
No output schema declared.
No examples provided.
search_oncology Search all oncology datasets ~163
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cancerType | string | – | Filter by cancer type, e.g. lung, breast, prostate, colorectal, melanoma, leukemia, lymphoma. |
| limit | integer | – | Max results per dataset (1–100, default 5). |
| q | string | yes | The keyword to search for, e.g. "osimertinib". |
| types | string | – | Optional comma-separated datasets to narrow to: research,news,blog,fdaApprovals,clinicalTrials. |
No output schema declared.
No examples provided.
How do I install the Cure Cancer With AI MCP server?
Cure Cancer With AI is a hosted endpoint at https://www.curecancerwithai.com/api/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 · www.curecancerwithai.com
claude mcp add --transport http hifarrer-cure-cancer-with-ai 'https://www.curecancerwithai.com/api/mcp'
What is the Cure Cancer With AI MCP server?
Cure Cancer With AI is an MCP server listed in the public MCP registry as io.github.hifarrer/cure-cancer-with-ai. Free oncology data (research, trials, FDA approvals, news) plus IBM MAMMAL biomedical predictions. This page covers its hosted endpoint (https://www.curecancerwithai.com/api/mcp).
Is the Cure Cancer With AI MCP server safe to use?
Cure Cancer With AI 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 Cure Cancer With AI MCP server expose?
Cure Cancer With AI exposes 15 tools: search_oncology, list_research, get_research_paper, list_news, list_blog_posts, and 10 more. Their descriptions and schemas cost roughly 1,605 tokens of context every time the server is loaded.
Does the Cure Cancer With AI MCP server require authentication?
Its publisher declares that Cure Cancer With AI requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.
Is the Cure Cancer With AI MCP server still maintained?
Cure Cancer With AI is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.