Skip to content

Zetesis Scientific Due Diligence

by reutavidan · remote · local (pypi) · no sign-in to list tools · v0.2.2 · published by GitHub user reutavidan

Due diligence on life-science claims: omics, trials, gene therapy. Dimension by dimension.

Changes · 4

4 tools: 4 change things.

Scanned Oct 21, 2026

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http zetesis https://api.zetesis.science/mcp

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "evaluate_claim" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The name "evaluate_claim" says "evaluate": a word for a change.

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Changes things 4Claude Code: ask
  • evaluate_claimRun Zetesis's graded reading of a scientific, biomedical, clinical, or AI/ML claim.1 finding

    Why it is in this group

    • The name "evaluate_claim" says "evaluate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "evaluate_claim" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The name "evaluate_claim" says "evaluate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Run Zetesis's graded reading of a scientific, biomedical, clinical, or AI/ML claim. Grades each evidence dimension and returns an overall reading, with every source cited by hard public id (PMID, DOI, NCT, NIH grant, SEC filing). Covers drug, omics, target-validation, diagnostic, and AI-model claims. Runs the hosted engine end to end and typically takes a couple of minutes, long enough that some clients background or time out the call. The output is Zetesis's own reading as a finished artifact. zetesis_scope and zetesis_evidence return the same dated sources and the same grading rubric immediately and without running a model, at full source depth rather than abstract level. A signed, independently re-checkable dossier is available by request at the Zetesis site. Args: claim: the claim to evaluate, in one or two sentences. context: optional background (stage, field, the decision at hand). documents: optional source text (a deck, abstract, or paper). as_of: year the claim was made. Set it for any claim that is not brand new. It restricts evidence to what existed then, which both keeps later outcomes out of the reading and sharply improves what is retrieved: left open, a pivotal trial report competes with every paper published since and gets buried.

    Annotations the server declares

    • title: Evaluate a scientific or AI claim
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • verify_attestationVerify a Zetesis attestation, confirming an evaluation's claim, evidence, and conclusion have not been altered since it was signed.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Verify a Zetesis attestation, confirming an evaluation's claim, evidence, and conclusion have not been altered since it was signed. Use when someone has a Zetesis dossier or attestation and wants to independently re-check it. Args: attestation_json: the full attestation object as JSON text.

    Annotations the server declares

    • title: Verify a Zetesis attestation
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • zetesis_evidenceStep 2 of a Zetesis evaluation.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Step 2 of a Zetesis evaluation. Runs the search queries against public evidence sources (Europe PMC, ClinicalTrials.gov, openFDA, and optionally NIH RePORTER and SEC EDGAR) and returns a deduplicated bundle where every source carries a hard public id, followed by the Zetesis grading rubric so you can grade the dimensions yourself. With as_of set, retrieval is fenced to sources published, registered, or filed on or before 31 December of that year, and two fields that leak later outcomes are suppressed: a trial's present-day status, and FDA labels effective after the cutoff. That makes it possible to judge a claim on what was actually knowable at the time. Runs no model, costs nothing, and returns immediately. Takes the queries worked out when the claim was scoped. Args: queries: 3 to 6 short keyword phrases. Query 1 should be the bare name of the thing claimed about (a drug, compound code, model, or gene); query 2 that name plus at most two outcome words. Longer phrases retrieve commentary rather than the primary report. If the claim names no agent at all (a behaviour, diet, procedure, exposure or policy), anchor on the field's own technical term instead of the lay one ("time restricted eating", not "intermittent fasting"), pair it with the outcome as the field measures it, and allow one design word such as crossover or randomized in one later query. Without an entity name that design word is the only thing separating a trial report from a review of trial reports. as_of: optional cutoff year, as used in zetesis_scope. include_capital: also retrieve funding and public-filing signal.

    Annotations the server declares

    • title: Retrieve dated public evidence for a claim
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • zetesis_scopeScope a scientific, biomedical, clinical, or AI/ML claim for evaluation.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Scope a scientific, biomedical, clinical, or AI/ML claim for evaluation. Returns three things: the source catalog, meaning where the evidence for this claim class lives; the diligence apparatus for that class, meaning the questions a domain reviewer asks and the failure patterns that have caught comparable claims before; and the scoping rubric used to work out which evidence dimensions bear on this particular claim and what to search for. Applies to a research claim, a study, a paper, an abstract, a preprint, a grant or a pitch, and to checking a paper or statistic before relying on it. Runs no model, costs nothing, and returns immediately. The queries worked out from its output are what zetesis_evidence takes as input. With as_of set, the apparatus and rubric are framed for judging the claim as it stood at the end of that year. Args: claim: the claim to evaluate, in one or two sentences. context: optional background (stage, field, the decision at hand). as_of: optional year. Set it to evaluate the claim as it stood at the end of that year, grading how it was derived at the time rather than how it turned out. claim_class: optional override for the routed claim class. The response lists every class; pass one back if the routing picked wrongly, or if nothing routed.

    Annotations the server declares

    • title: Scope a claim for evaluation
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.2.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http zetesis https://api.zetesis.science/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__zetesis__evaluate_claim",
      "mcp__zetesis__zetesis_scope",
      "mcp__zetesis__zetesis_evidence",
      "mcp__zetesis__verify_attestation"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as zetesis. Review it before you use it.