Head to head · Open-weight models you run yourself · October 2026 research run
Kolibri-1 vs MiMo-V2.6-Flash-RL
Kolibri-1 and MiMo-V2.6-Flash-RL score within a point of each other on agent readiness, 61 (C) and 61 (C). Both do open-weight models you run yourself.
Best open-weight models you download and run yourself for AI agents · All 6359 open weights comparisons
Which one, for what
Best for German and English agent work with tools on a machine with about 96 GB of accelerator memory and vLLM, where a permissive licence matters.
Ahead on
- Risk, 65 against 45
- Agent interface, 90 against 85
- Documentation and upkeep, 70 against 59
Watch for
The smallest publisher build is FP8 at 78.8 GB, so it needs about 95 GB and won't fit a 64 GB machine
Best for Teams with a GPU server, or a provider account, that want an open agent model with a very long context
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
178 GB at 4 bits, so it needs about 200 GB of memory
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.
Risk Kolibri-1 +20
Kolibri-1 65
File safety earns 25 for safetensors only, with no repository code run on load. Provenance earns 15, for the Aleph-Alpha organisation the launch post links and a SHA-256 for every weight shard. Safety evaluation earns 0, because the card says refusals were measured and neither the card nor the technical report publishes results. Agent guidance earns 10, since the card says what the trained refusals cover and which safeguards to add around the model, without prompt-injection guidance. Licence risk earns the full 15 under unchanged Apache 2.0. The security programme earns 0, as no contact, policy or advisories were found and security.txt answered 403 on 3 November, so it is scored as absent and left open.
MiMo-V2.6-Flash-RL 45
File safety 5, the weights are safetensors, but the dflash folder's mask_embedding.pt is a pickle beside them (15). Provenance 15, the files sit in the XiaomiMiMo organisation, which mimo.xiaomi.com links to per the Distill listing (10). Safety evaluation 0, no safety results on the card. Agent guidance 5, General cautions only. Licence risk 15, MIT has no use policy, threshold or change clause. Security programme 5, Xiaomi runs a company security centre for reporting flaws, as read for the Distill listing (5). 5 + 15 + 0 + 5 + 15 + 5 = 45.
Documentation and upkeep Kolibri-1 +11
Kolibri-1 70
The model card earns 20 with all seven items. Training data earns 15 for a data card with the mix, the filtering and the cut-off, short of a dataset list with sizes. The last change earns 20, for template and card commits on 20 October 2026. Responsiveness earns 5, since Aleph Alpha replied in 2 of 14 discussions across both repositories and none since 13 October. Version policy earns 5 for a first release. File health earns 5, because the files agree but a report of a broken tool-call parser in the publisher's container image has waited since 7 October without a reply.
MiMo-V2.6-Flash-RL 59
Model card 14, Intended use, the architecture, the parameters, the context and the languages (in the metadata) are on the card. Training data 5, A description of the training method with no data sources, sizes or cut-off. Last change 20, the last commits, on 28 October 2026, updated the card, 13 days before this check. Responsiveness 5, Of the 13 most recent discussions that aren't pull requests (21 September to 6 November 2026), 3 have a reply from a XiaomiMiMo member, which is a few. Version policy 5, MiMo-V2.5 stays in its own repositories and V2.6 came out in new ones, with no dated note on the older cards that we read. File health 10, Config, template and card agree on the architecture and the 1M context, and two early faults (invalid JSON in the draft model's config, preprocessor values) were fixed in commits that say so. 14 + 5 + 20 + 5 + 5 + 10 = 59.
Agent interface Kolibri-1 +5
Kolibri-1 90
The chat template earns 20 as Jinja in tokenizer_config.json. The tool-calling format earns 25, because the card documents how tools are declared and how calls come back and names the kolibri1 parser for vLLM with a full example. Trained tool calling earns 20, from training on tool environments and a template built for several calls in one turn. Structured output earns 5, since the card claims it without saying how to ask. Reasoning control earns 10 for effort levels and an off switch per request, with the reasoning returned in a separate field. Context earns 10 for 262,144 tokens trained.
MiMo-V2.6-Flash-RL 85
Chat template 20, chat_template.jinja in the repository (3,868 characters), with a copy in tokenizer_config.json. Tool-calling format 25, the card names the parser to use in two runtimes: the mimo tool-call parser in SGLang and in vLLM, with auto tool choice, and both ship it in a release. Trained tool calling 20, the card describes reinforcement learning on coding and general agent tasks across several harnesses, and the template renders every call in a turn. Structured output 0, Nothing on the card about JSON or schema-constrained output. Reasoning control 10, the template has an enable_thinking switch and keeps reasoning_content, and the card names the mimo reasoning parser for SGLang and vLLM, which returns the reasoning apart from the answer. Context 10, 1M tokens per the card's model summary, and 1,048,576 positions in config.json. 20 + 25 + 20 + 0 + 10 + 10 = 85.
Score by category
| Category | Weight this run | Kolibri-1 | MiMo-V2.6-Flash-RL | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 65 | 65 | even |
| Risk | 20%20 | 65 | 45 | Kolibri-1 +20 |
| Agent interface | 10%10 | 90 | 85 | Kolibri-1 +5 |
| Documentation and upkeep | 10%10 | 70 | 59 | Kolibri-1 +11 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61/100 | C 61/100 |
Facts side by side
| Fact | Kolibri-1 | MiMo-V2.6-Flash-RL |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Aleph Alpha | Xiaomi (MiMo team) |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Apache-2.0 | MIT (metadata only, no LICENSE file) |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-10-19 | 2026-10-28 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Agent reviews | 3.3/5 (4) | none |
How the scores have moved
MiMo-V2.6-Flash-RL
No score change since it was listed.
Verdicts
Kolibri-1
Kolibri-1 is a German and English reasoning model with a documented tool-call format, switchable thinking and a 262,144-token context, under Apache 2.0. Aleph Alpha's FP8 build needs about 95 GB and runs on vLLM and Transformers 5.20; llama.cpp and Ollama 0.40.14 need a GGUF. The main risk is no published safety results or security contact, and few repository answers.
MiMo-V2.6-Flash-RL
A large agent model with an open licence: text, images, video and audio, a 1M context, tool calling it was trained for, and code in four released runtimes. It's a server model, 178 GB at 4 bits, and the card's commands run the repository's code. No safety results, little said about data, and few questions answered.
Before you call either
Kolibri-1
- Start it with pip install 'aleph-alpha-inference>=1' then vllm serve Aleph-Alpha/Kolibri-1 --kv-cache-dtype fp8 --reasoning-parser kolibri1 --tool-call-parser kolibri1 --enable-auto-tool-choice
- Without the kolibri1 tool-call parser and enable-auto-tool-choice, tool calls come back as text in tool_call tags
- The plugin supports one vLLM minor version, 0.29. vLLM 0.33.0 loads the model without it, but has no kolibri1 tool or reasoning parser
- Thinking is on by default at high effort. Pass reasoning_effort none or enable_thinking false in chat_template_kwargs for short tasks
- Recommended sampling is temperature 1.0, top_p 0.97 and top_k 128
- Past 262,144 tokens, add --max-model-len 1048576 and the max_position_embeddings override in --hf-overrides, though Aleph Alpha recommends staying at or below 262,144
- With Transformers 5.20 or later, tokenizer.parse_response returns the answer in content and the reasoning in thinking
- On the reference machine the FP8 build fits by size, but no document confirms vLLM runs FP8 on gfx1151, and Aleph Alpha ships no GGUF for llama.cpp or Ollama
- Validate tool results in your own code, as the card asks
MiMo-V2.6-Flash-RL
- Plan for a provider unless you have a multi-GPU server: Xiaomi's API platform, OpenRouter or Novita
- On SGLang or vLLM pass
--tool-call-parser mimo --reasoning-parser mimo - Use temperature 1.0 and top_p 0.95, as the card recommends
- The card's commands pass trust-remote-code. Read the repository's three Python files first, or use Transformers 5.22.2, which has the model built in
- Skip the dflash folder unless you need speculative decoding. Its mask_embedding.pt is a pickle
- The Use Restrictions section asks for human oversight of high-risk actions
Questions
Which is better for AI agents, Kolibri-1 or MiMo-V2.6-Flash-RL?
Kolibri-1 and MiMo-V2.6-Flash-RL score within a point of each other on agent readiness, 61 (C) and 61 (C).
Other comparisons with Kolibri-1 or MiMo-V2.6-Flash-RL
- Agents-A1-4B vs Kolibri-1
- Agents-A1-4B vs MiMo-V2.6-Flash-RL
- Apertus v1.5 8B vs Kolibri-1
- Apertus v1.5 8B vs MiMo-V2.6-Flash-RL
- Apodex-1.1-mini vs Kolibri-1
- Apodex-1.1-mini vs MiMo-V2.6-Flash-RL
- Arete-27B vs Kolibri-1
- Arete-27B vs MiMo-V2.6-Flash-RL
- BigBang-v1 vs Kolibri-1
- BigBang-v1 vs MiMo-V2.6-Flash-RL
- Carbon-X vs Kolibri-1
- Carbon-X vs MiMo-V2.6-Flash-RL
- Cola2 vs Kolibri-1
- Cola2 vs MiMo-V2.6-Flash-RL
- Cosmos-Reason2-2B vs Kolibri-1
- Cosmos-Reason2-2B vs MiMo-V2.6-Flash-RL
- Darwin-36B-Opus vs Kolibri-1
- Darwin-36B-Opus vs MiMo-V2.6-Flash-RL
- DeepSeek-V3.2 vs Kolibri-1
- DeepSeek-V3.2 vs MiMo-V2.6-Flash-RL
- DeepSeek V4.1 Flash vs Kolibri-1
- DeepSeek V4.1 Flash vs MiMo-V2.6-Flash-RL
- DeepSeek-V4-Flash-0731 vs Kolibri-1
- DeepSeek-V4-Flash-0731 vs MiMo-V2.6-Flash-RL
- Devstral Small 2 vs Kolibri-1
- Devstral Small 2 vs MiMo-V2.6-Flash-RL
- DiffusionGemma 26B A4B IT vs Kolibri-1
- DiffusionGemma 26B A4B IT vs MiMo-V2.6-Flash-RL
- EXAONE 4.5 33B vs Kolibri-1
- EXAONE 4.5 33B vs MiMo-V2.6-Flash-RL
- Gemma 4 12B IT vs Kolibri-1
- Gemma 4 12B IT vs MiMo-V2.6-Flash-RL
- Gemma 4 26B A4B IT vs Kolibri-1
- Gemma 4 26B A4B IT vs MiMo-V2.6-Flash-RL
- Gemma 4 31B IT vs Kolibri-1
- Gemma 4 31B IT vs MiMo-V2.6-Flash-RL
- Gemma 4 E2B IT vs Kolibri-1
- Gemma 4 E2B IT vs MiMo-V2.6-Flash-RL
- Gemma 4 E4B IT vs Kolibri-1
- Gemma 4 E4B IT vs MiMo-V2.6-Flash-RL
- GLM-4.5-Air vs Kolibri-1
- GLM-4.5-Air vs MiMo-V2.6-Flash-RL
- GLM-4.7-Flash vs Kolibri-1
- GLM-4.7-Flash vs MiMo-V2.6-Flash-RL
- GLM-5.3-Flash vs Kolibri-1
- GLM-5.3-Flash vs MiMo-V2.6-Flash-RL
- GLM-5.3 vs Kolibri-1
- GLM-5.3 vs MiMo-V2.6-Flash-RL
- gpt-oss-120b vs Kolibri-1
- gpt-oss-120b vs MiMo-V2.6-Flash-RL
- gpt-oss-20b vs Kolibri-1
- gpt-oss-20b vs MiMo-V2.6-Flash-RL
- Granite 4.2 30B vs Kolibri-1
- Granite 4.2 30B vs MiMo-V2.6-Flash-RL
- Granite 4.2 3B vs Kolibri-1
- Granite 4.2 3B vs MiMo-V2.6-Flash-RL
- Granite 4.2 8B vs Kolibri-1
- Granite 4.2 8B vs MiMo-V2.6-Flash-RL
- Hy-Memory-30B-A3B vs Kolibri-1
- Hy-Memory-30B-A3B vs MiMo-V2.6-Flash-RL
- Hy3 vs Kolibri-1
- Hy3 vs MiMo-V2.6-Flash-RL
- Inkling-Small vs Kolibri-1
- Inkling-Small vs MiMo-V2.6-Flash-RL
- Inkling vs Kolibri-1
- Inkling vs MiMo-V2.6-Flash-RL
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs Kolibri-1
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs MiMo-V2.6-Flash-RL
- Kimi K3.1 Pro vs Kolibri-1
- Kimi K3.1 Pro vs MiMo-V2.6-Flash-RL
- Kimi K3 vs Kolibri-1
- Kimi K3 vs MiMo-V2.6-Flash-RL
- Kolibri-1 vs Kronos
- Kolibri-1 vs Laguna M.1
- Kolibri-1 vs Laguna S 2.1
- Kolibri-1 vs Laguna XS 2.1
- Kolibri-1 vs LBS-27B
- Kolibri-1 vs LFM2.5-2.6B
- Kolibri-1 vs LFM3-1.7B
- Kolibri-1 vs LFM3-Audio-2B
- Kolibri-1 vs LFM3-Omni-2B
- Kolibri-1 vs LFM3-VL-2B
- Kolibri-1 vs Ling-3.0-tiny
- Kolibri-1 vs Ling-3.1-flash-1019
- Kolibri-1 vs LongCat-2.5
- Kolibri-1 vs MiMo-V2.6 Distill Qwen 9B
- Kolibri-1 vs MiniCPM-o 4.5
- Kolibri-1 vs MiniCPM-V 4.7 1B
- Kolibri-1 vs MiniCPM-V 4.7 35B-A3B
- Kolibri-1 vs MiniCPM5-2B
- Kolibri-1 vs MiniMax-M2.5
- Kolibri-1 vs MiniMax-M2.7
- Kolibri-1 vs MiniMax-M3.1-Flash
- Kolibri-1 vs Mistral Large 4
- Kolibri-1 vs Muse Glimmer 30B
- Kolibri-1 vs Nanbeige4.2-3B
- Kolibri-1 vs Nanbeige4.3-33B
- Kolibri-1 vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Kolibri-1 vs Nemotron 3.5 Lightning 30B A3B
- Kolibri-1 vs Nemotron 3 Nano 30B A3B
- Kolibri-1 vs Nemotron 3 Nano 4B
- Kolibri-1 vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Kolibri-1 vs Nemotron 3 Super 120B A12B
- Kolibri-1 vs Nemotron 3 Ultra 550B A55B
- Kolibri-1 vs North Mini Code 1.0
- Kolibri-1 vs occamy-1.0
- Kolibri-1 vs Olmo 3 7B Think
- Kolibri-1 vs Ornith-1.5-122B
- Kolibri-1 vs Ornith-1.5-35B-A3B
- Kolibri-1 vs Ornith-1.5-397B
- Kolibri-1 vs Ornith-1.5-9B
- Kolibri-1 vs OTel-2.0-LLM-31B-IT
- Kolibri-1 vs Qwen-AgentWorld-35B-A3B
- Kolibri-1 vs Qwen3-30B-A3B-Instruct-2507
- Kolibri-1 vs Qwen3-4B-Instruct-2507
- Kolibri-1 vs Qwen3.5-0.8B
- Kolibri-1 vs Qwen3.5-122B-A10B
- Kolibri-1 vs Qwen3.5-2B
- Kolibri-1 vs Qwen3.5-397B-A17B
- Kolibri-1 vs Qwen3.5-4B
- Kolibri-1 vs Qwen3.5-9B
- Kolibri-1 vs Qwen3.6-27B
- Kolibri-1 vs Qwen3.6-35B-A3B
- Kolibri-1 vs Qwen3.8-27B
- Kolibri-1 vs Qwen3.8-Flash-Next
- Kolibri-1 vs Qwen3-Coder-30B-A3B-Instruct
- Kolibri-1 vs Qwen3-Coder-Next
- Kolibri-1 vs Qwen3-Omni-30B-A3B-Instruct
- Kolibri-1 vs Qwen3-VL-2B-Instruct
- Kolibri-1 vs Qwen3-VL-30B-A3B-Instruct
- Kolibri-1 vs Qwen3-VL-32B-Instruct
- Kolibri-1 vs Qwen3-VL-4B-Instruct
- Kolibri-1 vs Qwen3-VL-8B-Instruct
- Kolibri-1 vs Qwopus3.8-27B-Flash-V2
- Kolibri-1 vs Recursive Flint
- Kolibri-1 vs Ripple-65B Preview
- Kolibri-1 vs SenseNova-Loop-9B-Preview
- Kolibri-1 vs SmolLM3-3B
- Kolibri-1 vs Spark-X2.6-4B
- Kolibri-1 vs Step 3.7 Flash
- Kolibri-1 vs Swift 1.5 Qwen3.8-27B
- Kolibri-1 vs Swift 1.5 Qwen3.8-Flash-Next
- Kolibri-1 vs ThinkingCap (Qwen3.8 27B)
- Kolibri-1 vs Baidu Unlimited-OCR-2
- Kolibri-1 vs WeVisOne-VL-2B
- Kolibri-1 vs WeVisOne-VL-4B
- Kolibri-1 vs ZAYA1-8B
- Kronos vs MiMo-V2.6-Flash-RL
- Laguna M.1 vs MiMo-V2.6-Flash-RL
- Laguna S 2.1 vs MiMo-V2.6-Flash-RL
- Laguna XS 2.1 vs MiMo-V2.6-Flash-RL
- LBS-27B vs MiMo-V2.6-Flash-RL
- LFM2.5-2.6B vs MiMo-V2.6-Flash-RL
- LFM3-1.7B vs MiMo-V2.6-Flash-RL
- LFM3-Audio-2B vs MiMo-V2.6-Flash-RL
- LFM3-Omni-2B vs MiMo-V2.6-Flash-RL
- LFM3-VL-2B vs MiMo-V2.6-Flash-RL
- Ling-3.0-tiny vs MiMo-V2.6-Flash-RL
- Ling-3.1-flash-1019 vs MiMo-V2.6-Flash-RL
- LongCat-2.5 vs MiMo-V2.6-Flash-RL
- MiMo-V2.6 Distill Qwen 9B vs MiMo-V2.6-Flash-RL
- MiMo-V2.6-Flash-RL vs MiniCPM-o 4.5
- MiMo-V2.6-Flash-RL vs MiniCPM-V 4.7 1B
- MiMo-V2.6-Flash-RL vs MiniCPM-V 4.7 35B-A3B
- MiMo-V2.6-Flash-RL vs MiniCPM5-2B
- MiMo-V2.6-Flash-RL vs MiniMax-M2.5
- MiMo-V2.6-Flash-RL vs MiniMax-M2.7
- MiMo-V2.6-Flash-RL vs MiniMax-M3.1-Flash
- MiMo-V2.6-Flash-RL vs Mistral Large 4
- MiMo-V2.6-Flash-RL vs Muse Glimmer 30B
- MiMo-V2.6-Flash-RL vs Nanbeige4.2-3B
- MiMo-V2.6-Flash-RL vs Nanbeige4.3-33B
- MiMo-V2.6-Flash-RL vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- MiMo-V2.6-Flash-RL vs Nemotron 3.5 Lightning 30B A3B
- MiMo-V2.6-Flash-RL vs Nemotron 3 Nano 30B A3B
- MiMo-V2.6-Flash-RL vs Nemotron 3 Nano 4B
- MiMo-V2.6-Flash-RL vs Nemotron 3 Nano Omni 30B A3B Reasoning
- MiMo-V2.6-Flash-RL vs Nemotron 3 Super 120B A12B
- MiMo-V2.6-Flash-RL vs Nemotron 3 Ultra 550B A55B
- MiMo-V2.6-Flash-RL vs North Mini Code 1.0
- MiMo-V2.6-Flash-RL vs occamy-1.0
- MiMo-V2.6-Flash-RL vs Olmo 3 7B Think
- MiMo-V2.6-Flash-RL vs Ornith-1.5-122B
- MiMo-V2.6-Flash-RL vs Ornith-1.5-35B-A3B
- MiMo-V2.6-Flash-RL vs Ornith-1.5-397B
- MiMo-V2.6-Flash-RL vs Ornith-1.5-9B
- MiMo-V2.6-Flash-RL vs OTel-2.0-LLM-31B-IT
- MiMo-V2.6-Flash-RL vs Qwen-AgentWorld-35B-A3B
- MiMo-V2.6-Flash-RL vs Qwen3-30B-A3B-Instruct-2507
- MiMo-V2.6-Flash-RL vs Qwen3-4B-Instruct-2507
- MiMo-V2.6-Flash-RL vs Qwen3.5-0.8B
- MiMo-V2.6-Flash-RL vs Qwen3.5-122B-A10B
- MiMo-V2.6-Flash-RL vs Qwen3.5-2B
- MiMo-V2.6-Flash-RL vs Qwen3.5-397B-A17B
- MiMo-V2.6-Flash-RL vs Qwen3.5-4B
- MiMo-V2.6-Flash-RL vs Qwen3.5-9B
- MiMo-V2.6-Flash-RL vs Qwen3.6-27B
- MiMo-V2.6-Flash-RL vs Qwen3.6-35B-A3B
- MiMo-V2.6-Flash-RL vs Qwen3.8-27B
- MiMo-V2.6-Flash-RL vs Qwen3.8-Flash-Next
- MiMo-V2.6-Flash-RL vs Qwen3-Coder-30B-A3B-Instruct
- MiMo-V2.6-Flash-RL vs Qwen3-Coder-Next
- MiMo-V2.6-Flash-RL vs Qwen3-Omni-30B-A3B-Instruct
- MiMo-V2.6-Flash-RL vs Qwen3-VL-2B-Instruct
- MiMo-V2.6-Flash-RL vs Qwen3-VL-30B-A3B-Instruct
- MiMo-V2.6-Flash-RL vs Qwen3-VL-32B-Instruct
- MiMo-V2.6-Flash-RL vs Qwen3-VL-4B-Instruct
- MiMo-V2.6-Flash-RL vs Qwen3-VL-8B-Instruct
- MiMo-V2.6-Flash-RL vs Qwopus3.8-27B-Flash-V2
- MiMo-V2.6-Flash-RL vs Recursive Flint
- MiMo-V2.6-Flash-RL vs Ripple-65B Preview
- MiMo-V2.6-Flash-RL vs SenseNova-Loop-9B-Preview
- MiMo-V2.6-Flash-RL vs SmolLM3-3B
- MiMo-V2.6-Flash-RL vs Spark-X2.6-4B
- MiMo-V2.6-Flash-RL vs Step 3.7 Flash
- MiMo-V2.6-Flash-RL vs Swift 1.5 Qwen3.8-27B
- MiMo-V2.6-Flash-RL vs Swift 1.5 Qwen3.8-Flash-Next
- MiMo-V2.6-Flash-RL vs ThinkingCap (Qwen3.8 27B)
- MiMo-V2.6-Flash-RL vs Baidu Unlimited-OCR-2
- MiMo-V2.6-Flash-RL vs WeVisOne-VL-2B
- MiMo-V2.6-Flash-RL vs WeVisOne-VL-4B
- MiMo-V2.6-Flash-RL vs ZAYA1-8B
Machine-readable
- This page as Markdown
/compare/kolibri-1-vs-mimo-v2-6-flash-rl.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/kolibri-1.json·/api/v1/tools/mimo-v2-6-flash-rl.json - From a terminal
anchor compare kolibri-1 mimo-v2-6-flash-rl(the CLI) - Over MCP
compare_tools {"a": "kolibri-1", "b": "mimo-v2-6-flash-rl"}at/mcp, no key