pypi zetesisstdioMITupdated 1mo ago
Scientific due diligence on a claim, from inside Claude, Copilot, or any MCP host.
What can you do with zetesis?
Zetesis
Scientific due diligence on a claim, from inside Claude, Copilot, or any MCP host.
Zetesis takes a high-dimensional scientific or technical claim and grades it dimension by dimension against public literature, clinical trials, and filings. It returns an overall reading, cites every source by id, and, for a full evaluation, translates the science into what a commitment to the claim turns on and seals the result in an attestation anyone can re-check.
This package is a thin MCP client. It holds no keys and runs no model. Every call is proxied to the hosted engine at https://api.zetesis.science with your token.
Get a token
Free, no card, at https://api.zetesis.science/signup. The free plan gives you a handful of screening evaluations each month.
Connect it
Claude Code:
claude mcp add zetesis --env ZETESIS_TOKEN=zk_... -- uvx --from zetesis zetesis-client
Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"zetesis": {
"command": "uvx",
"args": ["--from", "zetesis", "zetesis-client"],
"env": { "ZETESIS_TOKEN": "zk_..." }
}
}
}
Tools
- evaluate_claim — grade a claim.
depth="screen"returns the verdict directly (free tier);depth="deep"runs the full signed dossier in the background.mode="research"is science only;mode="diligence"adds the capital reading. - check_evaluation — get the verdict and the rendered dossier link for a deep run.
- verify_attestation — re-check any Zetesis attestation. No account needed.
- account_status — your plan and remaining evaluations or credits.
How it grades
It grades only what the evidence supports, cites sources by hard id (PMID, DOI, NCT, NIH grant, SEC filing), and flags gaps rather than filling them. It never invents citations. Claim text is not logged; only metadata (the routed domain, depth, counts) is kept.
Configuration
ZETESIS_TOKEN— your token (required for evaluations; verify works without one)ZETESIS_API— override the API base (defaulthttps://api.zetesis.science)
MIT licensed. The hosted engine is a separate service.
mcp-name: io.github.reutavidan/zetesis
Install
Add zetesis to your client. Pick the one you use.
claude mcp add zetesis -- uvx zetesiscodex mcp add zetesis -- uvx zetesisamp mcp add zetesis -- uvx zetesis{
"mcpServers": {
"zetesis": {
"command": "uvx",
"args": [
"zetesis"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"zetesis": {
"command": "uvx",
"args": [
"zetesis"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
code --add-mcp '{"name":"zetesis","command":"uvx","args":["zetesis"]}'Or add the block manually to `.vscode/mcp.json` under `servers`.
{
"mcpServers": {
"zetesis": {
"command": "uvx",
"args": [
"zetesis"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"zetesis": {
"command": "uvx",
"args": [
"zetesis"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"zetesis": {
"command": "uvx",
"args": [
"zetesis"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"zetesis": {
"type": "local",
"command": "uvx",
"args": [
"zetesis"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"zetesis": {
"command": {
"path": "uvx",
"args": [
"zetesis"
]
}
}
}
}Add to your Zed `settings.json`.
uvx zetesisRun `goose configure`, choose **Add Extension → Command-line Extension**, and paste this command.
Score
39 / 100
Incomplete
- Documentation22/25
- Maintenance16/25
- Trust13/20
- Capability0/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 44 days ago
- Has a release history
- Repository is not archived
- Licensed MIT
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 12 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Version history
| Versions | Published |
|---|---|
| 0.1.1Latest | Jul 18, 2026 |