Zetesis Scientific Due Diligence MCP MCP server

An official MCP server by Zetesis that performs due diligence on high-dimensional scientific claims. It grades claims dimension-by-dimension against public records from sources like Europe PMC and ClinicalTrials.gov, identifying what evidence supports or refutes a claim, checking for retractions, and analyzing failure patterns in comparable scientific assertions.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Zetesis

MCP endpoint (Streamable HTTP)

https://api.zetesis.science/mcp

Vendor documentation

What you can do with it

Judge a scientific claim based on evidence available at a specific historical time
Verify if a health claim is well-supported by published literature before repeating it
Conduct due diligence on gene therapy assets or pitch decks
Check if a clinical trial paper has been retracted or corrected before citing

Tools advertised by the last live check:

evaluate_claim
zetesis_scope
zetesis_evidence
verify_attestation

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http zetesis-scientific-due-diligence-mcp https://api.zetesis.science/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add zetesis-scientific-due-diligence-mcp --url https://api.zetesis.science/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable zetesis-scientific-due-diligence-mcp in your MCP settings.

Cursor configuration

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

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

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

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start zetesis-scientific-due-diligence-mcp and inspect its tools.

VS Code configuration

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

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http zetesis-scientific-due-diligence-mcp https://api.zetesis.science/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

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

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "zetesis-scientific-due-diligence-mcp": {
      "serverUrl": "https://api.zetesis.science/mcp"
    }
  }
}

See all 1,583

Do you run Zetesis Scientific Due Diligence MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing