Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Show, Don't Code

REMOTE · PUGARHUDA--SHOW-DONT-CODE-WEB.US-EAST.MODAL.RUN

Lab video or protocols.io protocol to a simulator-checked Opentrons Flex/OT-2 protocol

61 Trust /100

Last scanned (1 day ago)

Scores higher than 43% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 872 tokens (~87/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (20% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 61

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://pugarhuda--show-dont-code-web.us-east.modal.run/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.us-east.modal.run CN=YE2,O=Let's Encrypt,C=US 5 Oct 2026 3 Jan 2027 ECDSA 256 ECDSA-SHA384 63abab4602edde2276922ebe98ae22cff88
SANs: *.us-east.modal.run
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of pugarhuda--show-dont-code-web.us-east.modal.run. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
run. present 37315 8 Verified
modal.run. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(self), geolocation=(), microphone=(self)

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pugarhuda--show-dont-code-web.us-east.modal.run/mcp Verified 200
http (plaintext) http://pugarhuda--show-dont-code-web.us-east.modal.run/mcp HTTPS enforced 308 https://pugarhuda--show-dont-code-web.us-east.modal.run/mcp
MCP tools · 10 exposed · ~752 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
crosscheck_volumes ~85

This run's per-reaction volumes next to those of published protocols.io protocols that use the same kit, read by Muse Spark: each match has the published volume, its verbatim quote (checked to be in the protocol's text), both reagents' share of the reaction and whether they agree within 20 %.

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

get_bench_card ~93

The illustrated bench card for training: each filmed step drawn by Muse Image from its own video frame (an edit of the real frame, no text drawn in), Muse Spark's check that the drawing kept every object, and the step's reagent and volume from the protocol. Image links are under /api/runs/<name>/bench-card/<step>.jpg.

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

get_protocol ~41

The generated Opentrons Flex protocol (Python, API 2.24), ready to import into the Opentrons App.

NameTypeReqDescription
namestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_protocol_designer ~70

The protocol as an Opentrons Protocol Designer file: import it at designer.opentrons.com to edit each step (transfers, mixes, the thermocycler program) without code. The Opentrons App can also run it as is.

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

get_receipt ~60

Reproducibility receipt: SHA-256 of the protocol, the video and every model output, and which models ran, anchored in Bitcoin with OpenTimestamps ('timestamp': pending calendars, or the confirming block).

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

get_related_protocols ~60

Public protocols on protocols.io that use this run's reagents (brand and kit names) and protocol type, with DOIs and which reagent words each mentions: how other labs wrote up the same kit.

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

get_run ~61

The steps found in the video (with video seconds), the open questions, and the Opentrons simulator and protocol analysis results, including the deck setup, runtime parameters and the thermocycler's minimum time in seconds.

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

get_tube_labels ~139

The tubes to load on the tube rack before the run: each tube's deck slot and well, how many µL to fill a source tube with (what the robot draws + 10 % + dead volume) for `reactions` copies of the filmed reaction (protocol.py's Reactions parameter, up to max_reactions), and the link its label's QR code opens. Links to the printable labels: an Avery L7160 sheet (SVG) and a Zebra thermal printer file (ZPL, 2 x 1 in).

NameTypeReqDescription
namestringyes–
reactionsinteger––

No output schema declared.

No examples provided.

list_runs ~20

Names of the sample runs (videos already turned into protocols).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

run_on_flex_robot_server ~123

Run the run's protocol.py end to end on Opentrons' own robot-server (the software inside a Flex, v10.1.0) in Flex simulation, with the Reactions parameter set: the robot's analysis, deck configuration, play to the end. Returns the robot's report (status 'succeeded', command count). About a minute the first time, then cached. Runs only the protocol this server generated, never code an agent sends.

NameTypeReqDescription
namestringyes–
reactionsinteger––

No output schema declared.

No examples provided.

Install

How do I install the Show, Don't Code MCP server?

Show, Don't Code is a hosted endpoint at https://pugarhuda--show-dont-code-web.us-east.modal.run/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · pugarhuda--show-dont-code-web.us-east.modal.run

# add to Claude Code
claude mcp add --transport http pugarhuda-show-dont-code 'https://pugarhuda--show-dont-code-web.us-east.modal.run/mcp'
Common questions

What is the Show, Don't Code MCP server?

Show, Don't Code is an MCP server listed in the public MCP registry as io.github.PugarHuda/show-dont-code. Lab video or protocols.io protocol to a simulator-checked Opentrons Flex/OT-2 protocol. This page covers its hosted endpoint (https://pugarhuda--show-dont-code-web.us-east.modal.run/mcp).

Is the Show, Don't Code MCP server safe to use?

Show, Don't Code scores 61 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Show, Don't Code MCP server expose?

Show, Don't Code exposes 10 tools: list_runs, get_run, get_protocol, get_protocol_designer, get_tube_labels, and 5 more. Their descriptions and schemas cost roughly 752 tokens of context every time the server is loaded.

Does the Show, Don't Code MCP server require authentication?

No. We connected to Show, Don't Code without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Show, Don't Code MCP server still maintained?

Show, Don't Code is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.