Skip to main content

model-serving-minefield

Read-only diagnostics for LLM-serving failures: blank streamed replies, thinking that will not turn off, tool calls that fail to render, context limits that lie, benchmarks that measure the wrong thing. It matches what you see against the Model Serving Minefield registry of documented traps and tells you the one check to run next.

Every result is a lead to check, never a diagnosis. No match does not mean your setup is safe.

Install

pipx install msmf

Use

Describe the symptom in plain words:

minefield streaming shows blank replies --stack vllm

Scan your launch scripts, compose files, model folder, chat template, logs and eval results offline:

minefield scan docker-compose.yml start.sh ./models/my-model ./logs/

Probe a live OpenAI-compatible endpoint with bounded, read-only requests:

minefield quick --base-url http://HOST:PORT/v1 --json doctor.json

minefield-mcp serves the same tools to an agent over MCP (stdio). It cannot restart or modify a server.

Metadata

Release files for model-serving-minefield 0.2.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for model-serving-minefield 0.2.2
File Size Uploaded
model_serving_minefield-0.2.2.tar.gz 461.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for model-serving-minefield 0.2.2
File Interpreter ABI Platform
model_serving_minefield-0.2.2-py3-none-any.whl Python 3 none any Details

Total release size: 864.7 kB

Release files / model_serving_minefield-0.2.2.tar.gz

Download URL model_serving_minefield-0.2.2.tar.gz
Size 461.4 kB
Tags Source
SHA-256 checksum
How to use checksums
b420078bbe9451b863083465c0548c07eaa71a5597fc403c06abc139d1c6d117
BLAKE2b-256 checksum
How to use checksums
bea01a06f7a17246ac5e48f279173441f0f83836e00e052f50d3f77d9d0ae8f4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.

Transparency log

Release files / model_serving_minefield-0.2.2-py3-none-any.whl

Download URL model_serving_minefield-0.2.2-py3-none-any.whl
Size 403.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
86351f7895eeb1ce809299b85cf092509192d048fa576dece760c1bc7b8fab90
BLAKE2b-256 checksum
How to use checksums
a12333d0cbd16acb167bc65e9cb67b62ffede2aabb3834338a8f34d2566e8fda
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.2.2 This release

2 release files

0.2.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page