mcpbeat Sign in

Biorender MCP Server

by biorender Your server? Claim it
answering

Biorender is answering right now. Last checked 2 min ago.

Uptime history 47 days of history · worst day 97%
47 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
327 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Biorender every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.services.biorender.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.services.biorender.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.services.biorender.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.services.biorender.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.services.biorender.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.services.biorender.com/mcp streamable-http sign-in 631 ms 2 min ago

Alternatives to Biorender

same job, measured the same way
Synthesize Bio
by synthesize-bio
answering
Biorxiv
by pipeworx-io

bioRxiv + medRxiv preprint server API

43 tools answering
Bigdata
by bigdata
answering

Biorender — questions

Answers built from our own checks of this server.

Why is there no tool list for Biorender?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Biorender working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 327 ms. The bar chart above shows every period we have measured.
How do I connect Biorender?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Biorender?
No API key is involved. Biorender answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Biorender?
It answers our handshake in 327 ms on average, which is faster than 47% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.