DeepSeek V4.1 Flash vs MiniCPM-V 4.7 35B-A3B

DeepSeek V4.1 Flash 60

Memory scores nothing, because the only build is DeepSeek's own at 510.3 GB, about 612 GB with the fifth added, and nobody's runtime library holds a smaller one at 4-bit or better. Four runtimes run it in a released version (5 each), vLLM 0.33.0, SGLang 0.5.23, which maps the V4.1 architecture name onto its V4 model, llama.cpp from b11870 (25 October 2026), which added the deepseek41 architecture and its converter, and Ollama 0.40.14, which builds llama.cpp b11963. Transformers 5.22.1 and LM Studio don't (0 each). The release itself is one quantised build, FP8 with FP4 experts (10). MIT with nothing added earns the full terms line (15), the repositories aren't gated (10), and Hugging Face maps three live inference providers for the update (5). 0 + 20 + 10 + 15 + 10 + 5 = 60.

MiniCPM-V 4.7 35B-A3B 90

Memory 25, since OpenBMB's IQ4_XS GGUF with its vision projector is 19.6 GB and needs about 23.6 GB with the fifth added, which fits 24 GB, while its Q4_K_M GGUF, 4-bit safetensors builds and Ollama entry need 32 GB. Runtimes 25, from vLLM 0.33.0, SGLang 0.5.23, Transformers 5.18.0 and later, llama.cpp's own MiniCPM-V 4.7 support and OpenBMB's entry on Ollama. Builds 15, OpenBMB publishes FP8, three 4-bit safetensors builds and GGUF. Terms 15, Apache 2.0 with nothing added. Download 10, nothing is gated. Hosted 0, no inference provider is mapped. 25 + 25 + 15 + 15 + 10 + 0 = 90.

DeepSeek V4.1 Flash 48

The cards cover architecture, parameters and context but not intended use, limitations, languages or a cut-off, so 8. Training data is a general description with no cut-off, which caps it at 5. The files changed on 16 and 17 October and DeepSeek's deepseek-recipe 0.2.0 changed the V4.1 prompt encoding on 20 October, inside 30 days (20). None of the 40 most recent questions across both repositories had a DeepSeek reply (0). Every release keeps its own repository and the update names what it replaces (10). File health loses 5 for an open, unanswered pull request saying the September template trails the encoding changes. 8 + 5 + 20 + 0 + 10 + 5 = 48.

MiniCPM-V 4.7 35B-A3B 68

Model card 8, it covers intended use, architecture and parameters but not limitations, context length, languages or a knowledge cut-off. Training data 0, none described. Last change 20, a commit on 3 November 2026. Responsiveness 20, OpenBMB answered 8 of 12 discussions. Version policy 10, earlier versions keep their repositories and the changes are dated and described. File health 10, the files agree. 8 + 0 + 20 + 20 + 10 + 10 = 68.

DeepSeek V4.1 Flash 50

The weights are safetensors only, but 10 comes off because the card's way to build prompts is running encoding.py from the repository, since there's no Jinja template. The files sit in DeepSeek's own organisation with a hash for every file. Nothing is published on safety and there's no guidance for agent use, so those two lines score 0. The security programme earns 5 for the security@deepseek.com reporting address in DeepSeek's site footer, read as for DeepSeek-V3.2, with no security.txt and no public advisories. The MIT licence carries no use policy, threshold or revocation, so licence risk keeps all 15.

MiniCPM-V 4.7 35B-A3B 55

File safety 25, safetensors and GGUF only, no Python in the main repository and no remote code needed. Provenance 15, the files come from the openbmb organisation OpenBMB's GitHub README links to, with a SHA-256 for every weight file. Safety evaluation 0 and agent guidance 0, nothing published on either, and the card has no limitations section. Licence risk 15, plain Apache 2.0. Security programme 0, no security.txt or SECURITY.md.

DeepSeek V4.1 Flash 75

There's no Jinja template in the 17 October repository, only code to run, so the template line gets 10. DeepSeek documents the DSML tool format both ways and ships its own parser in encoding.py and deepseek-recipe, but names no parser in a runtime (10, read as for DeepSeek-V3.2 and V4-Flash-0731), and one block can carry several calls (20). deepseek-recipe documents JSON Schema output via response_format (15). Thinking turns off in chat mode and takes an effort budget from 1 to 100, with reasoning returned in think tags (10). The 1M context was trained in (10).

MiniCPM-V 4.7 35B-A3B 70

Chat template 20, a Jinja file in the repository. Tool-calling format 10, the card shows the tools array going in but not the call coming back, and names no parser. Trained tool calling 20, the template renders several calls in one turn. Structured output 0, not documented or claimed. Reasoning control 10, enable_thinking per request, off by default, with the trace between markers. Context 10, 262,144 tokens native.