Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Recommend paper-backed diagnostics for PyTorch and Hugging Face training problems.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"traintools": {
"command": "uvx",
"args": [
"traintools",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add traintools -- uvx traintools mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"traintools": {
"command": "uvx",
"args": [
"traintools",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"traintools": {
"type": "stdio",
"command": "uvx",
"args": [
"traintools",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account AparajeetS, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.6.2) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Paper-backed ML training diagnostics for PyTorch. Small tools that answer practical questions while a run is still alive.
Have a real run or false alarm to share? Use the diagnostic report template.
pip install traintools
Not sure which tool fits the problem?
traintools recommend "my loss became NaN and gradients explode"
traintools integration gradient-health --framework pytorch
Agents can use the JSON CLI, the agent guide, llms.txt, or the optional local MCP server:
pip install "traintools[mcp]"
traintools-mcp
The same local, read-only server is discoverable through the official MCP Registry and can be launched without a persistent install:
uvx --with mcp traintools mcp
For AI coding assistants: start with traintools recommend " " --json, then insert the smallest diagnostic snippet into the user's existing loop. The agent-facing entrypoints are AGENTS.md, llms.txt, JSON schemas, and the optional MCP server.
| Tool | Question it answers |
|---|---|
| Gradient Noise Scale (GNS) | Is my batch size wasting compute? |
| GradientAccumulationGNS | Can I get GNS for free during gradient accumulation? |
| PlasticityProbe | Is my network losing the ability to learn? |
| TrainGuard | Should I stop training yet? |
| BatchInspector | Is this batch broken, imbalanced, or out of scale? |
| GradientHealthMonitor | Are gradients finite, clipped, vanished, exploded, or too large for the weights? |
| ExampleDynamicsTracker | Which examples are forgotten, hard, ambiguous, or likely mislabeled? |
| GradientConfusionMonitor | Are micro-batch gradients fighting each other and slowing SGD? |
| AUMTracker | Which examples look mislabeled by margin dynamics? |
| EL2NTracker | Which examples are important or pruneable early in training? |
| NeuralCollapseMonitor | Has the classifier entered neural-collapse geometry? |
from traintools import BatchInspector, GradientHealthMonitor
from traintools.callbacks.pytorch import TraintoolsTracker
tracker = TraintoolsTracker(model, loss_fn) batch_inspector = BatchInspector(expected_num_classes=10) grad_health = GradientHealthMonitor(max_grad_norm=1.0)
for step, (x, y) in enumerate(dataloader): batch_report = batch_inspector.inspect(x, y, step=step) if not batch_report.ok: print(batch_report)
loss = loss_fn(model(x), y) loss.backward()
grad_report = grad_health.inspect(model, step=step, lr=optimizer.param_groups0) if not grad_report.ok: print(grad_report)
optimizer.step() optimizer.zero_grad()
decision = tracker.step(step=step, inputs=x, targets=y, val_loss=val_loss) if decision and decision.should_stop: break
HuggingFace Trainer:
from transformers import Trainer
from traintools.callbacks.huggingface import TraintoolsCallback
trainer = Trainer(model=model, ..., callbacks=[TraintoolsCallback()])
GNS is the ratio of per-example gradient variance to gradient signal:
GNS = tr(Sigma) / ||G||^2
It estimates the critical batch size B*: the point where larger batches stop buying much more optimization progress.
GNS > B: under-batched, larger batches can helpGNS < B: over-batched, the batch may be larger than neededGNS ~= B: near the efficient frontiertraintools uses the unbiased estimators from McCandlish et al. 2018 (Bessel-corrected variance, bias-corrected signal) and tracks GNS as EMA(tr(Sigma)) / EMA(||G||^2).
[step 500] GNS=5010.7 (EMA) critical_batch=5011 current=64 regime=under-batched
Batch size 64 is ~78x below the critical batch (~5011). Larger batches would give cleaner gradients per step.
If you already use gradient accumulation, the per-micro-batch gradients you compute anyway are exactly the samples GNS needs.
from traintools import GradientAccumulationGNS
gns = GradientAccumulationGNS(model, micro_batch_size=B_micro)
for step in range(num_steps): for xm, ym in micro_batches: (loss_fn(model(xm), ym) / accum_steps).backward() gns.record_microbatch() optimizer.step() result = gns.compute(step=step) optimizer.zero_grad() gns.reset_accumulation()
PlasticityProbe measures activations directly:
Those are combined into a plasticity score in [0, 1].
[step 200] Plasticity Score: 0.706
All layers healthy.
TrainGuard fits a power-law or exponential curve to validation loss, bootstraps uncertainty, and only stops when continuing looks unlikely to matter.
[step 400] STOP
current loss: 0.6536 predicted final: 0.6119 expected improvement: 0.0417 (90% CI: [0.0012, 0.0821]) estimated plateau at step: 3200 reason: No improvement in 300 steps (best=0.6350 at step 93).
BatchInspector catches bad tensors and labels before they quietly poison a run.
from traintools import BatchInspector
inspector = BatchInspector(expected_num_classes=10, max_abs_value=1e4) report = inspector.inspect(inputs=x, targets=y, step=step) if not report.ok: print(report)
It checks for empty tensors, NaNs/infs, extreme scales, constant tensors, labels outside the expected class range, and severe batch imbalance.
GradientHealthMonitor is called after backward() and before optimizer.step().
from traintools import GradientHealthMonitor
monitor = GradientHealthMonitor(max_grad_norm=1.0) loss.backward() report = monitor.inspect(model, step=step, lr=optimizer.param_groups0) if not report.ok: print(report)
It reports global and per-layer gradient norms, non-finite gradients, likely vanishing/exploding gradients, clipping coefficient, and update-to-weight ratio.
ExampleDynamicsTracker implements two underused training-dynamics probes:
Use stable dataset ids, logits, and labels during a normal classification run.
from traintools import ExampleDynamicsTracker
dynamics = ExampleDynamicsTracker()
for step, (ids, x, y) in enumerate(dataloader): logits = model(x) loss = loss_fn(logits, y) dynamics.update(ids, logits, y, step=step) loss.backward() optimizer.step() optimizer.zero_grad()
print(dynamics.summary()) print("likely noisy or brittle:", [ex.example_id for ex in dynamics.most_forgotten(20)]) print("ambiguous:", [ex.example_id for ex in dynamics.cartography_region("ambiguous")])
A forgetting event is a transition from correct classification to incorrect classification for the same example. Repeatedly forgotten examples are often ambiguous, mislabeled, or distribution-edge cases. Unforgettable examples can be useful candidates for pruning or curriculum experiments.
GradientConfusionMonitor estimates whether micro-batch gradients are aligned or fighting each other, following the gradient-confusion idea from Sankararaman et al. 2019.
from traintools import GradientConfusionMonitor
confusion = GradientConfusionMonitor(n_splits=4) report = confusion.estimate(model, loss_fn, x, y, step=step) if not report.ok: print(report)
It reports mean/min/max pairwise gradient cosine, the fraction of negative gradient pairs, and a compact conflict score. High conflict can point to noisy labels, incompatible samples, depth/initialization issues, or a need for a different batching/curriculum strategy.
AUMTracker implements the Area Under the Margin statistic from Pleiss et al. 2020. For each example, it averages:
true_class_logit - max(other_class_logits)
Low-AUM examples are candidates for label audit or ambiguity review.
from traintools import AUMTracker
aum = AUMTracker(low_aum_threshold=0.0) for step, (ids, x, y) in enumerate(dataloader): logits = model(x) aum.update(ids, logits, y, step=step)
print([ex.example_id for ex in aum.lowest_aum(20)])
EL2NTracker implements the cheap example-importance score from Paul et al. 2021:
||softmax(logits) - one_hot(label)||_2
High EL2N examples tend to be important, hard, noisy, or distribution-edge examples. Low EL2N examples can be candidates for data-pruning experiments.
from traintools import EL2NTracker
el2n = EL2NTracker() el2n.update(ids, logits, y, step=step) important = el2n.highest(100) prune_candidates = el2n.lowest(100)
NeuralCollapseMonitor measures late-stage classifier geometry from Papyan, Han, and Donoho 2020:
from traintools import NeuralCollapseMonitor
collapse = NeuralCollapseMonitor() report = collapse.measure(features, labels, classifier_weight=model.fc.weight) print(report)
# Core: PyTorch only
pip install traintools
pip install traintools[full]
pip install traintools[hf]
pip install traintools[mcp]
pip install -e ".[dev]"
traintools is alpha software. The diagnostics are intentionally small and well-tested, but thresholds are heuristics and should be interpreted as training signals, not automatic truth. Bug reports, benchmark traces, and real-world failure cases are especially welcome.
Problem-oriented guides live in the documentation. Diagnostic objects can be written as versioned JSON with write_json_report.
Only the beginning is shown; read the rest in the repo