Context7
Up-to-date docs for AI agents
제작자가 쓴 설명(영어 원문)
Recommend paper-backed diagnostics for PyTorch and Hugging Face training problems.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요
{
"mcpServers": {
"traintools": {
"command": "uvx",
"args": [
"traintools",
"mcp"
]
}
}
}터미널에서 이 명령어를 실행하세요
claude mcp add traintools -- uvx traintools mcp프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"traintools": {
"command": "uvx",
"args": [
"traintools",
"mcp"
]
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"traintools": {
"type": "stdio",
"command": "uvx",
"args": [
"traintools",
"mcp"
]
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
레지스트리 이름이 GitHub 계정 AparajeetS 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.6.2)은 4개월 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Python (uv)도 있어야 해요.
같은 카테고리에는: Context7, Codebase Memory, Exa
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Up-to-date docs for AI agents
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.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
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.
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요