mcpbeat Sign in

Bio-Data Parser MCP Server

answering

Bio-Data Parser is answering right now. Last checked 4 min ago.

Bioinformatics and genomic sequence parser for clinical research.

Uptime history 91 days of history · worst day 0%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
104 ms
Response time
average over 24h
authentication required
Access
sse

Nothing serious here today

Today is the operative word: we check Bio-Data Parser 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 4 min ago.

run in your terminal
claude mcp add bio-data-parser --transport sse https://bio-data-parser-mcp.vercel.app/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://bio-data-parser-mcp.vercel.app/api/mcp
~/.codex/config.toml
[mcp_servers.bio-data-parser]
url = "https://bio-data-parser-mcp.vercel.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "bio-data-parser": {
      "url": "https://bio-data-parser-mcp.vercel.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "bio-data-parser": {
      "type": "sse",
      "url": "https://bio-data-parser-mcp.vercel.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://bio-data-parser-mcp.vercel.app/api/mcp sse needs auth 74 ms 4 min ago

Alternatives to Bio-Data Parser

same job, measured the same way
PubMed Clinical Research
by taru0208

Search 36M+ PubMed biomedical articles and ClinicalTrials.gov studies.

answering
Nyc311 MCP
by mrfentmen

MCP server for NYC 311 public service request search and aggregate civic data.

708 installs/wk local only
ResearchCal
by researchcal

Conference and call for papers deadlines in economics, business and political science, with sources.

4 tools answering
Clirank
by alexanderclapp

Search, compare, and get docs for 210+ APIs ranked by CLI and agent relevance.

51 installs/wk local only
Sniff MCP
by sniff

Canine genomics for agents: breed allele frequencies, AI pathogenicity + OMIA clinical disease layer

18 tools answering
Evidence
by titratelab

Find lab-report identities and clinical research with dated sources and evidence limitations.

answering
SourceWeave Web Search
by mrnaqa

Fully local MCP server and CLI for web research

61 installs/wk local only
Open Economics
by felipegambettadesouza6-jpg

Discover, resolve, and query official Brazilian economic data with semantic search and provenance.

19 tools answering

Bio-Data Parser — questions

Answers built from our own checks of this server.

Why is there no tool list for Bio-Data Parser?
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 Bio-Data Parser working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 104 ms. The bar chart above shows every period we have measured.
How do I connect Bio-Data Parser?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does Bio-Data Parser need an API key?
Yes. Every time we knock, Bio-Data Parser answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Bio-Data Parser?
It answers our handshake in 104 ms on average, which is faster than 92% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.