Reverse engineering. The MCP server returns general oncology information that the README says is work in progress and not medical advice, so outputs must not guide treatment decisions.
Who it is forAn AI agent builder or a researcher whose agent needs cited oncology facts about a specific cancer, treatment or trial.
The problemGeneral language models often state oncology facts without checkable sources or country-specific approval status.
The outcomeThe agent answers from On Co records, with a TL;DR, approval status for a chosen country and primary source links for each claim.
What you need first
- Node.js and npm (inferred, needed for the repository scripts)
- Git and a GitHub account for cloning the repository or opening issues and pull requests
- An MCP-capable client or agent for the MCP server (optional)
Steps
- Install Node.js so that npx is available. (inferred, check the README)
- Add an MCP server entry to your client that runs
npx -y onco-mcp. - Ask the agent to search On Co for a cancer type, then fetch one treatment record.
- Ask the agent to compare two treatments and list the primary source link for each fact.
- Open each source link and confirm it matches the claim before using the answer.
Prompt for your agent
Using the OnCo MCP server started with `npx -y onco-mcp` from the judegomila/OnCo repository, search for <cancer type>, fetch the treatment record for <treatment name>, and return its TL;DR, its approval status for <country>, and every primary source link. Verify that each link resolves before reporting, and state any field the record marks as no data.
Caveat. The README says facts may be incomplete, out of date or wrong, so every answer needs checking against the primary source linked on each page.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page