Bio-Data Parser

io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 25, 2026

Bioinformatics and genomic sequence parser for clinical research.

The publisher's own server: Parser Club

VerifiedSSEWeb executableData & Analytics

Overview

AI-generated overview

A remote bioinformatics and genomic sequence parser MCP server for clinical research, with a premium settlement option that requires a payment signature header.

What you can do
Parses bioinformatics and genomic sequence data for clinical research use cases, based on the registry description. The manifest lists no individual tools, so the exact parsing operations are not documented. A premium settlement path is indicated, gated by a payment-signature header.
When to use it
Consider it when an assistant needs to parse genomic or bioinformatics sequence data in a clinical research context and a remote endpoint is acceptable. Because no tools or README are published, verify its actual capabilities before relying on it.
Requirements
A remote SSE endpoint; no local runtime or package is needed. No authentication is declared, but premium settlement requires the payment-signature header, a Base64-encoded EIP-3009 TransferWithAuthorization signature. Network access to the hosted endpoint is required.
Before you install
The payment-signature header carries a cryptographic payment authorization signature; treat it as a secret and be aware that premium use involves payment settlement. The server is remote, so any sequence data submitted is sent to a third-party host. No tools or documentation are published, so behavior cannot be reviewed in advance.

Installation

In SourceWeft

  1. Open Bio-Data Parser in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Evozim%2Fbio-data-parser/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "bio-data-parser": {
      "type": "sse",
      "url": "https://bio-data-parser-mcp.vercel.app/api/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Parser integrations