Visualizers

Learn by moving things

Interactive explainers for the ideas behind retrieval, embeddings, and agents. A formula tells you what is true; dragging a vector shows you why. Each one also appears inside the article it belongs to, and runs entirely in your browser, so drag, poke, and break it.

Portrait of Sachin Gupta rendered in binary

How MCP evolved

From: How MCP Grew

An interactive timeline of MCP's four spec revisions. Click each to see what it added, from the initial primitives to authorization, async tasks, and governance.

2024-11-05launch

The initial release. JSON-RPC base, capability negotiation, five primitives (tools, resources, prompts, sampling, roots), and the stdio and original HTTP+SSE transports.

Four revisions in a year and a half. The six primitives barely changed; what grew was remoting, security, async, and governance around them.

Evaluating an LLM is choosing the right grader. Click each family, exact checks, reference metrics, LLM-as-judge, human review, to see how it works, what it costs, and what it can and cannot catch.

Pick a gradercheap & strict → rich & slow
Exact / heuristic
How it works
string equals, a regex, a JSON-schema check
Cost
free, instant, deterministic
Catches
exact values and formats
Misses
anything open-ended or reworded
There is no best grader, only the right one for the answer. Real systems stack several: cheap checks on everything, a judge on the open-ended parts, humans on a sample.

Step through how a production failure becomes a permanent test: offline eval gates the ship, online eval catches a surprise, and that surprise is captured back into the offline set so it never recurs silently.

0 / 5
Offline eval
Ship
Online eval
Capture
Caught forever
Offline is your test suite; online is your monitoring; the flywheel turns every production surprise into a permanent test. That loop is what makes an eval system improve instead of drift.
Visualizers — Sachin Gupta