Carbon-X vs MiniCPM-V 4.7 1B

Carbon-X 35

Chat template 20, a Jinja file in the repository. Tool-calling format 10, only the inherited template shows the format and no parser is named. Trained tool calling 0, nothing says it was trained to call tools. Structured output 0, not documented. Reasoning control 0, thinking can be switched off but was never trained, and the card asks you to keep it off. Context 5, 40,960 tokens from the base, though Hugging Face trained at 8,192 and under 16K. Most of what the card documents for agents is Carbon-X as a tool another model calls, which this checklist doesn't read.

MiniCPM-V 4.7 1B 70

Chat template 20, chat_template.jinja in the repository, 7,249 characters. Tool-calling format 10, the card shows tools declared in the OpenAI tools array in a request to Transformers' server, but not how a call comes back, and names no parser for vLLM or SGLang. Trained tool calling 20, the template loops over tool_calls, so it renders several calls in one assistant turn, and the card gives a tool-calling request as a supported use. Structured output 0, Neither JSON nor JSON Schema output is documented or claimed for the model on the card. Reasoning control 10, the card passes enable_thinking per request in its examples, the template has been off by default since 19 October 2026, and the GGUF repository keeps thinking builds in their own folder. Context 10, 262,144 tokens, max_position_embeddings in the text config. 20 + 10 + 20 + 0 + 10 + 10 = 70.

Carbon-X 72

Model card 17, everything but a knowledge cut-off. Training data 15, the mid-training sources and shares are listed, the instruction and fine-tuning data aren't named, and there's no cut-off. Last change 20, 28 October 2026, when config.json, generation_config.json, tokenizer_config.json and tokenizer.py were fixed. Responsiveness 10, organisation members replied to 2 of the 4 questions so far. Version policy 5, a first release whose history was squashed without a note. File health 5, the card now sends llama.cpp users to the publisher's GGUF repository, but the tokenizer config's 131,072 still contradicts the card's 40,960. 17 + 15 + 20 + 10 + 5 + 5 = 72.

MiniCPM-V 4.7 1B 48

Model card 8, Intended use (image, multi-image and video understanding on device), architecture (early visual-token compression inside the vision encoder) and parameters (1B) are there. Training data 0, no description of the training data on the card. Last change 20, the last commit, on 30 October 2026, updated the card and removed an unused asset folder, eleven days before this check. Responsiveness 0, the repository has no discussions that aren't pull requests (two pull requests in all), so nobody has asked anything yet and the line reads as none answered, as settled in calibration. Version policy 10, MiniCPM-V 4.5 and 4.6 stay in their own repositories and the GitHub README dates each release. File health 10, Config, template and card agree on the architecture and the thinking switch, and no report waits without a reply, since there are no discussions. 8 + 0 + 20 + 0 + 10 + 10 = 48.

Carbon-X 65

File safety 15, safetensors and GGUF only, but the documented loading path runs the repository's tokenizer.py through trust_remote_code. Provenance 15, the files are in HuggingFaceBio, which Hugging Face's GitHub repository links, with a checksum on every file. Safety evaluation 10, Hugging Face reports its own dual-use check on sequence editing in the launch post, without numbers or a harness. Agent guidance 5, general cautions only. Licence risk 15, plain Apache 2.0. Security programme 5, Hugging Face's security.txt is a reporting route, and public advisories couldn't be checked.

MiniCPM-V 4.7 1B 55

File safety 25, safetensors in the main repository and the AWQ, GPTQ and int4 builds, GGUF in the GGUF build, with no .bin, .pt, .pth or .py files in the main repository. Provenance 15, files in the openbmb organisation that OpenBMB's GitHub README links to (10), with a SHA-256 for both large files in the main repository (5). Safety evaluation 0, no safety results on the card. Agent guidance 0, the card has no limitations or disclaimer section, and no prompt-injection guidance, instruction hierarchy or statement of trained refusals. Licence risk 15, Apache 2.0 has no use policy, field-of-use limit, threshold or change clause, nothing is added on the card, and the LICENSE in OpenBMB's GitHub repository resolved on 10 November 2026. Security programme 0, no SECURITY.md in OpenBMB/MiniCPM-V and no security.txt on openbmb.cn (both 404 on 10 November 2026), and no advisories found. 25 + 15 + 0 + 0 + 15 + 0 = 55.

Carbon-X 90

Memory 30, the publisher's Q4_K_M GGUF is 9.6 GB, or 11.6 GB with a fifth added. Runtimes 20, released llama.cpp (from b11742, which added the DNA tokenizer), vLLM, SGLang and Transformers all run it, with no Ollama or LM Studio entry. Builds 15, Hugging Face publishes GGUFs at four precisions. Terms 15, Apache 2.0 on the model and on its Qwen3-14B base. Download 10, nothing is gated. Hosted 0, no inference provider or Hugging Face API serves it.

MiniCPM-V 4.7 1B 95

Memory 30, OpenBMB's own IQ4_XS GGUF is 0.64 GB, 1.54 GB with the 0.90 GB vision projector, and 1.54 GB × 1.2 = 1.9 GB, which fits 16 GB with room to spare. Runtimes 25, MiniCPMV4_7ForConditionalGeneration in vLLM's registry at v0.33.0, the minicpmv4_7 model type in SGLang's minicpmv.py at v0.5.23, the minicpmv4_7 model in Transformers at v5.22.2, a MiniCPM-V 4.7 guide and conversion code in llama.cpp at b12242, and an openbmb/minicpm-v4.7:1b tag in OpenBMB's namespace on Ollama, read as the 35B-A3B listing's is. Builds 15, OpenBMB publishes AWQ, GPTQ and int4 safetensors builds and a GGUF repository from IQ3_XS to F16, so quantised builds at two precisions or more. Terms 15, Apache 2.0 in the card's metadata and as the LICENSE of OpenBMB's MiniCPM-V repository, an OSI licence. Download 10, gated is false on the main repository and on the GGUF, AWQ, GPTQ and int4 repositories, so the files download with no account or terms. Hosted 0, Hugging Face lists no inference provider for the model (an empty provider mapping on 10 November 2026), and no provider's own list was read. 30 + 25 + 15 + 15 + 10 + 0 = 95.