Back to MCP servers

Zetesis Scientific Due Diligence

https://server.smithery.ai/reutavidan/zetesis/mcp
● healthy

Due diligence on a high-dimensional scientific claim, graded dimension by dimension against the published record. Give it a claim, a paper, an abstract or a pitch deck. It works out what would have to be true for the claim to hold, then reports what the evidence shows on each of those dimensions, what it does not show, and the ways claims like it have failed before. Every source it cites was retrieved from a public register, with a real identifier attached. Nothing is made up. Built for the moment a scientific claim is about to carry a decision: licensing a technology, funding a program, in-licensing an asset, citing a paper, or working out whether a company's stated result means what it sounds like. **No account or token needed for the Zetesis server itself.** Connecting through Smithery uses your Smithery credentials. ## What it covers 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, and structural biology. ## What it looks at Europe PMC, ClinicalTrials.gov, openFDA, NIH RePORTER and SEC EDGAR. Published papers, registered trials, regulatory records, grant funding and public company filings. Every source is checked against retraction and correction notices, and the notice is cited when one exists. A reading built on a withdrawn paper is the exact error this exists to prevent. ## The tools - `zetesis_scope` works out what kind of claim this is and what would have to hold for it to be true, including the ways claims like it have failed before. - `zetesis_evidence` goes and finds the evidence, with an identifier on every source. - `evaluate_claim` produces a graded reading, for when you want the assessment itself rather than the evidence to read yourself. - `verify_attestation` re-checks a signed Zetesis record for tampering. **The first two run no AI model at all.** They return in about a second, cost nothing, and send nothing to any AI provider. Your assistant does the thinking, with real sources in front of it. ## Judging a claim by what was known at the time You can ask about a claim as it stood in an earlier year, and only evidence that existed by then comes back. Hindsight is fenced out. This sharpens the answer rather than just making it fairer. On a test claim, an open search missed the one publication that mattered and reached 35% coverage of the relevant evidence. Fenced to the year the claim was made, the same searches found it and coverage reached 79%. ## Try it Ask what the published evidence actually supported about aducanumab and cognitive decline at the end of 2019, using only sources available by then. Then ask the same question without the year. The difference is the point.

Transport
streamable-http
Auth
smithery_api_key
Cost
—
Protocol revision
2025-11-25
negotiated, not declared

MCP readiness

B · 81/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 10/10 initialize and tools/list both answered.
Live MCP endpoint 23/25 Endpoint answers the MCP initialize handshake (5976 ms); very slow response -2.
Protocol revision 8/10 Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 15/15 30/30 probes succeeded over 30 days (100%).
Tool declaration 10/10 Lists 4 tool(s) with descriptions.
Verified identity 5/10 Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags 0/5 not seen in a source for over 30 days.
Auth declaration 2/5 Declares credential scheme: smithery_api_key.
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Very slow (5976 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness
Higher than 52% of peers
This listing 81 · peer median 81
Latency
Faster than 4% of peers
This listing 3,295 ms · peer median 326 ms

Where it loses the most points, and how to win them back

  • Verified identity −5 — Claim the listing and prove control of its domain.
    Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
  • Freshness + modern flags −5 — Keep the listing current in the registry or source it comes from.
    Now: not seen in a source for over 30 days.
  • Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
    Now: Declares credential scheme: smithery_api_key.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

How to connect

MCP endpoint (streamable-http)
https://server.smithery.ai/reutavidan/zetesis/mcp
JSON-RPC initialize probe
curl -X POST https://server.smithery.ai/reutavidan/zetesis/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://zetesis.science
Listed at (smithery)
https://zetesis.science