mcpbeat Sign in

Zetesis Scientific Due Diligence MCP Server

by reutavidan Your server? Claim it
answering

Zetesis Scientific Due Diligence is answering right now. Last checked 14 min ago. 31 installs a week from pypi. It exposes 4 tools. Last commit 1 Sep 2026.

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

Installs per day peak 18 · avg 8 · -54% w/w
a month agotoday
Uptime history 17 days of history
17 days agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
120 ms
Response time
average over 24h
31
Installs / week
npm and PyPI

What changed 14

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 2 September 2026. No other catalogue keeps this.

14 Sep 3 tool descriptions were rewritten4 times that day evaluate_claim, zetesis_evidence, zetesis_scope
6 Sep a tool changed version
5 Sep 4 tools changed the parameters they ask for evaluate_claim, verify_attestation, zetesis_evidence and 1 more
2 Sep 4 tool descriptions were rewritten5 times that day evaluate_claim, verify_attestation, zetesis_evidence and 1 more
and 2 more, back to 2 September 2026

Nothing serious here today

Today is the operative word: we check Zetesis Scientific Due Diligence every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add zetesis --transport http https://api.zetesis.science/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "zetesis": {
      "url": "https://api.zetesis.science/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.zetesis]
url = "https://api.zetesis.science/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "zetesis": {
      "url": "https://api.zetesis.science/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "zetesis": {
      "url": "https://api.zetesis.science/mcp"
    }
  }
}

This one needs environment variables set before it will start: ZETESIS_TOKEN (Zetesis access token. Only needed for a full attested dossier; the free screen needs none. Request access at https://api.zetesis.science/request-access.). The author declared them in the registry entry; get the values from the project itself.

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

zetesis
zetesis_evidence
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.
zetesis_scope
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.
evaluate
evaluate_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.
verify
verify_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.

Endpoints

URLTransportStateLatencyChecked
https://api.zetesis.science/mcp streamable-http answering 113 ms 14 min ago

Alternatives to Zetesis Scientific Due Diligence

same job, measured the same way
Due Diligence
by tvarka

Lithuanian company due diligence and KYC identification, attested by an attorney-at-law.

9 tools answering
Sieve MCP
by lmwharton

AI startup due diligence — screen companies across 7 dimensions, get a Sieve Score.

77 installs/wk local only
Amass
by amass

Linked life-science search: 40M+ papers, 1.2M+ trials, drugs, genes, FDA/EMA approvals, patents.

answering
Tooluniverse
by mims-harvard

2,500+ scientific tools for AI scientists: life science, research, literature, and more.

6 973 installs/wk local only
OmniScholar
by luffysolution-svg

Literature, Zotero, PDF, citation, materials, and scientific image tools for research agents.

local only
D
Ddplus
by cz-agents

Czech KYC due-diligence — paid tier extension (nominee, phoenix, risk timeline, watchlist).

answering
FBI Most Wanted
by mcp-dir

Checks whether a name is on the FBI Most Wanted list, for compliance and AML due diligence. Platform

7 tools answering
ConvergeQA Compare (Due Diligence)
by convergeqa

Compare one prompt across a multi-model panel side by side, with public verification receipts.

local only

Zetesis Scientific Due Diligence — questions

Answers built from our own checks of this server.

What can Zetesis Scientific Due Diligence do?
It exposes 4 tools, read directly from the server on our last check. Among them: evaluate_claim, verify_attestation, zetesis_evidence, zetesis_scope. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Zetesis Scientific Due Diligence working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 120 ms. The bar chart above shows every period we have measured.
How do I connect Zetesis Scientific Due Diligence?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Zetesis Scientific Due Diligence need an API key?
No. Zetesis Scientific Due Diligence completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Zetesis Scientific Due Diligence?
It answers our handshake in 120 ms on average, which is faster than 81% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Zetesis Scientific Due Diligence?
The pypi package zetesis was installed 31 times in the last week. Week over week that is -54%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Zetesis Scientific Due Diligence open source?
Yes — it is published under the MIT licence, written in Python and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.