Is the Execute bio-data-parser-mcp down?

mcp-registry/io.github.evozim/bio-data-parser-mcp · registry v2.0.0 · server reports v2.1.0

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
degraded
Last checked 2026-11-22 19:20 UTC · handshake 99ms

As of 2026-11-22 19:20 UTC, the Execute bio-data-parser-mcp is degraded with a Glimind reliability score of 58/100 (grade D). Over the last 30 days it answered 68.2% of Glimind's liveness checks.

uptime (30d checks)
68.2%
checks observed
975
outages (90d)
0
tools
1

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

Point your MCP client at this streamable-http endpoint: https://api.m2mcent.com/bio-data-parser-mcp/sse

Agent-readiness: D (60/100)

D (60/100): 1 error(s), 3 warning(s) across 1 tool(s); ~89 tokens of tool definitions.
Scores higher than 0% of 27,663 MCP servers Glimind has audited.
Its tool list costs an agent ~89 tokens per session — lighter than 99% of servers.
60 → 60 since 2026-11-11
no tool-poisoning patterns
Descriptions30
Safety hints30
Schemas100
Protocol40
Stability96
Token cost100
Reliability20
Client compatibility70

What to fix (6)

Up 37.9% of the time over the 29 days we have observed.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

2 parameter(s) across 1 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: bio-data-parser-mcp

1 of 1 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: bio-data-parser-mcp

Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

In the last 30 days: 0 tool(s) removed and 1 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.evozim/bio-data-parser-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.evozim/bio-data-parser-mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fio.github.evozim%2Fbio-data-parser-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.evozim%2Fbio-data-parser-mcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.evozim%2Fbio-data-parser-mcp?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.github.evozim%2Fbio-data-parser-mcp.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:87ff520a2aa10fe7…, first seen 2026-11-11, included at leaf 225616 of 384,974. Version history · verify what your client received.

Working alternatives

Tools (1)

Compare: most reliable data servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the Execute bio-data-parser-mcp down right now?

As of 2026-11-22 19:20 UTC, the Execute bio-data-parser-mcp is degraded with a Glimind reliability score of 58/100 (grade D). Over the last 30 days it answered 68.2% of Glimind's liveness checks.

How many tools does Execute bio-data-parser-mcp provide?

Execute bio-data-parser-mcp advertises 1 tool, including bio-data-parser-mcp.

How do I install Execute bio-data-parser-mcp?

Point your MCP client at this streamable-http endpoint: https://api.m2mcent.com/bio-data-parser-mcp/sse

Is the Execute bio-data-parser-mcp safe to connect to an AI agent?

Glimind scanned all 1 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Execute bio-data-parser-mcp?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve