# Zetesis Scientific Due Diligence (remote · api.zetesis.science)

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

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `api.zetesis.science`: 78/100 (this document), [markdown](https://verifymcp.io/servers/reutavidan-zetesis/api.md), [page](https://verifymcp.io/servers/reutavidan-zetesis/api)
- pypi · `zetesis`: 40/100, [markdown](https://verifymcp.io/servers/reutavidan-zetesis/zetesis.md), [page](https://verifymcp.io/servers/reutavidan-zetesis/zetesis)

## Channel facts

- Endpoint: `https://api.zetesis.science/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2222 tokens (~555/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Zetesis Scientific Due Diligence MCP server?

Zetesis Scientific Due Diligence is a hosted endpoint at https://api.zetesis.science/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "reutavidan-zetesis": {
      "url": "https://api.zetesis.science/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "reutavidan-zetesis": {
      "type": "http",
      "url": "https://api.zetesis.science/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.reutavidan-zetesis]
url = "https://api.zetesis.science/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "reutavidan-zetesis": {
      "type": "remote",
      "url": "https://api.zetesis.science/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add reutavidan-zetesis --url 'https://api.zetesis.science/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  reutavidan-zetesis:
    url: "https://api.zetesis.science/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "reutavidan-zetesis": {
      "Transport": "http",
      "Url": "https://api.zetesis.science/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add reutavidan-zetesis -t streamable-http -u 'https://api.zetesis.science/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 75, 0)

- [security] Tool “zetesis_evidence” rewrote its description, which is the text the model reads
- [security] Tool “evaluate_claim” rewrote its description, which is the text the model reads
- [security] Tool “zetesis_scope” rewrote its description, which is the text the model reads

### 2026-09-14 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 72, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

## MCP tools (4)

### `evaluate_claim` (~409 tokens)

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.

Input parameters:

- `as_of` (integer): Year the claim was made. Set it for any claim that is not brand new: it restricts evidence to what existed then, which keeps later outcomes out of the reading and sharply improves what is retrieved.
- `claim` (string, required): The claim to evaluate, in one or two sentences.
- `context` (string): Optional background: stage, field, or the decision at hand.
- `documents` (string): Optional source text to evaluate against, such as a deck, abstract or paper.

Output parameters:

- `result` (string)

### `zetesis_scope` (~420 tokens)

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.

Input parameters:

- `as_of` (integer): Year the claim was made. Set it for any claim that is not brand new: it restricts evidence to what existed then, which keeps later outcomes out of the reading and sharply improves what is retrieved.
- `claim` (string, required): The claim to evaluate, in one or two sentences.
- `claim_class` (string): Optional override for the routed claim class. The response lists every class; pass one back if the routing picked wrongly.
- `context` (string): Optional background: stage, field, or the decision at hand.

Output parameters:

- `result` (string)

### `zetesis_evidence` (~500 tokens)

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.

Input parameters:

- `as_of` (integer): Year the claim was made. Set it for any claim that is not brand new: it restricts evidence to what existed then, which keeps later outcomes out of the reading and sharply improves what is retrieved.
- `include_capital` (boolean): Also retrieve funding and public filing signal from NIH RePORTER and SEC EDGAR.
- `queries` (array, required): Three to six short keyword phrases. Query 1 should be the bare name of the thing claimed about; query 2 that name plus at most two outcome words.

Output parameters:

- `result` (string)

### `verify_attestation` (~95 tokens)

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.

Input parameters:

- `attestation_json` (string, required): The full Zetesis attestation object, as JSON text.

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/reutavidan-zetesis/api#diagnostics

## Score history

- 2026-09-21: 78
- 2026-09-20: 77
- 2026-09-19: 77
- 2026-09-18: 77
- 2026-09-17: 76
- 2026-09-16: 76
- 2026-09-15: 75
- 2026-09-14: 75
- 2026-09-13: 74
- 2026-09-12: 74
- 2026-09-11: 73
- 2026-09-10: 73
- 2026-09-09: 73
- 2026-09-08: 72
- 2026-09-07: 72
- 2026-09-06: 71
- 2026-09-05: 68
- 2026-09-04: 67
- 2026-09-03: 67
- 2026-09-02: 55
- 2026-09-01: 66

## Common questions

### What is the Zetesis Scientific Due Diligence MCP server?

Zetesis Scientific Due Diligence is an MCP server listed in the public MCP registry as io.github.reutavidan/zetesis. Due diligence on life-science claims: omics, trials, gene therapy. Dimension by dimension. This page covers its hosted endpoint (https://api.zetesis.science/mcp).

### Is the Zetesis Scientific Due Diligence MCP server safe to use?

Zetesis Scientific Due Diligence scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Zetesis Scientific Due Diligence MCP server expose?

Zetesis Scientific Due Diligence exposes 4 tools: evaluate_claim, zetesis_scope, zetesis_evidence, verify_attestation. Their descriptions and schemas cost roughly 1,424 tokens of context every time the server is loaded.

### Does the Zetesis Scientific Due Diligence MCP server require authentication?

No. We connected to Zetesis Scientific Due Diligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zetesis Scientific Due Diligence MCP server still maintained?

Zetesis Scientific Due Diligence is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.zetesis.science/mcp
- Repository: https://github.com/reutavidan/zetesis
- Website: https://zetesis.science/
- Changelog RSS feed: https://verifymcp.io/servers/reutavidan-zetesis/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/reutavidan-zetesis/api.json
- HTML version of this page: https://verifymcp.io/servers/reutavidan-zetesis/api