mcp-registry/com.seqbench/workbench · v1.1.0
As of 2026-10-25 04:09 UTC, the Seqbench Workbench MCP server is unknown with a Glimind reliability score of 51/100 (grade D). Over the last 30 days it answered 0% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 7 minutes.
Hosted DNA/RNA/protein tools: primers, oligos, PCR, cloning, CRISPR, alignment, batch & pipelines.
Point your MCP client at this streamable-http endpoint: https://seqbench.com/api/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →
5 tool definition(s) exceed ~1,200 tokens each (largest: cloning_next_observation, ~1,893).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~5,887 tokens every session. How to fix →
114 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
28 parameter(s) across 16 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 →
7 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Loading this server's tool list costs an agent ~47,432 tokens before any work — more than 99% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. 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 →
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/com.seqbench/workbench"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.seqbench/workbench"}) over MCP.
cloning_next_observation ~1,893 tokenscloning_diagnose ~1,891 tokensediting_plate_quantify ~1,802 tokensverify_assembly ~1,783 tokenscloning_simulate ~1,518 tokensStatic 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. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.seqbench%2Fworkbench?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.seqbench%2Fworkbench?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.seqbench%2Fworkbench.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.seqbench%2Fworkbench.svg :target: https://glimind.com/server/mcp-registry%2Fcom.seqbench%2Fworkbench?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:09c31790840c7df8…, first seen 2026-10-17, included at leaf 13774 of 78,153. Version history · verify what your client received.
Compare: most reliable data servers · most reliable other servers · most reliable knowledge servers · most reliable ml servers · most reliable code servers
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.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-25 04:09 UTC, the Seqbench Workbench MCP server is unknown with a Glimind reliability score of 51/100 (grade D). Over the last 30 days it answered 0% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 7 minutes.
Seqbench Workbench MCP server advertises 114 tools, including alphafold_lookup, aso_design, assembly_outcomes, band_traceback, base_edit_quant.
Point your MCP client at this streamable-http endpoint: https://seqbench.com/api/mcp
Glimind scanned all 114 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.
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.