MCP servers › io.github.dobo123123 › dobocache
MCP server · registry snapshot 2026-11-16 · last checked 2026-11-16
dobocache MCP server
Registry name io.github.dobo123123/dobocache
by dobo123123 · GitHub account (the registry's namespace rule)repository: same ownerSource ↗npm ↗Website ↗
Stabilizes LLM prompt-cache prefixes so provider caching hits. One command setup, no baseURL edit. — the publisher's description
Summary
io.github.dobo123123/dobocache is a local MCP server listed in the official MCP registry at version 0.9.2, under the namespace of the GitHub account dobo123123. Its linked repository, github.com/dobo123123/dobocache, belongs to the same GitHub account.
Record checks
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- met: Repository publishes a security policy (SECURITY.md)
- met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- met: npm package carries build provenance (attestation)
- met: No known critical or high advisory in the package or its dependencies
- #1,942 of 20,610 packages by monthly downloads, tied with 1 other
- Not ranked by stars: 0 stars (ranked from 10)
- #423 of 1,244 packages meeting all 9 record checks, by downloads
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- local package
- Transport
- standard input/output
- Your own values
- none declared (not a guarantee)
- Package
- npm · listed version current
- License
- Apache-2.0
- Dependencies
- no known high or critical advisories
- Repository
- public
- Last tested
- not tested
Tool list
Not read: It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.
Worth knowing before you connect it
- Its package is signed and carries a build record naming its source.
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- no
- Last tested
- not tested
- Latest version
- 0.9.2, published 2026-11-16 (registry, as of the 2026-11-16 snapshot)
- First listed version
- 2026-11-07 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 9 versions listed, 2026-11-07 to 2026-11-16; 9 in the 90 days before the 2026-11-16 snapshot.(versions still listed in the registry only)
Most recent 9 versions
0.9.2· 2026-11-160.9.1· 2026-11-160.8.0· 2026-11-160.6.1· 2026-11-150.6.0· 2026-11-140.5.2· 2026-11-130.5.1· 2026-11-130.5.0· 2026-11-130.4.9· 2026-11-07
- Registry data
- snapshot 2026-11-16
- Package and repository
- checked 2026-11-16
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
Version 0.6.1 (published 2026-11-15) → 0.9.2 (published 2026-11-16), between the registry lists of 2026-11-15 and 2026-11-16.
The publisher’s GitHub release note for v0.9.2 (“DoboCache v0.9.2 - v0.9.1 的发布收口版:内容同 v0.9.1,含 CI runner 修复”), published 2026-11-16.
Read the release note (the publisher’s text, shown as plain text, cut at 4,000 characters)
# DoboCache v0.9.2 — v0.9.1 的发布收口版:内容同 v0.9.1,补入 CI runner 修复
> 这一版没有新功能,只做一件事:**把 v0.9.1 真正发对**。
> v0.9.1 发布时,tag、npm 包与 Release 资产指向的是修复前的提交(`a263632`),其中不含 `macos-15-intel` runner 修复与随后的文档口径同步;真实交付提交是 `789a4a5`。
> npm 已发布版本不可覆盖,为保证「一个版本号只对应一份内容」,改发 v0.9.2。**v0.9.1 的 Release 与 npm 包保留可查,请以本版为准。**
## 本版包含
**v0.9.1 的全部内容:**
- **逐项验证台账**:13 项内置适配(内置 10 + 老三家 3)每一项都记验证等级、复核日期、证据原文,台账是唯一口径,描述符与 CLI 都从它取。
- **三级验证等级**:
- `client-confirmed` — 真实客户端自己认过这条接入(4 家);
- `write-rollback` — 写入 → 真解析器校验语法 → 按真实字段校验条目 → 回滚 → 与接入前逐字节比对,全跑通,但没在这台机器上把该客户端跑起来(8 家);
- `docs-only` — 配置格式无法安全代写,只输出手填指引,永不写盘(1 家)。
- **可复算矩阵脚本**(`npm run ci:hosts-matrix`):在沙箱目录内对 13 项逐个跑完整链路,产出矩阵文档,退出码 0 = 13 项全 PASS,**不触碰用户真实配置**。
- **修复 `--revert` 退不回上游 baseURL(真实缺陷)**:原实现写在盘后才读「接入前的 baseURL」,读到的是自家代理地址,回滚判断直接跳过,用户原来的上游地址再也退不回去。现改为**写盘前**取原值,并记录「接入前到底有没有这个键」,回滚按「复原原值 / 清空 / 删除我们加的键」三态处理。
**额外补入(v0.9.1 的包缺失的部分):**
- `ci: replace retired macos-13 runner with macos-15-intel` — GitHub 已于 2025-12-04 退役 macOS 13 镜像,无机器接单的 job 只会排队到 24 小时被取消;改用官方最后一个 Intel 镜像 `macos-15-intel`(支持到 2027 年秋)。
## 测试
- 单测 **155 例全通过**(6 个文件)。
- `npm run ci:hosts-matrix`:13 项 **PASS 13 / FAIL 0**,退出码 0。
- `npm run ci-mcp-smoke`:9 工具全部 PASS,握手实测 `serverInfo={"name":"dobocache","version":"0.9.2"}`,`tools/list` 数量 9。
- `npm run check:docs`:**0 ERROR**。
- GitHub Actions:在 `ubuntu-latest` / `windows-latest` / `macos-latest` / `macos-15-intel` 四个 runner 上全部通过。
## 口径(不承诺)
- `write-rollback` 证明的是「写进去合法、条目字段正确、能原样退回」,**不等于**该客户端在你机器上一定加载成功——要客户端自己认,才叫 `client-confirmed`;
- 矩阵只在 Windows 11 真机复算过,Linux / macOS 未跑矩阵;
- 「13 项」指本仓库内置描述符 + 老三家的适配范围,**不等于**「这 13 家都做过端到端真机验证」。
## 附件
- `dobocache-v0.9.2-portable.zip` — 含 `dist`、`src`、启动脚本与校验清单;代理形态零外部依赖,解压双击即可跑。
- 大小:7,094,843 字节(3850 个文件)
- SHA256:`0894DFD7A53EAA709572AAF5CA1D8F78978C4140A7A7B31EE2941740320B8B28`
- MD5:`9DB701B0ABD5187F456D675B9097D4C1`
## 安装
```bash
npx -y dobocache@0.9.2 dobostitch setup
```
MCP 客户端手动挂载:
```json
{
"mcpServers": {
"dobocache": {
"command": "npx",
"args": ["-y", "dobocache@0.9.2"]
}
}
}
```
查看自己这台机器上 13 项各自的结论:
```bash
npx -y dobocache@0.9.2 providers list
```
---
# English
## DoboCache v0.9.2 — release hygiene for v0.9.1 (same content, plus the CI runner fix)
No new features. This release exists to ship v0.9.1 **correctly**.
When v0.9.1 was published, its tag, npm package and Release asset pointed at the pre-fix commit `a263632`, which did not include the `macos-15-intel` runner fix and the follow-up docs sync; the actual delivery commit was `789a4a5`. npm versions cannot be overwritten, so v0.9.2 carries identical content plus that fix, keeping "one version = one content". **The v0.9.1 Release and npm package stay online for reference; use this release.**
**What's inside**
- Per-target verification ledger for all 13 built-in targets (level, review date, evidence), used as the single source of truth by descriptors and CLI.
- Three verification levels: `client-confirmed` (4), `write-rollback` (8), `docs-only` (1, never writes to disk).
- Recomputation script (`npm run ci:hosts-matrix`) that runs all 13 targets in a sandbox — never touches real user configs.
- Fix: `--revert` could not restore the upstream baseURL (the pre-write value was read after the write). It is now captured before writing, with `hadBaseURL` recorded so rollback handles "restore / clear / delete the key we added".
- CI: macOS 13 runners were retired on 2025-12-04; switched to the official `macos-15-intel` label (last Intel image, supported through autumn 2027).
**Tests**: 155 unit tests pass; 13/13 targets PASS; MCP smoke handshake reports `serverInfo={"name":"dobocache","version":"0.9.2"}` with 9 tools; docs consistency check 0 errors; green on ubuntu-latest / windows-latest / macos-latest / macos-15-intel.
**Scope**: `write-rollback` means "writes valid content, correct entry fields, reverts byte-identically" — it does not mean the client will load it on your machine. The matrix was only recomSource: the official MCP Registry list on 2026-11-15 and on 2026-11-16; release notes from the GitHub Releases API, checked 2026-11-16.
What it is
How do I add it to my client?
Config from the registry entry
- No config: the npm package names the runner "node", not npx.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 0.9.2
- Latest stable
- 0.9.2
- Status
- current
- Withdrawn
- no
Source: registry.npmjs.org · 2026-11-16. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-11-16 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha512-vPaBOoFEYsioNB+Hg…
- Signature
- signed and attested
- License
- Apache-2.0
Source: the package registry · 2026-11-16.
Usage
- Downloads
- 1,769 in the last month
Source: api.npmjs.org · 2026-11-16.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- Install-time script (npm). No install-time script in the published package.json (version 0.9.2). Source: registry.npmjs.org/dobocache/0.9.2 · read 2026-11-16.
- Operating systems and processors (npm). The npm package sets no os or cpu limit (package.json). Source: registry.npmjs.org/dobocache/0.9.2 · read 2026-11-16.
- Node.js version (npm). Needs Node 18 or later (engines.node
>=18.0.0). Source: registry.npmjs.org/dobocache/0.9.2 · read 2026-11-16. - MCP SDK in the package files. Lists
@modelcontextprotocol/sdkas a dependency (package.json). Source: registry.npmjs.org/dobocache/-/dobocache-0.9.2.tgz · read 2026-11-16. - Build workflow. Built and published by GitHub Actions workflow
.github/workflows/publish.ymlinhttps://github.com/dobo123123/dobocache(npm provenance). Source: read 2026-11-16.
Registry entry
- Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-16.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-16. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-16. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-16. Source: read 2026-11-16.
- Cline marketplace. Not in the Cline marketplace on 2026-11-16. Source: read 2026-11-16.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Version 0.9.2 on npm | Exists and can be installed | matches | npm · 2026-11-16 |
| Repository github.com/dobo123123/dobocache | Opens publicly | matches | api.github.com · 2026-11-16 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.dobo123123
- GitHub owner
- a personal account (dobo123123)
- Build record
- signed and attested
- Repository
- github.com/dobo123123/dobocache
- Stars
- 0
- Repository age
- 0–30 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- SECURITY.md
Source: the registry entry and api.github.com · 2026-11-16; security policy read from GitHub · 2026-11-08.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating9 of 9 record checks met
- #1,942 of 20,610 packages by monthly downloads, tied with 1 other
- Not ranked by stars: 0 stars (ranked from 10)
- #423 of 1,244 packages meeting all 9 record checks, by downloads
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
- MetPackage names its licence with a standard (SPDX) identifierApache-2.0
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
- Metnpm package carries build provenance (attestation)Signed, with a build attestation naming the source and workflow.
- MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-16 (security policy 2026-11-08). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about io.github.dobo123123/dobocache
Answered from the data aboveWho publishes io.github.dobo123123/dobocache?
The registry ties the namespace io.github.dobo123123 to the GitHub account dobo123123; only its owner can publish under it. Its linked repository, github.com/dobo123123/dobocache, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.dobo123123/dobocache safe to install?
We do not rate servers as safe or unsafe. 9 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its npm package carries a build-provenance attestation that names its source repository and build workflow. Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has io.github.dobo123123/dobocache been security tested?
No. It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's.
Does io.github.dobo123123/dobocache publish a security policy?
Yes: its repository has a public security policy (github.com/dobo123123/dobocache/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.
Is the listed version current?
Yes. The registry lists 0.9.2, the latest stable release on npm.
Where is the source code of io.github.dobo123123/dobocache?
In github.com/dobo123123/dobocache, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
Has it been tested?
Feature #1It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. — our limit
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.dobo123123/dobocache: MCP server record.” Data checked 2026-11-16. https://protocolprobe.com/mcp/servers/io.github.dobo123123/dobocache
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.dobo123123/dobocache)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology