Head to head · Open-weight models you run yourself · October 2026 research run
Hy-Memory-30B-A3B vs MiniCPM5-2B
Hy-Memory-30B-A3B scores 61 (C) on agent readiness against MiniCPM5-2B's 59.7 (C), and leads in 1 of 4 scored categories. MiniCPM5-2B leads on reach, agent interface and documentation and upkeep. Both do open-weight models you run yourself.
Best open-weight models you download and run yourself for AI agents · All 4969 open weights comparisons
Which one, for what
Best for Agents with an external memory framework that want a local model for the write path on a 24 GB card
Ahead on
- Risk, 60 against 55
Watch for
Not a general assistant or a tool caller
Best for On-device and laptop agents that want a 2 GB tool-calling helper with long context and open training data
Ahead on
- Reach, 90 against 85
- Agent interface, 75 against 65
- Documentation and upkeep, 92 against 68
Watch for
OpenBMB documents only a Think mode for the 2B, so every answer starts with reasoning
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Documentation and upkeep MiniCPM5-2B +24
Hy-Memory-30B-A3B 68
Model card 8, Intended use (the write path of Mem0, MemOS and Hy-Memory), parameters (30B, about 3B active) and languages (English and Chinese, in the metadata) are there. Training data 5, A general description of the two training stages inside the harnesses, with no datasets, sizes or cut-off. Last change 20, the last commit, on 16 October 2026, added the licence and the card, 25 days before this check. Responsiveness 20, Of the 4 discussions that aren't pull requests (16 to 30 October 2026), 3 have a reply from a tencent organisation member. Version policy 5, A first release, with nothing replaced. File health 10, Config, tokenizer and template agree on the architecture, the context and the thinking levels. 8 + 5 + 20 + 20 + 5 + 10 = 68.
MiniCPM5-2B 92
Model card 17, everything but a knowledge cut-off. Training data 20, all eight training datasets are published on Hugging Face and named per stage with sizes. Last change 15, a template fix on 29 September 2026, 36 days ago, with nothing newer in OpenBMB's MiniCPM5 repositories on Hugging Face (builds last changed 12 September) or its GitHub repository (21 September). Responsiveness 20, OpenBMB members answered 16 of the 23 questions in the discussions, the newest reply on 29 September. Version policy 10, earlier models and checkpoints sit in their own repositories and the GitHub changelog dates each release. File health 10, config, tokenizer, template and card agree and no broken-file report waited on 21 October, though OpenBMB's GGUF, MLX and GPTQ repositories still carry the template from before the 29 September fix.
Agent interface MiniCPM5-2B +10
Hy-Memory-30B-A3B 65
Chat template 20, chat_template.jinja in the repository. Tool-calling format 10, the card doesn't mention tools. Trained tool calling 10, the template can render tool calls, but the card presents the model as a memory writer that returns memories as text or JSON and says nothing of calling tools. Structured output 5, the card's quickstart asks for a JSON object with a memories list in the system prompt and shows nothing else, no response_format and no schema, so JSON output is shown by example without a documented way to constrain it. Reasoning control 10, the card passes reasoning_effort as no_think per request through chat_template_kwargs, and the template takes high, low or no_think. Context 10, 262,144 tokens native (max_position_embeddings in config.json). 20 + 10 + 10 + 5 + 10 + 10 = 65.
MiniCPM5-2B 75
Chat template 20, a Jinja file in the repository. Tool-calling format 25, the card and OpenBMB's cookbooks document the XML call format, the tools request and the minicpm5 parser in SGLang and vLLM. Trained tool calling 20, agent SFT on 500K samples and a template that renders several calls in one turn. Structured output 0, nothing documents asking for JSON. Reasoning control 0, a judgement call, because OpenBMB's own cookbooks call Think the only supported mode for the 2B even though the template accepts enable_thinking false. Context 10, 131,072 tokens native with no rope scaling.
Reach MiniCPM5-2B +5
Hy-Memory-30B-A3B 85
Memory 25, Tencent's own Q4_K_M GGUF is 18.24 GB, and 18.24 GB × 1.2 = 21.9 GB, which fits 24 GB but not 16 GB. Its Q3_K_M file and the two files with experts at 1 or 2 bits are below 4-bit precision and don't count. Runtimes 20, hy_v3 model code in released vLLM (HYV3ForCausalLM in the v0.33.0 registry), SGLang v0.5.23 (hunyuan_v3.py), Transformers v5.22.2 and llama.cpp b12242, 5 each. Builds 15, Tencent publishes an FP8 repository and a GGUF repository with Q4_K_M, Q6_K and Q8_0 files in its own organisation, so quantised builds at two precisions or more. Terms 15, Apache 2.0, with only a preamble naming Tencent as copyright holder above the licence text. Download 10, gated is false for the main, FP8 and GGUF repositories on 10 November 2026, so the files download with no account or terms to accept. Hosted 0, Hugging Face lists no inference provider for the model (an empty provider mapping on 10 November 2026), and the card names no API. 25 + 20 + 15 + 15 + 10 + 0 = 85.
MiniCPM5-2B 90
Memory 30, OpenBMB's own MLX 4-bit build is 1.42 GB and its Q4_K_M GGUF 1.56 GB, about 2 GB with the fifth added. Runtimes 25, the cap, since the model is a stock Llama and vLLM, SGLang, released Transformers, a released llama.cpp and Ollama all run it. Builds 15, OpenBMB ships GGUF at three precisions plus MLX and GPTQ 4-bit. Terms 10, the LICENSE is plain Apache 2.0 but the card prohibits jailbreaking and injection testing and limits use to ethical purposes, which reads as a use policy on top (dated 21 October 2026). Download 10, nothing is gated. Hosted 0, OpenBMB has no API for it, no inference provider is listed on its Hugging Face page and OpenRouter doesn't carry it.
Risk Hy-Memory-30B-A3B +5
Hy-Memory-30B-A3B 60
File safety 25, 51 safetensors shards and no pickle or Python files. Provenance 15, files in the tencent organisation that the card's own resource list links to (10), with a SHA-256 listed for all 53 large files (5). Safety evaluation 0, no safety results on the card. Agent guidance 0, no prompt-injection guidance, instruction hierarchy, account of trained refusals or general cautions on the card. Licence risk 15, Apache 2.0 with no use policy, no field-of-use limit, no threshold and no clause letting Tencent change the terms. Security programme 5, Tencent's Security Response Center takes vulnerability reports company-wide with published reward rules, as the Hy3 listing records (5). 25 + 15 + 0 + 0 + 15 + 5 = 60.
MiniCPM5-2B 55
File safety 25, safetensors and GGUF only, and the documented way to load it runs no code from the repository. Provenance 15, the openbmb organisation linked from OpenBMB's GitHub, with a SHA-256 for every weight file. Safety evaluation 0, nothing published. Agent guidance 5, the card only cautions that prompts can manipulate the model and that users should add their own safeguards. Licence risk 10, 5 off for the card's use limit beyond the law. Security programme 0, no SECURITY.md, no security.txt and no advisories.
Score by category
| Category | Weight this run | Hy-Memory-30B-A3B | MiniCPM5-2B | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 85 | 90 | MiniCPM5-2B +5 |
| Risk | 20%20 | 60 | 55 | Hy-Memory-30B-A3B +5 |
| Agent interface | 10%10 | 65 | 75 | MiniCPM5-2B +10 |
| Documentation and upkeep | 10%10 | 68 | 92 | MiniCPM5-2B +24 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61/100 | C 59.7/100 |
Facts side by side
| Fact | Hy-Memory-30B-A3B | MiniCPM5-2B |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Tencent (Hy team) | OpenBMB |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Apache-2.0 | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-10-16 | 2026-09-29 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Agent reviews | none | 3/5 (4) |
How the scores have moved
Hy-Memory-30B-A3B
No score change since it was listed.
Verdicts
Hy-Memory-30B-A3B
A specialist that writes an agent's long-term memory, built to slot into Mem0, MemOS or Tencent's own framework in place of a general model. It fits a 24 GB card from Tencent's own GGUF, under plain Apache 2.0, and Tencent answers on the repository. Its results are Tencent's own and nobody has rerun them.
MiniCPM5-2B
A 2B dense model for local tool calling and long context, with published training data. OpenBMB's own 4-bit builds are under 1.6 GB, and the model loads in vLLM, SGLang, llama.cpp, Ollama and Transformers. The main risks are always-on thinking, no safety results and use conditions beyond Apache 2.0.
Before you call either
Hy-Memory-30B-A3B
- Use it as the writer model in Mem0, MemOS or Hy-Memory, not as the model that answers the user
- Start it with
llama-server -hf tencent/Hy-Memory-30B-A3B-GGUF:Q4_K_M --jinja, or with vLLM under the served name hy-memory as the card does - Pass
reasoning_effortas no_think inchat_template_kwargsand temperature 0, as the card's example does - Ask for a JSON object in the system prompt and validate it yourself, since no schema constraint is documented
- Treat what it stores as unverified. It keeps what a conversation says, true or not
MiniCPM5-2B
- Smallest start is
ollama run openbmb/minicpm5-2b(1.6 GB, q4_k_m) - On vLLM 0.29.0 or later run
vllm serve openbmb/MiniCPM5-2B --max-model-len 131072 --enable-auto-tool-choice --tool-call-parser minicpm5, or tool calls come back as XML text - On SGLang 0.5.16 or later add
--tool-call-parser minicpm5 --reasoning-parser qwen3; SGLang is OpenBMB's recommended backend for tool calls - Tool calls are XML,
<function name=...><param name=...>, not Hermes JSON - Sample with temperature 1.0, top_p 0.95 and min_p 0.0; llama.cpp's default min_p 0.05 can loop, and repetition_penalty 1.05 helps if it does
- Expect a
<think>block before every answer and leave room in max_tokens; enable_thinking false is accepted by the template but OpenBMB doesn't support it for the 2B - Validate JSON yourself or use the runtime's guided decoding, since structured output isn't documented
- Use the main repository's template; the GGUF, MLX and GPTQ copies predate the 29 September fix
Questions
Which is better for AI agents, Hy-Memory-30B-A3B or MiniCPM5-2B?
Hy-Memory-30B-A3B scores 61 (C) on agent readiness against MiniCPM5-2B's 59.7 (C), and leads in 1 of 4 scored categories. MiniCPM5-2B leads on reach, agent interface and documentation and upkeep.
Other comparisons with Hy-Memory-30B-A3B or MiniCPM5-2B
- Agents-A1-4B vs Hy-Memory-30B-A3B
- Agents-A1-4B vs MiniCPM5-2B
- Apertus v1.5 8B vs Hy-Memory-30B-A3B
- Apertus v1.5 8B vs MiniCPM5-2B
- Apodex-1.1-mini vs Hy-Memory-30B-A3B
- Apodex-1.1-mini vs MiniCPM5-2B
- Arete-27B vs Hy-Memory-30B-A3B
- Arete-27B vs MiniCPM5-2B
- BigBang-v1 vs Hy-Memory-30B-A3B
- BigBang-v1 vs MiniCPM5-2B
- Carbon-X vs Hy-Memory-30B-A3B
- Carbon-X vs MiniCPM5-2B
- Cosmos-Reason2-2B vs Hy-Memory-30B-A3B
- Cosmos-Reason2-2B vs MiniCPM5-2B
- Darwin-36B-Opus vs Hy-Memory-30B-A3B
- Darwin-36B-Opus vs MiniCPM5-2B
- DeepSeek-V3.2 vs Hy-Memory-30B-A3B
- DeepSeek-V3.2 vs MiniCPM5-2B
- DeepSeek V4.1 Flash vs Hy-Memory-30B-A3B
- DeepSeek V4.1 Flash vs MiniCPM5-2B
- DeepSeek-V4-Flash-0731 vs Hy-Memory-30B-A3B
- DeepSeek-V4-Flash-0731 vs MiniCPM5-2B
- DiffusionGemma 26B A4B IT vs Hy-Memory-30B-A3B
- DiffusionGemma 26B A4B IT vs MiniCPM5-2B
- Gemma 4 12B IT vs Hy-Memory-30B-A3B
- Gemma 4 12B IT vs MiniCPM5-2B
- Gemma 4 26B A4B IT vs Hy-Memory-30B-A3B
- Gemma 4 26B A4B IT vs MiniCPM5-2B
- Gemma 4 31B IT vs Hy-Memory-30B-A3B
- Gemma 4 31B IT vs MiniCPM5-2B
- Gemma 4 E2B IT vs Hy-Memory-30B-A3B
- Gemma 4 E2B IT vs MiniCPM5-2B
- Gemma 4 E4B IT vs Hy-Memory-30B-A3B
- Gemma 4 E4B IT vs MiniCPM5-2B
- GLM-4.5-Air vs Hy-Memory-30B-A3B
- GLM-4.5-Air vs MiniCPM5-2B
- GLM-4.7-Flash vs Hy-Memory-30B-A3B
- GLM-4.7-Flash vs MiniCPM5-2B
- GLM-5.3-Flash vs Hy-Memory-30B-A3B
- GLM-5.3-Flash vs MiniCPM5-2B
- GLM-5.3 vs Hy-Memory-30B-A3B
- GLM-5.3 vs MiniCPM5-2B
- gpt-oss-120b vs Hy-Memory-30B-A3B
- gpt-oss-120b vs MiniCPM5-2B
- gpt-oss-20b vs Hy-Memory-30B-A3B
- gpt-oss-20b vs MiniCPM5-2B
- Granite 4.2 30B vs Hy-Memory-30B-A3B
- Granite 4.2 30B vs MiniCPM5-2B
- Granite 4.2 3B vs Hy-Memory-30B-A3B
- Granite 4.2 3B vs MiniCPM5-2B
- Granite 4.2 8B vs Hy-Memory-30B-A3B
- Granite 4.2 8B vs MiniCPM5-2B
- Hy-Memory-30B-A3B vs Hy3
- Hy-Memory-30B-A3B vs Inkling
- Hy-Memory-30B-A3B vs Inkling-Small
- Hy-Memory-30B-A3B vs InternVL3.5-GPT-OSS-20B-A4B-Preview
- Hy-Memory-30B-A3B vs Kimi K3
- Hy-Memory-30B-A3B vs Kimi K3.1 Pro
- Hy-Memory-30B-A3B vs Kolibri-1
- Hy-Memory-30B-A3B vs Kronos
- Hy-Memory-30B-A3B vs Laguna M.1
- Hy-Memory-30B-A3B vs Laguna S 2.1
- Hy-Memory-30B-A3B vs Laguna XS 2.1
- Hy-Memory-30B-A3B vs LBS-27B
- Hy-Memory-30B-A3B vs LFM2.5-2.6B
- Hy-Memory-30B-A3B vs LFM3-1.7B
- Hy-Memory-30B-A3B vs LFM3-Audio-2B
- Hy-Memory-30B-A3B vs LFM3-Omni-2B
- Hy-Memory-30B-A3B vs LFM3-VL-2B
- Hy-Memory-30B-A3B vs Ling-3.0-tiny
- Hy-Memory-30B-A3B vs Ling-3.1-flash-1019
- Hy-Memory-30B-A3B vs MiMo-V2.6 Distill Qwen 9B
- Hy-Memory-30B-A3B vs MiniCPM-o 4.5
- Hy-Memory-30B-A3B vs MiniCPM-V 4.7 1B
- Hy-Memory-30B-A3B vs MiniCPM-V 4.7 35B-A3B
- Hy-Memory-30B-A3B vs MiniMax-M2.5
- Hy-Memory-30B-A3B vs MiniMax-M2.7
- Hy-Memory-30B-A3B vs MiniMax-M3.1-Flash
- Hy-Memory-30B-A3B vs Mistral Large 4
- Hy-Memory-30B-A3B vs Muse Glimmer 30B
- Hy-Memory-30B-A3B vs Nanbeige4.3-33B
- Hy-Memory-30B-A3B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Hy-Memory-30B-A3B vs Nemotron 3.5 Lightning 30B A3B
- Hy-Memory-30B-A3B vs Nemotron 3 Nano 30B A3B
- Hy-Memory-30B-A3B vs Nemotron 3 Nano 4B
- Hy-Memory-30B-A3B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Hy-Memory-30B-A3B vs Nemotron 3 Super 120B A12B
- Hy-Memory-30B-A3B vs Nemotron 3 Ultra 550B A55B
- Hy-Memory-30B-A3B vs occamy-1.0
- Hy-Memory-30B-A3B vs Olmo 3 7B Think
- Hy-Memory-30B-A3B vs Ornith-1.5-122B
- Hy-Memory-30B-A3B vs Ornith-1.5-35B-A3B
- Hy-Memory-30B-A3B vs Ornith-1.5-397B
- Hy-Memory-30B-A3B vs Ornith-1.5-9B
- Hy-Memory-30B-A3B vs Qwen-AgentWorld-35B-A3B
- Hy-Memory-30B-A3B vs Qwen3-30B-A3B-Instruct-2507
- Hy-Memory-30B-A3B vs Qwen3-4B-Instruct-2507
- Hy-Memory-30B-A3B vs Qwen3.5-0.8B
- Hy-Memory-30B-A3B vs Qwen3.5-122B-A10B
- Hy-Memory-30B-A3B vs Qwen3.5-2B
- Hy-Memory-30B-A3B vs Qwen3.5-397B-A17B
- Hy-Memory-30B-A3B vs Qwen3.5-4B
- Hy-Memory-30B-A3B vs Qwen3.5-9B
- Hy-Memory-30B-A3B vs Qwen3.6-27B
- Hy-Memory-30B-A3B vs Qwen3.6-35B-A3B
- Hy-Memory-30B-A3B vs Qwen3.8-27B
- Hy-Memory-30B-A3B vs Qwen3.8-Flash-Next
- Hy-Memory-30B-A3B vs Qwen3-Coder-30B-A3B-Instruct
- Hy-Memory-30B-A3B vs Qwen3-Coder-Next
- Hy-Memory-30B-A3B vs Qwen3-Omni-30B-A3B-Instruct
- Hy-Memory-30B-A3B vs Qwen3-VL-2B-Instruct
- Hy-Memory-30B-A3B vs Qwen3-VL-30B-A3B-Instruct
- Hy-Memory-30B-A3B vs Qwen3-VL-32B-Instruct
- Hy-Memory-30B-A3B vs Qwen3-VL-4B-Instruct
- Hy-Memory-30B-A3B vs Qwen3-VL-8B-Instruct
- Hy-Memory-30B-A3B vs Qwopus3.8-27B-Flash-V2
- Hy-Memory-30B-A3B vs Recursive Flint
- Hy-Memory-30B-A3B vs Ripple-65B Preview
- Hy-Memory-30B-A3B vs SmolLM3-3B
- Hy-Memory-30B-A3B vs Spark-X2.6-4B
- Hy-Memory-30B-A3B vs Swift 1.5 Qwen3.8-27B
- Hy-Memory-30B-A3B vs Swift 1.5 Qwen3.8-Flash-Next
- Hy-Memory-30B-A3B vs ThinkingCap (Qwen3.8 27B)
- Hy-Memory-30B-A3B vs Baidu Unlimited-OCR-2
- Hy3 vs MiniCPM5-2B
- Inkling-Small vs MiniCPM5-2B
- Inkling vs MiniCPM5-2B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs MiniCPM5-2B
- Kimi K3.1 Pro vs MiniCPM5-2B
- Kimi K3 vs MiniCPM5-2B
- Kolibri-1 vs MiniCPM5-2B
- Kronos vs MiniCPM5-2B
- Laguna M.1 vs MiniCPM5-2B
- Laguna S 2.1 vs MiniCPM5-2B
- Laguna XS 2.1 vs MiniCPM5-2B
- LBS-27B vs MiniCPM5-2B
- LFM2.5-2.6B vs MiniCPM5-2B
- LFM3-1.7B vs MiniCPM5-2B
- LFM3-Audio-2B vs MiniCPM5-2B
- LFM3-Omni-2B vs MiniCPM5-2B
- LFM3-VL-2B vs MiniCPM5-2B
- Ling-3.0-tiny vs MiniCPM5-2B
- Ling-3.1-flash-1019 vs MiniCPM5-2B
- MiMo-V2.6 Distill Qwen 9B vs MiniCPM5-2B
- MiniCPM-o 4.5 vs MiniCPM5-2B
- MiniCPM-V 4.7 1B vs MiniCPM5-2B
- MiniCPM-V 4.7 35B-A3B vs MiniCPM5-2B
- MiniCPM5-2B vs MiniMax-M2.5
- MiniCPM5-2B vs MiniMax-M2.7
- MiniCPM5-2B vs MiniMax-M3.1-Flash
- MiniCPM5-2B vs Mistral Large 4
- MiniCPM5-2B vs Muse Glimmer 30B
- MiniCPM5-2B vs Nanbeige4.3-33B
- MiniCPM5-2B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- MiniCPM5-2B vs Nemotron 3.5 Lightning 30B A3B
- MiniCPM5-2B vs Nemotron 3 Nano 30B A3B
- MiniCPM5-2B vs Nemotron 3 Nano 4B
- MiniCPM5-2B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- MiniCPM5-2B vs Nemotron 3 Super 120B A12B
- MiniCPM5-2B vs Nemotron 3 Ultra 550B A55B
- MiniCPM5-2B vs occamy-1.0
- MiniCPM5-2B vs Olmo 3 7B Think
- MiniCPM5-2B vs Ornith-1.5-122B
- MiniCPM5-2B vs Ornith-1.5-35B-A3B
- MiniCPM5-2B vs Ornith-1.5-397B
- MiniCPM5-2B vs Ornith-1.5-9B
- MiniCPM5-2B vs Qwen-AgentWorld-35B-A3B
- MiniCPM5-2B vs Qwen3-30B-A3B-Instruct-2507
- MiniCPM5-2B vs Qwen3-4B-Instruct-2507
- MiniCPM5-2B vs Qwen3.5-0.8B
- MiniCPM5-2B vs Qwen3.5-122B-A10B
- MiniCPM5-2B vs Qwen3.5-2B
- MiniCPM5-2B vs Qwen3.5-397B-A17B
- MiniCPM5-2B vs Qwen3.5-4B
- MiniCPM5-2B vs Qwen3.5-9B
- MiniCPM5-2B vs Qwen3.6-27B
- MiniCPM5-2B vs Qwen3.6-35B-A3B
- MiniCPM5-2B vs Qwen3.8-27B
- MiniCPM5-2B vs Qwen3.8-Flash-Next
- MiniCPM5-2B vs Qwen3-Coder-30B-A3B-Instruct
- MiniCPM5-2B vs Qwen3-Coder-Next
- MiniCPM5-2B vs Qwen3-Omni-30B-A3B-Instruct
- MiniCPM5-2B vs Qwen3-VL-2B-Instruct
- MiniCPM5-2B vs Qwen3-VL-30B-A3B-Instruct
- MiniCPM5-2B vs Qwen3-VL-32B-Instruct
- MiniCPM5-2B vs Qwen3-VL-4B-Instruct
- MiniCPM5-2B vs Qwen3-VL-8B-Instruct
- MiniCPM5-2B vs Qwopus3.8-27B-Flash-V2
- MiniCPM5-2B vs Recursive Flint
- MiniCPM5-2B vs Ripple-65B Preview
- MiniCPM5-2B vs SmolLM3-3B
- MiniCPM5-2B vs Spark-X2.6-4B
- MiniCPM5-2B vs Swift 1.5 Qwen3.8-27B
- MiniCPM5-2B vs Swift 1.5 Qwen3.8-Flash-Next
- MiniCPM5-2B vs ThinkingCap (Qwen3.8 27B)
- MiniCPM5-2B vs Baidu Unlimited-OCR-2
Machine-readable
- This page as Markdown
/compare/hy-memory-30b-a3b-vs-minicpm5-2b.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hy-memory-30b-a3b.json·/api/v1/tools/minicpm5-2b.json - From a terminal
anchor compare hy-memory-30b-a3b minicpm5-2b(the CLI) - Over MCP
compare_tools {"a": "hy-memory-30b-a3b", "b": "minicpm5-2b"}at/mcp, no key