DoboCache
NPM · DOBOCACHE
Stabilizes LLM prompt-cache prefixes so provider caching hits. One command setup, no baseURL edit.
Available components
Last scanned (19 hours ago)
Scores higher than 73% of npm servers
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to dobo123123/dobocache). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 4 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3096 tokens (~344/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management36
- Stability check failed: the tool surface changed between 0.4.9 and 0.9.2: 1 tool removals, 0 breaking changes, 1 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 29 to 32.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 22 to 26.
- 17 Nov 26 +10
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- 16 Nov 26 −10
- Stability: fail → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Dependency health: 0.85 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.6.1 → 0.9.2 functional
- Package version: 0.6.1 → 0.9.1 functional
- Package version: 0.6.1 → 0.8.0 functional
- 15 Nov 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- Package version: 0.6.0 → 0.6.1 functional
- 14 Nov 26 0
- Stability: 0.20 → fail ▼ security
- Known CVEs: unverified → pass ▲ security
- Schema quality: 285 → 344 ▼ functional
- Dependency health: unverified → 0.85 ▲ functional
- Schema quality: good → excellent functional
- Package version: 0.5.2 → 0.6.0 functional
- 13 Nov 26 −7
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Dependency health: 0.85 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.20 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.4.9 → 0.5.2 functional
- Package version: 0.4.9 → 0.5.1 functional
- Package version: 0.4.9 → 0.5.0 functional
- 8 Nov 26 +15
- Malware scan: unverified → pass ▲ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/dobocache@0.9.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | dobo123123/dobocache |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/dobo123123/dobocache/.github/workflows/publish.yml@refs/tags/v0.9.2 |
| Rekor log index | 3921000629 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:bcf6813a814462c8a8341f8780b82849f861121e98303bd0f4d6509ec427145b41fca45b69b159fde1e542219abe41891fdd08d81b186e72b267f984e |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cf_inject ~725
会话增量注入:固定版本化前缀(规则块+分级片段+固定补充块)逐字节不变,新内容(本次请求+易变内容)只追加到尾部 tail;同一 sessionId 自动冻结前缀支持跨请求复用;前缀不足最小有效长度时自动补高价值片段/固定文档块过门槛。【何时调】发请求前需要稳定前缀时:同一会话首次 reset=true,之后同一 sessionId 增量追加;短对话、一次性提问不必调用。
| Name | Type | Req | Description |
|---|---|---|---|
| align128 | boolean | – | 128-token 对齐开关(默认开启;false 恢复原行为) |
| alignFillText | string | – | 128 对齐填充块(默认固定 ASCII 注释块) |
| fragments | array | yes | 已分级准入片段(首次请求时冻结,后续请求复用) |
| freezeFragments | boolean | – | 是否冻结片段用于跨请求前缀复用(v0.4.2,默认 true;false 时冷启动不锁死占位片段,允许随请求重建前缀) |
| hitTokens | integer | – | 本次请求的厂商 usage 命中 tokens(prompt_cache_hit_tokens),供 cf_meter 计费相对值曲线累计;必须 ≥ 0 |
| maxTokens | integer | – | 注入后 token 上限;必须为 ≥ 1 的整数(不传则用内置默认值) |
| minPrefixDocBlocks | array | – | 过门槛用的固定版本文档块 |
| minPrefixSafetyFactor | number | – | 最小前缀门槛安全余量(v0.4.2,默认 1.15):实际门槛 = ceil(minPrefixTokens × factor);必须 ≥ 1(< 1 会让门槛低于厂商最小值,缓存必然不生效) |
| minPrefixTokens | integer | – | 最小有效前缀长度门槛(token),默认 200;必须 ≥ 0 |
| missTokens | integer | – | 本次请求的厂商 usage 未命中 tokens(prompt_cache_miss_tokens),供 cf_meter 计费相对值曲线累计;必须 ≥ 0 |
| previousPrefixHash | string | – | 上一次请求返回的 prefixHash;一致则标记前缀复用(兼容无冻结信息场景) |
| request | string | yes | 当前请求文本(动态增量 tail) |
| reset | boolean | – | 重置该会话冻结前缀,重新冻结 |
| scenario | string | – | 显式指定约束场景(默认按缓存充足度自动选择) |
| sessionId | string | – | 会话标识;同一会话冻结前缀,跨请求复用 |
| strictness | string | – | 约束强度(v0.4.2):strict 完整硬约束(默认)/ balanced 平衡(允许自身知识补充并标注)/ loose 自由放行;仅影响 full 场景;同一会话冻结后以冻结值为准 |
| volatile | array | – | 显式易变内容(时间戳/会话标记等),强制进 tail |
No output schema declared.
No examples provided.
cf_judge ~317
判定当前请求能否命中既有缓存上下文:关键词分层(实体锚词/意图修饰词)、三层匹配、时效衰减、负向过滤,输出可解释证据。【何时调】要判断「这段历史/记忆值不值得复用、能不能命中」时,在 cf_inject 之前调一次;不要每轮都调。
| Name | Type | Req | Description |
|---|---|---|---|
| blacklist | array | – | 黑名单词,支持 /regex/ 形式 |
| entries | array | yes | 缓存条目列表(记忆/历史对话) |
| hitTokens | integer | – | 本次请求厂商 usage 命中 tokens(prompt_cache_hit_tokens),供 cf_meter 计费相对值曲线累计;必须 ≥ 0 |
| missTokens | integer | – | 本次请求厂商 usage 未命中 tokens(prompt_cache_miss_tokens),供 cf_meter 计费相对值曲线累计;必须 ≥ 0 |
| now | integer | – | 用于测试的当前时间戳(毫秒),必须 ≥ 0 |
| query | string | yes | 当前请求文本(不能为空:空文本无实体锚词,判定结果恒为未命中) |
| threshold | number | – | 命中阈值,默认 5;必须 ≥ 0 |
| topK | integer | – | 返回候选数,默认 5;必须为 ≥ 1 的整数 |
No output schema declared.
No examples provided.
cf_meter ~198
输出测量仪表快照:判定命中率、平均分、价值分级分布、预计命中 token/比例;v0.2.1 新增按请求累计计费相对值曲线(累计命中/未命中 tokens)。注意:此处的 hitRate 是「cf_judge 判定命中率」(DoboCache 内部召回判定口径),且无判定样本时为 null(未判定,勿读作 0%);厂商 usage 回传的真实缓存命中率请看 cf_report 的 hitRate / judgedCalls。【何时调】用户问「当前判定/召回质量」时;问「真实缓存命中多少」请改用 cf_report(读落盘日志、跨进程累计)。
| Name | Type | Req | Description |
|---|---|---|---|
| reset | boolean | – | 是否清空计数器后输出空快照 |
No output schema declared.
No examples provided.
cf_normalize ~186
归一化结构化行数据(对象数组):按字段白名单裁剪 + 稳定排序,让内容相同但顺序抖动的返回归为同一个缓存键,输出归一后的 rows 与 `nk-` 前缀键指纹。与 cf_prune 的分工:cf_normalize 吃 rows 数组、产出稳定键;cf_prune 吃纯文本、产出短文本。【何时调】同类工具多次返回、内容相同但字段顺序抖动导致缓存键反复失效时调一次,把顺序固定下来。
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | 保留字段白名单;不传则保留全部字段 |
| rows | array | yes | 结构化行数据(对象数组),排序依据字段名而非原始行序 |
No output schema declared.
No examples provided.
cf_ping ~118
连通性自检(最先调这个):返回 pong: dobocache ready 表示 MCP 服务已正常加载;同时探测代理端口并给出结构化结论——proxy: listening 表示改写链路在跑,refused 表示代理没起(此时请求不会被改写),listening_other 表示端口被别的程序占用,timeout 表示代理卡住。用户说「没反应 / 没效果 / 不生效」时先调它定位。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cf_prune ~254
压缩你传入的文本,为稳定前缀腾出空间:去重行、压缩空白,按 maxChars / maxLines 双上限截断(默认保留头部),返回修剪前后体积比与丢弃行数。输入只认参数里的 text 字符串,输出是可直接拼进上下文的短文本;【何时调】工具输出很长、要压进上下文又不想破坏前缀稳定性时。要处理结构化行数据用 cf_normalize。白盒日志由服务端自维护(单文件 10MB 轮转、默认保留 7 天,`DOBOCACHE_LOG_MAX_MB` / `DOBOCACHE_LOG_KEEP_DAYS` 可调),体积无需人工干预。
| Name | Type | Req | Description |
|---|---|---|---|
| keepHead | boolean | – | 保留头部(默认 true) |
| maxChars | integer | – | 最大字符数,默认 2000;必须为 ≥ 1 的整数 |
| maxLines | integer | – | 最大行数,默认 200;必须为 ≥ 1 的整数 |
| text | string | yes | 原始工具输出 |
No output schema declared.
No examples provided.
cf_report ~460
历史报表:从本地白盒日志汇总请求次数、厂商 usage 真实缓存命中率、原始/优化 token、预计命中 token 与命中比例,【何时调】任务收尾、或用户问「缓存效果怎么样/命中多少」时调一次即可(读落盘日志,跨进程跨天累计,重启不丢);不要每轮轮询。支持 total / per_session 聚合,附带 cardMode(白盒卡片档位,默认 quiet)。与 cf_meter 的分工:cf_report 读落盘日志,可跨进程、跨天累计(source=disk,进程重启不丢);cf_meter 只报当前进程内即时快照。命中率为 null 表示本期没有可判定的厂商 usage 数据(未判定),不是 0%。日志默认写平台标准可写目录(`DOBOCACHE_LOG_DIR` 可覆盖),只在本机、不含提问原文、不占对话 token;按「单文件 10MB 轮转 + 默认保留 7 天」自动维护(`DOBOCACHE_LOG_MAX_MB` / `DOBOCACHE_LOG_KEEP_DAYS` 可调),返回中的 logPolicy 即当前生效值。
| Name | Type | Req | Description |
|---|---|---|---|
| aggregateBy | string | – | 聚合维度(v0.4.2,默认 total):total=进程内累计;per_session=按会话分组) |
| days | integer | – | source=disk 时回溯的自然日数(v0.4.7,默认等于日志保留天数,通常 7 天) |
| reset | boolean | – | 是否清空累计计数后输出空统计 |
| source | string | – | 统计来源(v0.4.7,默认 memory):memory=当前进程内累计,进程重启即从 0 开始;disk=读取本地白盒日志重新聚合,跨进程/跨天累计,适合回答「累计到底省了多少」。disk 为纯本地只读,不联网、不上报。 |
No output schema declared.
No examples provided.
cf_tier ~240
对候选记忆/上下文片段做价值分级准入:提纯去噪 → A/B/C 分级 → 按预算从高到低填充,输出准入列表与丢弃明细。【何时调】候选片段超出预算、需要决定「留哪些、丢哪些」时;片段很少(不足 5 条)可直接注入,不必先分级。
| Name | Type | Req | Description |
|---|---|---|---|
| fragments | array | yes | 候选片段列表 |
| now | integer | – | 用于测试的当前时间戳(毫秒),必须 ≥ 0 |
| query | string | – | 用于评分的当前请求 |
| reservedChars | integer | – | 预留前缀字符数,默认 250;必须 ≥ 0,且不应大于 totalChars(否则预算被预留吃光,什么都不会被准入) |
| totalChars | integer | – | 总预算(字符),默认 800;必须 ≥ 0(填 0 表示不赋予预算,全部片段都会被丢弃) |
No output schema declared.
No examples provided.
cf_warmup ~293
预热工具(v0.2.1):在正式请求前显式调用一次,用当前冻结前缀(sessionId)或传入片段构造最小占位请求;客户端需将返回的 prompt 发一次 LLM 请求以触发厂商前缀缓存建立。注意:必须显式调用、默认不自动触发;该占位请求本身会产生少量计费(按未命中计价系数);命中率无法由 server 侧确认,请以下一次请求的 usage 为准。【何时调】确认紧接着会有一次长上下文请求、想先把厂商缓存建立起来时;日常短任务不要调(占位请求本身也要计费)。
| Name | Type | Req | Description |
|---|---|---|---|
| align128 | boolean | – | 128-token 对齐开关(默认开启) |
| fragments | array | – | 无冻结前缀时用于构造候选前缀的分级片段 |
| minPrefixTokens | integer | – | 最小有效前缀长度门槛(token),默认 200;必须 ≥ 0 |
| request | string | – | 占位请求文本(默认固定占位符) |
| sessionId | string | – | 会话标识;存在冻结前缀时基于冻结前缀构造占位请求 |
No output schema declared.
No examples provided.
How do I install the DoboCache MCP server?
DoboCache runs locally as an npm package, launched with npx -y dobocache. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · dobocache
claude mcp add dobo123123-dobocache -- npx -y dobocache
What is the DoboCache MCP server?
DoboCache is an MCP server listed in the public MCP registry as io.github.dobo123123/dobocache. Stabilizes LLM prompt-cache prefixes so provider caching hits. One command setup, no baseURL edit. This page covers its npm package (dobocache).
Is the DoboCache MCP server safe to use?
DoboCache scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the DoboCache MCP server expose?
DoboCache exposes 9 tools: cf_ping, cf_judge, cf_tier, cf_inject, cf_meter, and 4 more. Their descriptions and schemas cost roughly 2,791 tokens of context every time the server is loaded.
Is the DoboCache MCP server still maintained?
DoboCache is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the DoboCache MCP server under?
DoboCache declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the DoboCache MCP server?
VerifyMCP ran 16 checks on DoboCache, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.