Zetesis Scientific Due Diligence

io.github.reutavidanPublished by GitHub account reutavidanv0.2.2Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableKnowledge & MemoryData & AnalyticsAI & ML

Overview

AI-generated overview

Zetesis evaluates scientific, biomedical, clinical and AI/ML claims against public evidence, returning cited sources, reviewer questions and failure patterns.

What you can do
Scope a claim to its scientific class, returning the source catalog, reviewer questions and failure-pattern taxonomy with counterexamples, optionally fenced to an earlier year so only evidence available by then is used. Run searches against Europe PMC, ClinicalTrials.gov, openFDA, NIH RePORTER and SEC EDGAR and get a deduplicated evidence bundle with hard public identifiers plus a grading rubric. Produce Zetesis's own graded reading of a claim, dimension by dimension, with an overall assessment. Verify a signed Zetesis attestation to confirm its claim, evidence and conclusion have not been altered.
When to use it
Useful when checking whether published evidence supports a life-science, clinical or AI/ML claim, such as an abstract, paper, grant or investor deck, and when judging a claim on what was knowable in its own year rather than with hindsight. Also for independently re-checking a Zetesis dossier someone shares.
Requirements
The hosted endpoint needs no account, key or token. The older stdio Python client (zetesis package via uvx) needs a ZETESIS_TOKEN access token, requested from Zetesis; verification works without one. Network access to the Zetesis API and the public evidence sources is required.
Before you install
evaluate_claim sends claim text to a model sub-processor named in Zetesis's privacy policy; the evidence and scope tools send nothing to a model provider. Claim text is not logged, only metadata such as routed class and counts. The stdio client requires the ZETESIS_TOKEN secret and proxies every call to the hosted engine. The hosted engine is a separate service from the MIT-licensed code.

Installation

In SourceWeft

  1. Open Zetesis Scientific Due Diligence in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.reutavidan%2Fzetesis/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "zetesis-scientific-due-diligence": {
      "type": "http",
      "url": "https://api.zetesis.science/mcp"
    }
  }
}

README

Zetesis

Available on Smithery

Scientific due diligence on a claim, from inside Claude, Copilot, or any MCP host.

Give Zetesis a claim, an abstract, a paper, a grant or a deck. It routes the claim to its scientific class, then returns the questions a domain reviewer would ask, the failure patterns that caught comparable claims before, and the public evidence bearing on it, with a PMID, DOI, NCT number, NIH grant number or SEC filing reference on every source. Every identifier it hands back was retrieved. None are generated.

It can also evaluate a claim as it stood in an earlier year, restricting evidence to what existed by then, so a claim is judged on what was knowable at the time rather than on how it turned out.

Install

No account, key or token is required for any of these.

WhereCommand
Terminal chatuv tool install zetesis, then run zetesis (or pipx install zetesis)
Claude Codeclaude mcp add --transport http zetesis https://api.zetesis.science/mcp
Claude Code plugin (tools plus skills)/plugin marketplace add reutavidan/zetesis-plugin, then /plugin install zetesis@zetesis
Codexcodex mcp add zetesis --url https://api.zetesis.science/mcp
Gemini CLIgemini mcp add --transport http zetesis https://api.zetesis.science/mcp
Browserhttps://api.zetesis.science/app

Chat in the terminal

bash
uv tool install zetesis     # or: pipx install zetesiszetesis

zetesis opens a chat in the terminal with the hosted Zetesis agent. Ask a question, or drag a deck or paper (PDF, DOCX or PPTX) into the window, and watch it scope the claim, search the dated record and grade each dimension. Follow-up questions use the same evidence. /help lists the commands (/attach, /sources, /new, /web). No account or key is needed.

Connect it

The hosted server is at https://api.zetesis.science/mcp, over Streamable HTTP. No account, key or token is required.

Claude Code:

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

Claude Desktop (claude_desktop_config.json):

json
{  "mcpServers": {    "zetesis": {      "type": "http",      "url": "https://api.zetesis.science/mcp"    }  }}

Any other MCP client:

ClientHow
Microsoft Copilot StudioTools, then Add a tool, then Model Context Protocol. Server URL, auth None.
ChatGPTSettings, then Connectors, then Developer mode. Add the URL.
Gemini CLIgemini mcp add --transport http zetesis https://api.zetesis.science/mcp
Codexcodex mcp add zetesis --url https://api.zetesis.science/mcp

For Gemini's settings.json, use httpUrl rather than url; the latter is SSE and will not connect. Full setup notes: https://api.zetesis.science/docs

Tools

zetesis_scope routes the claim and returns the diligence apparatus for its class: the questions a reviewer would ask, structured by substrate, methods, cohort and risk of bias, a failure-pattern taxonomy carrying the companies each pattern was derived from, and the edge cases where those patterns were wrong. A checklist that only ever fires positive teaches over-rejection, so the counterexamples ship alongside it.

zetesis_evidence runs the searches and returns a deduplicated bundle from Europe PMC, ClinicalTrials.gov, openFDA, NIH RePORTER and SEC EDGAR, every source carrying a hard public identifier, followed by the grading rubric so you grade the evidence yourself in context.

Neither of those calls a language model. They return in under a second, cost nothing to run, and send nothing to a model provider. That is usually the answer a security reviewer is looking for.

evaluate_claim produces Zetesis's own graded reading server-side. Slower, and only needed when the assessment itself is the deliverable rather than the evidence.

verify_attestation re-checks a signed Zetesis record to confirm its claim, evidence and conclusion have not been altered since signing. Needs no account.

Claim classes: genomics and Mendelian randomisation, single-cell, bulk omics, CRISPR screens, clinical trials, real-world evidence, AI clinical decision support, diagnostics, preclinical models, cell and gene therapy, structural biology.

Why the year fence matters

Ask a general model about a 2020 claim today and it answers with years of hindsight; the publication that mattered at the time is buried under everything published since.

Measured on a control claim: unfenced retrieval missed the pivotal publication entirely and scored 35% evidence coverage. Fenced to the claim's own year, the same query set retrieved it and coverage rose to 79%. So the fence is not only about honesty in retrospect. It is a retrieval precision feature.

Set as_of to the year a claim was made for anything that is not brand new.

Try it

What did the published evidence actually support about aducanumab and cognitivedecline at the end of 2019, using only sources available by then?

Then ask the same question without the year and compare. The difference is the point.

Privacy

The evidence tools send nothing to a model provider. evaluate_claim processes claim text through a model sub-processor, named along with retention terms and hosting region in the privacy policy. Claim text is not logged; only metadata (the routed class, depth, counts) is kept.

The Python client

This repository also publishes a thin stdio MCP client to PyPI, which predates the hosted server and exposes an older tool set (evaluate_claim, check_evaluation, verify_attestation, account_status). It holds no keys and runs no model; every call is proxied to the hosted engine, and it needs a token.

Prefer the hosted endpoint above. It needs no token and carries the current tools. The client remains for existing stdio setups:

bash
claude mcp add zetesis --env ZETESIS_TOKEN=zk_... -- uvx --from zetesis zetesis-client

Run from a terminal, zetesis opens the chat above. Launched by an MCP host over stdio, it runs this client, so zetesis and zetesis-client both work in MCP configs.

Tokens: https://api.zetesis.science/request-access

  • ZETESIS_TOKEN sets the token (verification works without one)
  • ZETESIS_API overrides the API base, default https://api.zetesis.science

Security

Report vulnerabilities privately to [email protected]. See SECURITY.md.

MIT licensed. The hosted engine is a separate service.


mcp-name: io.github.reutavidan/zetesis

Source: README.md at commit 5c0d598

Tools

4

evaluate_claim

Evaluate a scientific or AI claim

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.

Parametersas_ofclaimrequiredcontextdocuments

zetesis_scope

Scope a claim for evaluation

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.

Parametersas_ofclaimrequiredcontextclaim_class

zetesis_evidence

Retrieve dated public evidence for a claim

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.

Parametersas_ofqueriesrequiredinclude_capital

verify_attestation

Verify a Zetesis attestation

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.

Parametersattestation_jsonrequired

Version history

2
  1. v0.2.2LatestOct 17, 2026
  2. v0.2.1Sep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts