MCP.Market

Globocan MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/globocan·v0.2.1

GLOBOCAN — the IARC/WHO Global Cancer Observatory.

B73/100grade B
What users say
No reviews yet
Be the first
Safety scan
B73/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Globocan yet.

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

Globocan tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Globocan compares

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

Safety score
73/100
higher than 39% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
39 ms
faster than 94% of 30,031 servers

Release history: 7 versions in the registry since 2026-09-14, latest 2026-11-02, typically one every 10 days.

Install Globocan in Claude Code, Cursor or VS Code

claude mcp add --transport http globocan https://gateway.pipeworx.io/globocan/mcp
Add to Cursor

What the publisher says

From the Globocan repository's README, as published. We do not edit it. Read it on GitHub

GLOBOCAN — Global Cancer Observatory (IARC/WHO)

Cancer incidence, mortality and 5-year prevalence for 238 countries and territories across 41 cancer sites: new cases, deaths, age-standardised rates per 100,000, and cumulative risk to age 74.

Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.

Attribution — a condition of use, not a courtesy

IARC permits free use of these data but not sale, and requires the source to be acknowledged. Every response carries the credit, and the note travels with the mirrored rows so it cannot be dropped downstream.

IARC / WHO Global Cancer Observatory (GLOBOCAN). Free to use, not for sale; source acknowledged as a condition of use.

Tools

Why this is a mirror

gco-api.iarc.fr refuses both of our compute environments while serving a laptop in about a second:

TLS is not the cause — the certificate is valid for the host (SAN .iarc.fr) and verifies clean — so this is a deliberate refusal of datacenter ranges. The standard egress-relay fix does not** work, because the block is not Cloudflare-specific.

The block affects serving, not ingesting. Data is fetched once from an allowed connection and read here from Postgres. GLOBOCAN is an annual estimate release, so a mirror costs nothing in freshness.

Refreshing

<store credentials in the environment> node scripts/ingest-globocan.mjs

Run it from a laptop, not CI or a Worker — see above. If it starts hanging, you are probably on a cloud host. It is idempotent (upserts on the natural key), so re-running is safe. Once a year is enough.

Schema: supabase/migrations/067globocanmirror.sql.

Gotchas

  1. The dimensions are bare integers and the measure is the dangerous one. Upstream calls it type; the mirror stores it as measure precisely because type says nothing. 0 = incidence, 1 = mortality, 2 = prevalence. Handing back a raw row lets 632,166 US cancer deaths read as new cases, or an 8-million prevalence figure read as an annual count. Every number this pack returns is labelled.

The encodings were pinned against published US figures — 2,462,729 / 632,166 / 8,069,773 — not assumed.

  1. cancercode 39 is "All cancers"** (C00-97), not a site. It is excluded from the leading-site rankings; leaving it in puts a row worth 100% at the top of every list.
  1. Sex-specific sites have no both-sexes row. Asking for a male-only site with sex: "female" returns no_estimate with the reason — the standard being coherent, not a gap in the data.
  1. These are modelled estimates, not case counts. IARC estimates national burden from registry data of varying completeness. For observed registry counts see CI5 (Cancer Incidence in Five Continents), which is a different dataset answering a different question.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "globocan": {
      "url": "https://gateway.pipeworx.io/globocan/mcp"
    }
  }
}

What this endpoint actually serves

Shortened. The full README is on GitHub.

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

Grade history

  • 2026-10-03downgradeA → Bscore 73
  • 2026-09-19restoreB → Ascore 87

Globocan: common questions

Is Globocan MCP server safe?
Mostly: it is graded B (73/100). Read the Globocan safety report
How do I install Globocan?
It runs remotely at gateway.pipeworx.io. 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 Globocan need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Globocan maintained?
The last commit was 39 days ago (2026-09-26). The latest release is v0.2.1.
Is Globocan up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Globocan compare with other MCP servers?
safety score 73/100 (higher than 39% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 39 ms (faster than 94% of 30,031 servers). Full comparison.

More from pipeworx-io →