MiniCPM-V 4.7 1B vs Nanbeige4.3-33B

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.

Nanbeige4.3-33B 80

Memory earns 20, since Nanbeige's INT4 build is 22.57 GB, about 27 GB with a fifth added, which fits 32 GB. Runtimes earn 20 from released vLLM, SGLang, Transformers and llama.cpp, which all run the Llama architecture, and Ollama and LM Studio have no build. Builds earn 15 for Nanbeige's INT4, INT8 and FP8 builds of 31 October 2026. Terms earn 15 for Apache 2.0 with nothing added, though only the metadata names it. Download earns 10, with no gate. Hosted earns 0, as no provider or Nanbeige API serves it.

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.

Nanbeige4.3-33B 85

The chat template earns 20, Jinja in tokenizer_config.json. The tool-calling format earns 25, with the XML call format in the template and the qwen3_coder parser named for vLLM and SGLang. Trained tool calling earns 20, several calls per turn in the template. Structured output earns 0, as nothing mentions it. Reasoning control earns 10, thinking switched per request with the qwen3 reasoning parser named. Context earns 10 for 512K set in the config with no scaling.

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.

Nanbeige4.3-33B 56

The model card earns 11, with intended use, parameters, context and languages but no limitations, architecture or cut-off. Training data earns 0, as nothing describes it. Last change earns 20 for the quantised builds of 31 October 2026. Responsiveness earns 10, a Nanbeige member answering nine of 30 discussions. Version policy earns 5 for a first release, with a config change made and reverted under bare commit titles. File health earns 10, the files and the card agreeing.

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.

Nanbeige4.3-33B 60

File safety earns 25, safetensors only and no repository code, so the card's trust_remote_code has nothing to run. Provenance earns 15, the lab's own organisation as its arXiv report links it, with a hash for every file. Safety evaluation earns 0 and agent guidance 0, since neither card says anything on either. Licence risk keeps all 15 under Apache 2.0. The security programme earns 5 for BOSS Zhipin's security response centre, which isn't linked to the model.