Skip to content

Zetesis Scientific Due Diligence MCP server

io.github.reutavidan/zetesisreutavidanstreamable-httpv0.2.2Scanned

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

4 tools: 4 change things.

Tools: 0 delete, 0 irreversible, 4 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Zetesis Scientific Due Diligence MCP server can do

The Zetesis Scientific Due Diligence MCP server is published by the GitHub account reutavidan. It has 4 tools. It can create or change data (4 tools: evaluate_claim, zetesis_scope, zetesis_evidence and verify_attestation), but cannot delete data. None of its tools only reads.

4 tools bring in text other people can write (evaluate_claim, zetesis_scope, zetesis_evidence and 1 more).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 0.2.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 4Claude Code: ask
  • evaluate_claimRun Zetesis's graded reading of a scientific, biomedical, clinical, or AI/ML claim.Reads text others write1 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    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.Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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.Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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.Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:10 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.zetesis.science/mcp: tools/list returned 4 tools to an anonymous client, including evaluate_claim (write), zetesis_scope (write), zetesis_evidence (write), verify_attestation (write)

    What this check looks for

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

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

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
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 or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as zetesis. Review it before you use it.

Capability tags behind 4 rules
  • mcp__zetesis__evaluate_claim untrusted-input
  • mcp__zetesis__zetesis_scope untrusted-input
  • mcp__zetesis__zetesis_evidence untrusted-input
  • mcp__zetesis__verify_attestation untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.reutavidan/zetesis/verify?hash=04a00573b068f06767aa9f1564457bd22c253703cf12586d5e8d2405956b6a29" | jq -e '.changed == false'

Pinned hash 04a00573b068, from Nov 20, 2026, 10:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.reutavidan/zetesis/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.reutavidan/zetesis
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.reutavidan/zetesis.svg)](https://radar.anlyon.com/servers/io.github.reutavidan/zetesis)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:46 UTC.

Zetesis Scientific Due Diligence MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Zetesis Scientific Due Diligence MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Zetesis Scientific Due Diligence MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Zetesis Scientific Due Diligence MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Zetesis Scientific Due Diligence MCP server have?

4 tools: 4 write. evaluate_claim, zetesis_scope, zetesis_evidence and verify_attestation.

Does the Zetesis Scientific Due Diligence MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Zetesis Scientific Due Diligence MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Zetesis Scientific Due Diligence MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.