// SCAN REPORT

Cure Cancer With AI

15 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 16 Aug 2026

2 can modify or destroy data

13 read-only

15 tools total

Community server · catalogue entry checked 16/08/2026 · full schemas captured for 13 of 15 tools

How to control Cure Cancer With AI ↓

TOOL MAP

What Cure Cancer With AI exposes to your agents

Read (13) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Cure Cancer With AI costs in tokens

2,373 tokens of tool definitions, loaded on every request

1.2% of a 200k context window

261 heaviest tool: search_compounds

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Cure Cancer With AI tools

Execute · Medium predict_dti This tool triggers an external AI/ML inference computation via IBM MAMMAL, making it Execute. Execute · Medium predict_ppi This tool executes a remote/local CPU-bound machine learning inference job against the IBM MAMMAL foundation model.

2 of Cure Cancer With AI's 15 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Cure Cancer With AI

PolicyLayer is an MCP gateway — it sits between your AI agents and Cure Cancer With AI, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "get_blog_post": {
    "limits": [
      {
        "counter": "get_blog_post_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Cure Cancer With AI — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON CURE CANCER WITH AI →

Instant setup, no code required.

FULL CATALOGUE

All 15 Cure Cancer With AI tools

EXECUTE 2 tools

Execute predict_dti Predict drug–target binding affinity as pKd (−log10 Kd; higher = stronger binding) using IBM MAMMAL. Inference Execute predict_ppi Predict the binding-affinity class for a pair of proteins using the IBM MAMMAL biomedical foundation model. Re

READ 13 tools

Read get_blog_post Fetch a single blog post by slug, including the full article content. Read get_clinical_trial Fetch a single clinical trial by NCT id (or internal id), including eligibility criteria and locations. Read get_research_paper Fetch a single research paper by its internal id or PubMed id. Read list_blog_posts List editorial blog articles (excerpts). Use get_blog_post for full content. Filter by category, cancer-type t Read list_clinical_trials List clinical trials from public registries (conditions, status, intervention type). Filter by condition, stat Read list_compound_characteristics List the pharmaceutical-compound characteristics (each scored on the −4…+4 scale) that can be used as preferen Read list_fda_approvals List FDA-approved oncology drugs with indication, company, approval date, and label links. Filter by cancer ty Read list_news List curated cancer news articles aggregated from trusted sources. Filter by cancer type, keyword, or publishe Read list_research List peer-reviewed oncology research papers ingested from PubMed (abstracts, authors, journal, plain-language Read mammal_health Check whether the IBM MAMMAL prediction model is loaded and ready. No API key required. Call this before predi Read predict_clintox Predict clinical-trial toxicity for a compound using IBM MAMMAL. Returns pred 1 (toxic / likely to fail trials Read search_compounds Find pharmaceutical compounds two ways: by example drugs you already know (fuzzy-matched), or by setting targe Read search_oncology Search a keyword across every Cure Cancer With AI dataset at once — research papers, news, blog posts, FDA app

FAQ

Questions about Cure Cancer With AI

Is the Cure Cancer With AI MCP server safe to use without restrictions? +

The Cure Cancer With AI server is primarily read-only with 13 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Cure Cancer With AI MCP server expose? +

15 tools across 1 categories: Read. 13 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Cure Cancer With AI? +

Register the Cure Cancer With AI MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Cure Cancer With AI tool call.

Deterministic rules across all 15 Cure Cancer With AI tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON CURE CANCER WITH AI →

Instant setup, no code required.

15 Cure Cancer With AI tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Cure Cancer With AI's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →