Execute bio-data-parser-mcp

io.github.EvozimPublished by GitHub account Evozimv2.0.0Updated Oct 24, 2026

Premium agentic endpoint for bio-data-parser-mcp.

The publisher's own server: Parser Club

VerifiedSSEWeb executableFinanceData & Analytics

Overview

AI-generated overview

A remote MCP endpoint for a bio-data parsing service that requires a per-call crypto payment signature.

What you can do
The registry describes this as a premium agentic endpoint for bio-data-parser-mcp, reachable over SSE at a hosted address. No tools are listed in the manifest, so the exact parsing capabilities are not documented here. Access is gated by a payment signature rather than a conventional API key.
When to use it
Consider it only if you specifically need a hosted bio-data parsing endpoint and are willing to pay per call in USDC on Base Mainnet. Without a published tool list, it is hard to judge fit in advance.
Requirements
A remote SSE connection to the provider's endpoint; no local package or runtime is declared. A Payment-Signature header carrying a Base64-encoded EIP-3009 TransferWithAuthorization signature for x402 V2 settlement on Base Mainnet, quoted at $0.05 USDC per settlement. No environment variables are declared.
Before you install
Each call settles a crypto payment of $0.05 USDC on Base Mainnet, so the assistant can spend real money. The Payment-Signature header is a signed transfer authorization; treat it as a secret and do not log or share it. No tool list is published, so what data is sent to the provider and what it does with it cannot be verified from this listing.

Installation

In SourceWeft

  1. Open Execute bio-data-parser-mcp 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-mcp/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": {
    "execute-bio-data-parser": {
      "type": "sse",
      "url": "https://api.m2mcent.com/bio-data-parser-mcp/sse"
    }
  }
}

Tools

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

Version history

1
  1. v2.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