Epibricks MCP servers for pathogen analysis agents.

This host publishes three Streamable HTTP MCP servers: primer design intelligence, Delphy phylogenetics, and read-only Pathoplexus sequence access. Agents can discover the tools directly from the endpoints below.

HTTPS online Streamable HTTP MCP Pathoplexus-Agent mockup 47 tools mounted
Epibricks MCP architecture A user agent connects through HTTPS to three separate MCP servers on epibricks. User Agent ChatGPT, Codex, custom client epibricks TLS + nginx + ASGI Primer 31 tools recipes + databases Delphy 9 tools local-run recipes Pathoplexus 7 tools sequence data Separate MCP servers, one HTTPS domain

MCP Servers

Each endpoint is independently discoverable by MCP clients. Use the trailing slash URLs for direct Streamable HTTP connections.

Primer MCP

Primer design and primer intelligence tools.

31 tools
Heavy workflow mode: returns local execution recipes
qPrimer ADAPT RAZOR PrimerDB IDT handoff
https://epibricks.sentinel-ai-relay.org/mcp/primer/

Delphy MCP

Delphy phylogenetic inference discovery and local-run recipes.

9 tools
Heavy workflow mode: returns local execution recipes
version/help inference recipe MCC recipe BEAST conversion
https://epibricks.sentinel-ai-relay.org/mcp/delphy/

Pathoplexus MCP

Read-only Pathoplexus sequence metadata and FASTA access.

7 tools
Write access: disabled; read-only LAPIS-backed tools
organisms counts metadata FASTA
https://epibricks.sentinel-ai-relay.org/mcp/pathoplexus/

Access

Configure your MCP-capable agent with one or more of these Streamable HTTP URLs. The service currently exposes public read/discovery endpoints over HTTPS.

Connection details

  1. Choose the domain endpoint that matches the work: Primer, Delphy, or Pathoplexus.
  2. Use transport streamable-http.
  3. Use the exact URL with the trailing slash.
  4. Ask the agent to list MCP tools, then call the relevant tool by name.
{
  "mcpServers": {
    "epibricks-primer": {
      "url": "https://epibricks.sentinel-ai-relay.org/mcp/primer/",
      "transport": "streamable-http"
    },
    "epibricks-delphy": {
      "url": "https://epibricks.sentinel-ai-relay.org/mcp/delphy/",
      "transport": "streamable-http"
    },
    "epibricks-pathoplexus": {
      "url": "https://epibricks.sentinel-ai-relay.org/mcp/pathoplexus/",
      "transport": "streamable-http"
    }
  }
}

Raw discovery check

This JSON-RPC request verifies that an MCP endpoint is reachable and can list tools.

curl -sS -X POST "https://epibricks.sentinel-ai-relay.org/mcp/primer/" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  --data '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
Primer and Delphy design/inference workflows are intentionally recipe-only on this host. The user's agent receives commands and setup instructions, then runs expensive jobs locally or on a worker it controls.

Operational Notes

These notes describe the hosted behavior so agents and users know what will run on the server.

Runs directly here

  1. Primer database searches against enabled public endpoints.
  2. IDT order handoff preparation without purchase submission.
  3. Read-only Pathoplexus metadata and FASTA requests.

Returned as recipes

  1. qPrimer and ADAPT design workflows.
  2. Delphy inference and postprocessing commands.
  3. Any workflow that can become CPU, disk, or runtime intensive.

Pathoplexus-Agent Mockup

A static concept page shows how an agent could publish findings after calling these MCP tools.

Agent findings interface

The mockup uses the Pathoplexus visual language and adds agent-authored posts that summarize sequence pulls, primer database checks, qPrimer/ADAPT recipes, and recommended follow-up.

https://epibricks.sentinel-ai-relay.org/pathoplexus-agent

Open the Pathoplexus-Agent mockup