Health · Remote MCP server

Cure Cancer With AI

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

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.hifarrer/cure-cancer-with-ai
Version
1.0.0
Status
Active
Category
health
Transport
Streamable HTTP
Published
2026-06-12
Updated
2026-06-12
Publisher
hifarrer (GitHub) · 2 servers with pages here
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/hifarrer) · how
Repository
github.com/hifarrer/ccwai-api
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://www.curecancerwithai.com/api/mcpAuthorization (required, secret)

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 200)
Handshake
cure-cancer-with-ai 1.0.0 · protocol 2025-06-18
Tools discovered
15 - show namessearch_oncology, list_research, get_research_paper, list_news, list_blog_posts, get_blog_post, list_fda_approvals, list_clinical_trials, get_clinical_trial, predict_ppi, predict_dti, predict_clintox, search_compounds, list_compound_characteristics, mammal_health
Checked on
2026-10-05

How the live check works

How to connect Cure Cancer With AI

Cure Cancer With AI is a remote MCP server: there is nothing to install. Its endpoint is https://www.curecancerwithai.com/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More from hifarrer (GitHub)

All 2 →
ServerRunsEndpoint or package
FFMPEG APIHosted MCP tools for FFmpeg-style video and audio processing through FFMPEG API.Remote · HTTPLive check: sign-in requiredmcp.ffmpegapi.net

More health servers

All 381 →
ServerRunsEndpoint or package
CounterScript - Drug Price BenchmarksFree US drug-price benchmarks from federal data (CMS NADAC): a benchmark, not a price anyone owes.Remote · HTTPLive check: ✓ handshakerx.agentlookups.ai
Coverage ExceptionWhy Medicare Part D restricts a drug, and the exception and appeal path to challenge it.Remote · HTTPLive check: ✓ handshakeinsurewith.ai
CredcycleProvider credentialing & payer-enrollment tracking for medical practices - read-only demo tools.Remote · HTTPLive check: ✓ handshakecredcycle.artificl.us
Cup24.it AvailabilitySearch private healthcare appointment availability across Cup24.it: services, doctors, clinics.Remote · HTTPLive check: ✗ no handshakemcpserver.cup24.it
DailymedDailyMed MCP - FDA Structured Product Labels via NLM.Remote · HTTPLive check: ✓ handshakegateway.pipeworx.io
DailymedSearch DailyMed drug labels, SPLs, NDCs and packaging.Remote · HTTPLive check: ✓ handshakedailymed.usefulapi.io
Dailymed MCPFDA drug label information from DailyMed. No key required.Local · stdionpm: dailymed-mcp
Datasignals Lab Events MCPTwelve US filing and career-site streams in one schema: SEC, FDA, NIH, contracts, Congress, hiring.Remote & Local · HTTP, stdioLive check: sign-in requiredmcp.apify.com