Is the Hifarrer Cure Cancer With Ai MCP server down?

mcp-registry/io.github.hifarrer/cure-cancer-with-ai · v1.0.0

Also listed as glama/hifarrer/cure-cancer-with-ai-mcp-server

healthy
Last checked 2026-10-22 10:35 UTC · handshake 127ms

As of 2026-10-22 10:35 UTC, the Hifarrer Cure Cancer With Ai MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 9 outages in 90 days, with a median recovery of 4 minutes.

uptime (30d checks)
100%
checks observed
4,253
outages (90d)
9
tools
15

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

Install Hifarrer Cure Cancer With Ai MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http hifarrer-cure-cancer-with-ai-mcp-server https://www.curecancerwithai.com/api/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "hifarrer-cure-cancer-with-ai-mcp-server": {
      "type": "http",
      "url": "https://www.curecancerwithai.com/api/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (85/100)

B (85/100): 0 error(s), 1 warning(s) across 15 tool(s); ~2,763 tokens of tool definitions.
Scores higher than 48% of 15,518 MCP servers Glimind has audited.
Its tool list costs an agent ~2,763 tokens per session — more than 50% of servers.
85 → 85 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (2)

15 of 15 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: get_blog_post, get_clinical_trial, get_research_paper, list_blog_posts, list_clinical_trials and 10 more

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 12 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.hifarrer%2Fcure-cancer-with-ai/fixes

get_blog_post 1 change
{
  "name": "get_blog_post",
  "description": "Fetch a single blog post by slug, including the full article content.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "description": "Blog post slug, e.g. \"immunotherapy-breakthroughs\"."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get a blog post"
}
get_clinical_trial 1 change
{
  "name": "get_clinical_trial",
  "description": "Fetch a single clinical trial by NCT id (or internal id), including eligibility criteria and locations.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "nctId"
    ],
    "properties": {
      "nctId": {
        "type": "string",
        "description": "NCT id or internal id, e.g. \"NCT01234567\"."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get a clinical trial"
}
get_research_paper 1 change
{
  "name": "get_research_paper",
  "description": "Fetch a single research paper by its internal id or PubMed id.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "idOrPubmedId"
    ],
    "properties": {
      "idOrPubmedId": {
        "type": "string",
        "description": "Internal id or PubMed id, e.g. \"38123456\"."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get a research paper"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.hifarrer/cure-cancer-with-ai"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.hifarrer/cure-cancer-with-ai"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.hifarrer%2Fcure-cancer-with-ai.svg)](https://glimind.com/server/mcp-registry%2Fio.github.hifarrer%2Fcure-cancer-with-ai?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.hifarrer%2Fcure-cancer-with-ai?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.hifarrer%2Fcure-cancer-with-ai.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.hifarrer%2Fcure-cancer-with-ai.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.hifarrer%2Fcure-cancer-with-ai?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:543b617d43cdab88…, first seen 2026-10-17, included at leaf 4442 of 45,446. Version history · verify what your client received.

Tools (15)

Compare: most reliable retrieval servers · most reliable search servers · most reliable knowledge servers · most reliable data servers · most reliable ml servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Hifarrer Cure Cancer With Ai MCP server down right now?

As of 2026-10-22 10:35 UTC, the Hifarrer Cure Cancer With Ai MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 9 outages in 90 days, with a median recovery of 4 minutes.

How many tools does Hifarrer Cure Cancer With Ai MCP server provide?

Hifarrer Cure Cancer With Ai MCP server advertises 15 tools, including get_blog_post, get_clinical_trial, get_research_paper, list_blog_posts, list_clinical_trials.

How do I install Hifarrer Cure Cancer With Ai MCP server?

Point your MCP client at this streamable-http endpoint: https://www.curecancerwithai.com/api/mcp

Is the Hifarrer Cure Cancer With Ai MCP server safe to connect to an AI agent?

Glimind scanned all 15 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Hifarrer Cure Cancer With Ai MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve