Biolab MCP Server

io.github.srikarjy由 GitHub 帳號 srikarjy 發布v0.3.0更新於 Oct 24, 2026

Auditable MCP server for PubMed, Europe PMC, ClinicalTrials.gov, and bioRxiv/medRxiv queries

已驗證Streamable HTTP可網頁執行網頁搜尋與抓取知識與記憶資料與分析

概覽

AI 產生的概覽

可稽核的科研證據伺服器:檢索 PubMed、Europe PMC、ClinicalTrials.gov、UniProt、Open Targets 與 bioRxiv/medRxiv,並以雜湊鏈記錄每次檢索。

可以做什麼
  • 檢索科研來源:一次執行可稽核的多來源檢索,或分別檢索 PubMed、Europe PMC、ClinicalTrials.gov 與 bioRxiv/medRxiv,並提供標準 search 與 fetch
  • 檢視檢索紀錄:依檢索 ID 取回完整紀錄,包含原始查詢與來源原始回應
  • 整理證據:建立專案與經審閱的證據集合,並把檢索結果加入集合
  • 監控變化:建立儲存的證據監控、執行單一或全部監控,並列出偵測到的變更事件
  • 追蹤論斷:建立論斷紀錄、連結證據、把論斷追溯到支持或衝突證據,並產出專案報告
  • 執行與驗證工具:列出已註冊工具、執行工具並封存執行紀錄,再驗證雜湊鏈、取得產物或重播執行
適用情境
適合助理進行生物學或醫學研究、且結果日後必須可追溯的情境,例如文獻回顧、標的驗證或法規文件。也適合需要說明某篇論文由哪個查詢、何時取得,以及論斷是否有經審閱證據支持的團隊。
執行需求
可直接使用遠端端點,無需安裝;自行部署需要 Python 3.11 或更新版本(也可用 Go 二進位檔或 Docker 映像)。預設使用本機 SQLite 檔案儲存,也可透過 TURSO_DATABASE_URL 與 TURSO_AUTH_TOKEN 使用遠端 Turso 資料庫。選用的 Authorization 標頭 Bearer 金鑰可提高速率上限,NCBI_API_KEY 可提高 PubMed 速率限制。
安裝前請注意
託管執行個體為共用且開放,匿名呼叫者共用較小的速率額度;金鑰透過 Authorization Bearer 標頭傳送。伺服器會把專案、集合、監控、論斷與執行紀錄持久寫入資料庫,監控也會重新查詢外部來源。查詢內容與 agent 識別會傳送給 PubMed、Europe PMC、ClinicalTrials.gov、UniProt、Open Targets 與 bioRxiv/medRxiv。執行工具會執行已註冊程式碼,例如 mmseqs2_search。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Biolab MCP Server,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.srikarjy%2Fbiolab-mcp-server/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "biolab": {
      "type": "http",
      "url": "https://srikarjy025-biolab-mcp.hf.space/mcp"
    }
  }
}

README

Biolab MCP Server

[Python Version] [Go Version] [MCP] [License] [PyPI] [Docker]

"AI agents querying biological databases leave no audit trail. Six months later, nobody can answer: what exact query returned this result, when, and was that paper peer-reviewed at the time? Biolab solves that."

A local-first scientific evidence workspace with Python and Go clients. It sits between scientists or AI agents and PubMed, Europe PMC, ClinicalTrials.gov, UniProt, Open Targets, and bioRxiv/medRxiv. Every retrieval preserves its source response and returns a retrieval_id; projects, reviewed collections, evidence watches, and claim links build a traceable workflow on top.

New to MCP? It's an open standard that lets an AI assistant — Codex, ChatGPT, Claude, Cursor, and others — call external tools during a conversation. Add Biolab and the assistant can retrieve, preserve, organize, monitor, and cite scientific evidence while keeping every result inspectable later.

Use It Now — No Install

A hosted instance is available at https://srikarjy025-biolab-mcp.hf.space/mcp. Point your client at it and you're done. Hosted capabilities follow the version currently deployed there; run locally for the complete 0.4 workspace in this repository.

Claude Code:

bash
claude mcp add --transport http biolab https://srikarjy025-biolab-mcp.hf.space/mcp

Claude Desktop / Cursor — add this to your MCP config file:

json
{  "mcpServers": {    "biolab": {      "url": "https://srikarjy025-biolab-mcp.hf.space/mcp"    }  }}

(Add "headers": {"Authorization": "Bearer <your key>"} alongside "url" once you have a key — see the rate-limit note below.)

The 0.4 server exposes unified search, source-specific search, standard search/fetch, retrieval inspection, projects, collections, watches, claims, and reports. Every retrieval is written to a hash-chained audit trail you can inspect later (see Audit Trail Schema below).

For cross-source research, search_evidence searches PubMed, Europe PMC, ClinicalTrials.gov, UniProt, and Open Targets through one call while preserving explicit results and errors for each source.

Also listed on the official MCP Registry and Smithery if you'd rather discover/install it from there.

A note on rate limits. The hosted server is shared and stays open — no signup required for casual use — but callers with no API key share one small, low-throughput budget (1 req/s to PubMed) so no single anonymous user can starve everyone else. If you're doing more than a handful of queries, ask for a key (below) and you get your own isolated, higher budget instead.

Getting a key:

Authorization: Bearer <your key>

Add that header in your client's MCP config (Claude Code: claude mcp add --transport http biolab <url> --header "Authorization: Bearer <key>"). Keys are issued with biolab keys create <label> — see Managing API Keys below if you're running your own instance; otherwise ask the maintainer for one.

Want to run your own copy instead (local dev, your own storage, self-hosting)? Keep reading.

The Problem

A drug discovery team uses an AI agent to research gene targets. The agent queries PubMed 200 times over three days and surfaces a paper claiming gene X is upregulated in pancreatic cancer. A scientist makes a decision based on that. Six months later, during FDA submission:

  • What exact query returned that paper?
  • What date was it retrieved?
  • Was it peer-reviewed at retrieval time, or a preprint published later?
  • Did the agent summarize it accurately, or hallucinate details?

Without Biolab, nobody can answer any of those questions. The retrieval is invisible.

What Biolab Does

Biolab is an interception and logging layer, not a retrieval layer. It doesn't interpret evidence, rank it, or summarize it — it records what happened, verbatim, so an agent's claim can always be traced back to an unforgeable original.

Your AI Agent    ↓  MCP tool call (e.g. search_pubmed)Biolab MCP Server    ↓  HTTPSource API (PubMed, Europe PMC, ClinicalTrials.gov, bioRxiv/medRxiv)    ↓  paperBiolab writes a hash-chained retrieval record to the audit database    ↓  paper + retrieval_idBack to your agent

The agent gets the paper it asked for. Biolab gets a permanent, queryable, tamper-evident record of exactly what happened.

Sources Supported

SourceMCP ToolCLI CommandNotes
PubMedsearch_pubmedbiolab searchE-utilities, full XML stored
Europe PMCsearch_europepmcbiolab search-europepmcFree, indexes bioRxiv/medRxiv
ClinicalTrials.govsearch_clinicaltrialsbiolab search-clinicaltrialsAPI v2, condition-based search
UniProtsearch_evidencebiolab evidenceProtein records and sequences
Open Targetssearch_evidencebiolab evidenceTarget, disease, and drug entities via GraphQL
bioRxiv/medRxivsearch_biorxivbiolab search-biorxivDate-range pagination (API limit)

All sources share a single audit database (SQLite locally, or Turso — a hosted, SQLite-compatible database — in production) with one source-agnostic schema.

Build It Yourself

You don't need to know Python or Go to get this running locally — just follow these steps in order. All commands are run in a terminal.

Prerequisites

  • Python 3.11 or newer — check with python3 --version. Get it from python.org if you don't have it.
  • Git — to download (clone) the code. Check with git --version.

That's genuinely it for the Python path — no database server to install, no API keys required (PubMed works anonymously, just at a lower rate limit).

1. Get the code

bash
git clone https://github.com/srikarjy/biolab-mcp-server.gitcd biolab-mcp-server

2. Install it

bash
python3 -m venv .venv          # creates an isolated Python environmentsource .venv/bin/activate      # on Windows: .venv\Scripts\activatepip install -e ".[dev]"        # installs the package + test tools# Add the optional remote Turso driver only if needed: pip install -e ".[turso]"

3. Try it

bash
biolab demo --query "BRCA1 pancreatic cancer"

This searches PubMed for real, stores every result in a local biolab.db file (created automatically, no setup needed), and prints back the retrieval_id for each paper — the same ID an AI agent would get back over MCP.

4. Run the test suite (optional, confirms everything works)

bash
pytest -m "not live and not benchmark" -v

Run pytest -m live -v separately when network access and local socket binding are available. Those tests exercise real PubMed, Europe PMC, ClinicalTrials.gov, and bioRxiv services; the default command stays deterministic and offline.

5. Run it as an MCP server (what an AI agent actually connects to)

bash
python -m biolab.server

This starts an HTTP server on http://localhost:8000/mcp — point Claude Desktop, Claude Code, or Cursor at that URL exactly like in Use It Now, just with localhost:8000 instead of the hosted URL.

6. Build the Docker image (optional)

If you'd rather not install Python locally at all:

bash
docker build -f space/Dockerfile -t biolab-mcp .docker run -p 8000:8000 biolab-mcp

(Storage defaults to an ephemeral file inside the container unless you set TURSO_DATABASE_URL/TURSO_AUTH_TOKEN — see Environment Variables below.)

Prefer a pre-built release?

bash
pipx install biolab-mcp      # or: pip install biolab-mcp
bash
# Or the Go binary, no Python required at all:curl -L https://github.com/srikarjy/biolab-mcp-server/releases/latest/download/biolab_darwin_arm64.tar.gz | tar xz./biolab search "BRCA1 pancreatic cancer" --max 3

Usage

CLI (Scientist-Friendly)

bash
# Search several evidence sources in one audited workflowbiolab evidence "KRAS pancreatic cancer" \  --sources pubmed,europepmc,clinicaltrials,uniprot,opentargets --max 5
# Search PubMedbiolab search "BRCA1 pancreatic cancer" --max 5
# Search Europe PMCbiolab search-europepmc "BRCA1 pancreatic cancer" --max 5
# Search ClinicalTrials.govbiolab search-clinicaltrials "pancreatic cancer" --max 5
# List bioRxiv preprints (no free-text search - API limitation)biolab search-biorxiv neuroscience --max 10biolab search-biorxiv all --server medrxiv --max 10
# Retrieve full audit recordbiolab get <retrieval_id>
# List recent retrievalsbiolab list --source pubmed --limit 10
# Export for analysisbiolab export evidence.jsonl --source clinicaltrials
# Verify the complete tamper-evident audit chainbiolab verify --db biolab.db
# Run demobiolab demo --query "BRCA1 pancreatic cancer"
# Run the offline portfolio demo (no network or scientific claims)biolab portfolio-demo
# Run the real end-to-end scientist workflow against a local serverpython scripts/scientist_workflow_demo.py --url http://127.0.0.1:8000
# Start the private local dashboard and REST APIbiolab web# Open http://127.0.0.1:8000
# Create a project, organize evidence, and trace a claimbiolab projects create "KRAS target review" --description "Pancreatic cancer evidence"biolab collections create <project_id> "Reviewed evidence"biolab collections add <collection_id> <retrieval_id> --relevance relevant --note "Reviewed"biolab claims create <project_id> "KRAS is a therapeutic target"biolab claims link <claim_id> <retrieval_id> --stance supports --assessment human_reviewed
# Monitor a source for added, removed, or revised recordsbiolab watches create <project_id> pubmed "KRAS pancreatic cancer"biolab watches run-all
# Export a complete project reportbiolab projects report <project_id> --output report.md

The dashboard binds to 127.0.0.1 by default. REST endpoints cover evidence, projects, collections, watches, claims, and reports. Discover them at /openapi.json; use /health, /metrics, and /v1/verify for operations. Run biolab web --require-auth with keys created by biolab keys create, or use BIOLAB_REQUIRE_AUTH=true on the unified MCP server, before exposing it remotely.

MCP Tools (Agent-Friendly)

json
// Search any source{"name": "search_evidence", "arguments": {"query": "KRAS pancreatic cancer", "agent_id": "research:target-validation", "sources": ["pubmed", "europepmc", "clinicaltrials", "uniprot", "opentargets"], "max_results": 5}}{"name": "search_pubmed", "arguments": {"query": "BRCA1 pancreatic cancer", "agent_id": "aletheia:advocate", "max_results": 5}}{"name": "search_europepmc", "arguments": {"query": "BRCA1 pancreatic cancer", "agent_id": "aletheia:advocate", "max_results": 5}}{"name": "search_clinicaltrials", "arguments": {"query": "pancreatic cancer", "agent_id": "aletheia:advocate", "max_results": 5}}{"name": "search_biorxiv", "arguments": {"category": "neuroscience", "agent_id": "aletheia:advocate", "max_results": 5, "server": "biorxiv"}}
// Retrieve full audit record (works for ALL sources){"name": "get_retrieval", "arguments": {"retrieval_id": "uuid-from-search"}}

BioClaw

A ready-to-copy BioClaw skill is included at integrations/bioclaw/biolab-evidence. It connects BioClaw's containerized research assistant to the local REST API and supports cross-source search, retrieval inspection, and chain verification without extra Python packages.

Codex and ChatGPT

  • Start the complete local server with python -m biolab.server.
  • Copy integrations/codex/config.toml.example into your Codex configuration and keep tool approval on prompt while developing.
  • The portable Agent Plugin bundle is in plugins/biolab/ (plugin.json, mcp.json, and its evidence-workspace skill). Change the remote URL in mcp.json to your HTTPS deployment before publishing or submitting it.
  • The MCP server includes standard search and fetch knowledge tools plus the richer Biolab tools. Tool annotations disclose read-only, write, external-data, and idempotency behavior to clients.

ChatGPT/Codex can therefore search and preserve evidence, create project state, run watches, and trace claims. The assistant proposes relationships; a scientist must use human_reviewed when a relationship has actually been reviewed.

REST and API gateways

One python -m biolab.server process serves MCP at /mcp, the dashboard at /, and REST under /v1. The important routes are:

RoutePurpose
POST /v1/evidence/searchAudited multi-source search
GET /v1/retrievals/{id}Full preserved retrieval
GET, POST /v1/projectsList or create projects
POST /v1/collectionsCreate a reviewed collection
GET, POST /v1/watchesList or create monitoring queries
POST /v1/watches/run-allScheduled drift detection
POST /v1/claimsCreate a claim without asserting truth
GET /v1/claims/{id}Trace claim/evidence relationships
GET /v1/projects/{id}/reportJSON or ?format=markdown report
GET /openapi.jsonGateway/API discovery document

The zero-cost Caddy/Docker example in deploy/gateway/ adds a reverse-proxy boundary and persistent volume. It binds only to localhost by default. Add a real domain, HTTPS, backups, and organization-specific authorization before public use.

Python API

python
from biolab.pubmed_client import search_and_fetchfrom biolab.retrieval_log import write_retrieval, get_retrievalfrom biolab.db import connect
conn = connect("biolab.db")papers = search_and_fetch("BRCA1 pancreatic cancer", 3)for p in papers:    record = write_retrieval(conn, query="...", pmid=p.pmid, ...)    print(record.retrieval_id)

Managing API Keys

The server stays open to unauthenticated callers by design — but they all share one small, low-throughput rate-limit budget (see Use It Now). Issuing someone a key gives them their own isolated, higher budget instead. This doesn't gate access — it's purely a fairness mechanism so one caller can't starve everyone else's share of PubMed's real rate limit.

bash
# Issue a key — the raw key is shown once, save it immediatelybiolab keys create alice
# List issued keys (never shows the raw key — only a hash is stored)biolab keys list
# Revoke all of a label's active keysbiolab keys revoke alice

The caller sends the key back as Authorization: Bearer <key>. By default a missing header uses the anonymous tier while an invalid/revoked key returns 401. Set BIOLAB_REQUIRE_AUTH=true to reject requests without a key as well.

Environment Variables

All optional — the server runs with sensible defaults if you set none of these.

VariablePurposeDefault
BIOLAB_DB_PATHLocal SQLite file path (ignored if TURSO_DATABASE_URL is set)biolab.db
TURSO_DATABASE_URLOptional remote Turso URL; requires pip install "biolab-mcp[turso]"unset (uses local file)
TURSO_AUTH_TOKENAuth token for the Turso database aboveunset
BIOLAB_HOSTHost the MCP server binds to; non-loopback requires BIOLAB_REQUIRE_AUTH=true or BIOLAB_ALLOW_ANONYMOUS=true127.0.0.1
BIOLAB_PORTPort the MCP server listens on8000
BIOLAB_REQUIRE_AUTHRequire a valid Bearer API key on MCP/REST requestsfalse
NCBI_API_KEYRaises the PubMed rate limit from 3 req/s to 10 req/sunset (works fine without one)

Audit Trail Schema (v2)

sql
CREATE TABLE retrievals (    retrieval_id     TEXT PRIMARY KEY,  -- UUID    source           TEXT NOT NULL,     -- pubmed, europepmc, trials, UniProt, Open Targets, etc.    external_id      TEXT NOT NULL,     -- PMID, NCT ID, DOI, etc.    query_text       TEXT NOT NULL,     -- exact query sent to source    retrieved_at     TEXT NOT NULL,     -- ISO 8601 UTC    agent_id         TEXT NOT NULL,     -- e.g. "aletheia:advocate"    source_metadata  TEXT NOT NULL,     -- JSON: source-specific fields    raw_response     TEXT NOT NULL,     -- verbatim XML/JSON from source    snapshot         TEXT NOT NULL,     -- JSON: structured fields (title, abstract, authors, journal, DOI, pub types, MeSH/conditions)    response_hash    TEXT NOT NULL,     -- SHA-256(prev_hash + raw_response + retrieval_id + retrieved_at)    prev_hash        TEXT NOT NULL      -- response_hash of the previous row — makes this a hash chain);

Key properties:

  • One row per paper retrieval (not per query)
  • Raw response stored verbatim — parsing bugs are recoverable
  • Hash-chained, not just hashed: each row's hash covers the previous row's hash too, so deleting or editing any row — even in the database directly — breaks the chain for every row after it. Call retrieval_log.verify_chain(conn) to check the whole log; it returns exactly which row broke, if any.
  • Background write queue serializes all writes through one path, so the chain stays consistent even under concurrent agent calls

Tamper Evidence and Execution Runtime

  • Retrieval rows are hash-chained over every audited column (hash_version 2); legacy v1 rows still verify.
  • biolab anchor out.json [--chain retrievals|executions] writes an HMAC-signed checkpoint of a chain head (BIOLAB_ANCHOR_KEY). Keep it outside the database host; biolab verify-anchor out.json then detects tail truncation and full rewrites that the chain alone cannot see.
  • biolab run-tool <tool> -i '{...}' runs a registered tool (sequence_stats; mmseqs2_search when mmseqs is on PATH) and seals an immutable ExecutionRecord with content-addressed artifacts. biolab executions {list,show,verify,replay,artifact} inspects, verifies and replays them. If the record cannot be sealed, no result is returned.
  • The Go port (go-biolab/) writes the same v2 chain and has verify, anchor and verify-anchor; hashes are byte-compatible with Python and pinned by shared test vectors. The Go port does not implement the execution runtime.

Architecture

biolab/├── cli.py                   # Search plus scientist workspace commands├── server.py                # Unified MCP + REST + dashboard process├── evidence.py              # Shared multi-source orchestration and audit persistence├── workspace.py             # Projects, collections, watches, claims, reports├── web.py                   # Local dashboard + versioned REST API├── db.py                    # Connection + schema (local SQLite or remote Turso)├── models.py                 # RetrievalRecord dataclass├── retrieval_log.py          # Only writer + background queue + hash chain├── pubmed_client.py           # PubMed E-utilities wrapper + rate limiter├── europepmc_client.py        # Europe PMC adapter├── clinicaltrials_client.py   # ClinicalTrials.gov adapter├── uniprot_client.py          # UniProt adapter├── opentargets_client.py      # Open Targets GraphQL adapter├── biorxiv_client.py          # bioRxiv/medRxiv adapter└── migrations/                # Schema migration scripts
integrations/├── bioclaw/                   # BioClaw evidence skill and REST client└── codex/                     # Local MCP configuration template
plugins/biolab/                # Portable Codex/ChatGPT Agent Plugin bundledeploy/gateway/                # Caddy + Docker Compose deployment template
space/                      # Files pushed to the hosted Hugging Face Space├── Dockerfile                # Python-server-specific image (see repo-root Dockerfile for the Go one)└── README.md                  # Space config (title, hosting metadata)

Design principles:

  • Python + Go implementations (same interface, different runtimes)
  • Shared core with CLI, MCP, REST, and web delivery surfaces
  • Database, not log files — structured queries across time
  • Hard-fail, never degrade — paper without retrieval_id is worse than error
  • Offline acceptance tests plus explicit live connector tests
  • Single-writer queue, not row-level locking — simplest thing that keeps the hash chain consistent under concurrency

Development

bash
# Pythonpip install -e ".[dev]"pytest -m "not live and not benchmark" -v
# Gocd go-biolabgo test ./...go build -o biolab ./cmd/cligo build -o biolab-server ./cmd/server

Deployment

TargetMethod
Hosted (no install)https://srikarjy025-biolab-mcp.hf.space/mcp — capabilities depend on the deployed Space version
Localpipx install biolab-mcp or download binary
CI/CDGitHub Actions → PyPI (Trusted Publishing/OIDC) + GHCR + GitHub Releases
Containersdocker pull ghcr.io/srikarjy/biolab-mcp:latest, or build space/Dockerfile yourself
Linux packages.deb, .rpm, .apk via goreleaser
DiscoveryMCP Registry · Smithery

Student-cost path: local SQLite, the CLI, dashboard, MCP server, BioClaw client, and Caddy gateway require no paid service. Free hosted tiers may also work, but their quotas and persistence policies can change; verify them before relying on a public deployment.

Roadmap

  • Added/removed/content-changed evidence monitoring via response hashes
  • Projects, collections, claims, reports, REST, dashboard, and agent packaging
  • Provenance graph (cross-source linking by DOI)
  • Nextflow/Snakemake plugins
  • Rate limiting + caching (audit-safe)
  • Organization accounts and fine-grained project authorization
  • Retraction/correction feeds with durable alert delivery

License

MIT — see LICENSE

Author

Srikar Jy — [email protected]

來源:README.md,提交 8d3f5fe

工具

30

search_evidence

Search several scientific sources in one explicitly audited workflow. Args: query: scientific evidence query sent to each selected source agent_id: calling agent or workflow identity sources: any of pubmed, europepmc, clinicaltrials, uniprot, opentargets max_results: maximum results to preserve per source (1-50)

輸入參數query必填sourcesagent_id必填max_results

fetch

Fetch one preserved evidence record by retrieval ID.

輸入參數id必填

create_project

Create a persistent scientist research project.

輸入參數name必填description

list_projects

List scientist research projects.

無需輸入參數。

create_evidence_collection

Create a reviewed evidence collection in a project.

輸入參數name必填project_id必填description

list_evidence_collections

List evidence collections, optionally within one project.

輸入參數project_id

add_evidence_to_collection

Add or update a retrieval in a scientist-reviewed evidence collection.

輸入參數noterelevanceretrieval_id必填collection_id必填

get_evidence_collection

Return a collection and its reviewed evidence items.

輸入參數collection_id必填

create_evidence_watch

Create a saved query for explicit evidence-change monitoring.

輸入參數query必填source必填agent_id必填project_id必填max_results

list_evidence_watches

List saved evidence watches, optionally within one project.

輸入參數project_id

run_evidence_watch

Run one evidence watch and record added, removed, or revised evidence.

輸入參數watch_id必填

list_evidence_events

List change events previously detected by an evidence watch.

輸入參數watch_id必填

run_all_evidence_watches

Run all active watches and return explicit per-watch failures.

無需輸入參數。

create_claim

Create a scientific claim record without asserting that it is true.

輸入參數claim必填project_id必填

trace_claim

Trace a claim to supporting, conflicting, contextual, or insufficient evidence.

輸入參數claim_id必填

get_project_report

Return collections, claims, evidence links, watches, and events for a project.

輸入參數project_id必填

search_pubmed

Search PubMed and log every retrieved paper to the audit trail. Args: query: exact search string, sent to PubMed verbatim — no normalization agent_id: which agent is asking, e.g. "aletheia:advocate" max_results: how many papers to retrieve (default 5)

輸入參數query必填agent_id必填max_results

search_europepmc

Search Europe PMC and log every retrieved article to the audit trail. Args: query: exact search string, sent to Europe PMC verbatim — no normalization agent_id: which agent is asking, e.g. "aletheia:advocate" max_results: how many articles to retrieve (default 5)

輸入參數query必填agent_id必填max_results

search_clinicaltrials

Search ClinicalTrials.gov and log every retrieved study to the audit trail. Args: query: condition/disease search string, sent to ClinicalTrials.gov verbatim agent_id: which agent is asking, e.g. "aletheia:advocate" max_results: how many studies to retrieve (default 5)

輸入參數query必填agent_id必填max_results

search_biorxiv

List bioRxiv/medRxiv preprints by category and log each to the audit trail. No free-text search exists on this API — only category listing (last 30 days). Args: category: category, e.g. "neuroscience", "bioinformatics", or "all" agent_id: which agent is asking, e.g. "aletheia:advocate" max_results: how many preprints to retrieve (default 5) server: "biorxiv" or "medrxiv" (default "biorxiv")

輸入參數serveragent_id必填category必填max_results

list_execution_tools

List runnable tools with their pinned versions, containers and devices.

無需輸入參數。

run_tool

Run a registered tool and seal an ExecutionRecord (inputs, versions, output hashes). Args: tool: tool name from list_execution_tools inputs: tool inputs (JSON object); stored verbatim so the run can be replayed agent_id: calling agent or workflow identity retrieval_ids: evidence retrievals this run was derived from, for provenance links

輸入參數tool必填inputs必填agent_id必填retrieval_ids

get_execution

Fetch one execution record, including output artifact hashes.

輸入參數execution_id必填

list_executions

List recent execution records, newest first.

輸入參數toollimit

get_artifact

Fetch an output artifact by its sha256 (text only; capped in size).

輸入參數sha256必填

verify_executions

Verify the execution hash chain and that every output artifact is intact.

無需輸入參數。

replay_execution

Re-run a recorded execution and report whether its outputs reproduced. Writes nothing.

輸入參數execution_id必填

get_retrieval

Retrieve a full retrieval record by its retrieval_id. Args: retrieval_id: the UUID returned by search_pubmed

輸入參數retrieval_id必填

版本歷史

1
  1. v0.3.0最新Sep 16, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分