Workbench MCP Server

https://seqbench.com/api/mcp Remote v1.1.0

Published by seqbench.com — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Hosted DNA/RNA/protein tools: primers, oligos, PCR, cloning, CRISPR, alignment, batch & pipelines.

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Live
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 94/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: sequence_fetch → sanger_plate_verify ⇒ sequence_format_convert. Untrusted input is ingested, private data is read, and it can be sent to an external sink — and at least one leg is a direct schema wire (⇒), where a producer's output drops straight into a free-text parameter of the next tool, so the chain needs little agent cooperation. Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow sequence_fetch → sanger_plate_verify → sequence_format_convert

Tools 114

Each tool and what it can reach — enumerated from the running server.

  • sanger_plate_verifyreads sensitive data
  • sequence_fetchingests untrusted input
  • sequence_format_convertnetwork egress
  • sequence_searchingests untrusted input
  • session_getingests untrusted input
  • vector_library_searchingests untrusted input
  • web_searchingests untrusted input
  • alphafold_lookupno sensitive capability
  • aso_designno sensitive capability
  • assembly_outcomesno sensitive capability
Show 104 more tools ↓
  • band_tracebackno sensitive capability
  • base_edit_quantno sensitive capability
  • base_editing_designno sensitive capability
  • batchno sensitive capability
  • characterize_sequenceno sensitive capability
  • cloning_diagnoseno sensitive capability
  • cloning_next_observationno sensitive capability
  • cloning_simulateno sensitive capability
  • codon_adaptation_indexno sensitive capability
  • codon_optimizeno sensitive capability
  • construct_autofixno sensitive capability
  • construct_qcno sensitive capability
  • crispr_grna_designno sensitive capability
  • crispr_hdr_donorno sensitive capability
  • crispr_offtarget_checkno sensitive capability
  • crispr_ontargetno sensitive capability
  • cross_dimerno sensitive capability
  • diagnostic_digestno sensitive capability
  • dna_molarityno sensitive capability
  • double_digestno sensitive capability
  • editing_plate_quantifyno sensitive capability
  • export_echo_picklistno sensitive capability
  • export_opentrons_protocolno sensitive capability
  • export_plate_layoutno sensitive capability
  • expression_heatmap_clusterno sensitive capability
  • fastq_qc_reportno sensitive capability
  • fastq_trimno sensitive capability
  • find_orfsno sensitive capability
  • format_sequenceno sensitive capability
  • functional_enrichmentno sensitive capability
  • gc_contentno sensitive capability
  • gene_dossierno sensitive capability
  • gene_expressionno sensitive capability
  • gene_modelno sensitive capability
  • golden_gate_designno sensitive capability
  • golden_gate_fidelityno sensitive capability
  • golden_gate_from_partsno sensitive capability
  • hgvs_convertno sensitive capability
  • id_map_pollno sensitive capability
  • id_map_submitno sensitive capability
  • in_silico_pcrno sensitive capability
  • kasp_primer_designno sensitive capability
  • ligation_setupno sensitive capability
  • melting_temperatureno sensitive capability
  • motif_finderno sensitive capability
  • multiple_sequence_alignmentno sensitive capability
  • multiplex_panel_designno sensitive capability
  • oligo_analysisno sensitive capability
  • oligo_cofoldno sensitive capability
  • oligo_pool_screenno sensitive capability
  • ortholog_mapno sensitive capability
  • outcome_deconvolveno sensitive capability
  • pairwise_alignmentno sensitive capability
  • parse_genbankno sensitive capability
  • parse_sanger_traceno sensitive capability
  • parse_snapgeneno sensitive capability
  • parts_library_searchno sensitive capability
  • plasmid_annotateno sensitive capability
  • plasmid_deep_annotateno sensitive capability
  • plasmid_full_reportno sensitive capability
  • plasmid_identifyno sensitive capability
  • prime_editing_designno sensitive capability
  • prime_editing_efficiencyno sensitive capability
  • prime_editing_twin_designno sensitive capability
  • primer_designno sensitive capability
  • primer_specificityno sensitive capability
  • protease_digestionno sensitive capability
  • protein_annotate_pollno sensitive capability
  • protein_annotate_submitno sensitive capability
  • protein_hydrophobicityno sensitive capability
  • protein_propertiesno sensitive capability
  • random_sequenceno sensitive capability
  • rbs_designno sensitive capability
  • rbs_predictno sensitive capability
  • read_placement_planno sensitive capability
  • repeat_instabilityno sensitive capability
  • restriction_sitesno sensitive capability
  • reverse_complementno sensitive capability
  • reverse_translateno sensitive capability
  • rna_foldno sensitive capability
  • sanger_assembleno sensitive capability
  • sanger_indel_spectrumno sensitive capability
  • sanger_knockin_quantno sensitive capability
  • sanger_vs_referenceno sensitive capability
  • save_permalinkno sensitive capability
  • seqfile_statsno sensitive capability
  • sequence_reportno sensitive capability
  • sequencing_readback_verifyno sensitive capability
  • session_createno sensitive capability
  • session_runno sensitive capability
  • session_setno sensitive capability
  • sirna_designno sensitive capability
  • site_directed_mutagenesisno sensitive capability
  • trace_secondary_peaksno sensitive capability
  • translateno sensitive capability
  • variant_annotateno sensitive capability
  • variant_comparatorno sensitive capability
  • variant_to_constructno sensitive capability
  • vector_library_getno sensitive capability
  • verify_assemblyno sensitive capability
  • verify_constructno sensitive capability
  • virtual_gelno sensitive capability
  • volcano_plot_datano sensitive capability
  • workflowno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.1.0 latest A 94/100 1 1.13.0 2026-09-14

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/seqbench-com-api/badge.svg)](https://mcptrustchecker.com/registry/seqbench-com-api)
HTML
<a href="https://mcptrustchecker.com/registry/seqbench-com-api"><img src="https://mcptrustchecker.com/registry/seqbench-com-api/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/seqbench-com-api/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan https://seqbench.com/api/mcp --online

Use the free API → How scoring works

More in Data Science & ML