DepTime

Name: DepTime
Author: cschmertz

作者：cschmertz版本 0.1.7i★ –i在你的电脑上运行

注册名称io.github.cschmertz/deptime

安装

概览

作者提供的说明（英文原文）

What changed in a Python library, in which release, and what replaces it. Answered locally.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： DEPTIME_OFFLINE, DEPTIME_HOME

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "deptime": {
      "command": "uvx",
      "args": [
        "deptime",
        "mcp"
      ],
      "env": {
        "DEPTIME_OFFLINE": "your-value",
        "DEPTIME_HOME": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add deptime --env DEPTIME_OFFLINE=your-value --env DEPTIME_HOME=your-value -- uvx deptime mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "deptime": {
      "command": "uvx",
      "args": [
        "deptime",
        "mcp"
      ],
      "env": {
        "DEPTIME_OFFLINE": "your-value",
        "DEPTIME_HOME": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "deptime": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "deptime",
        "mcp"
      ],
      "env": {
        "DEPTIME_OFFLINE": "your-value",
        "DEPTIME_HOME": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

DEPTIME_OFFLINE env
Set to 1 to never touch the network: no index download and no daily update check.
DEPTIME_HOME env
Where the index is stored. Defaults to ~/.cache/deptime.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 cschmertz 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32684 个服务器的 0%
发布到注册中心的时间比此分类中其他 32684 个服务器的 99% 更新
基础检查结果等于或优于此分类中其他 32684 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

DepTime 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.7）于今天进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Master CSS

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211前天更新

安装

Master CSS

作者：master-co

Inspect Master CSS classes, generated CSS, and project stylesheets from your AI client.

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

An API time machine for Python libraries, built for coding agents.

When an agent hits ImportError, AttributeError or "unexpected keyword argument" in a fast-moving library, one call to DepTime says what changed, in which release, and what to use instead. Answers are computed from static diffs of every indexed release, not from docs or model memory.

Free, open source (MIT), and local: your code and errors never leave your machine.

Every night, GitHub Actions reads each new release's public API with griffe, which parses the source without running it, diffs it against the previous release, and publishes the result as one file, index.sqlite.xz, on this repo's Releases. On your machine, deptime mcp checks that file's sha256 and schema before swapping it in, then answers every question locally in milliseconds. The full design is in docs/04-architecture.md, and the decisions are in docs/adr/.

TypeError: Client.__init__() got an unexpected keyword argument 'proxies'

"symbol": "httpx.Client.init(proxies)", "issue": "param_removed", "installed_version": "0.28.1", "last_version_with": "0.27.2", "first_version_without": "0.28.0", "deprecated_in": "0.26.0", "replacements": [ {"target": "proxy", "confidence": 0.8, "source": "deprecation_message"}, {"target": "mounts", "confidence": 0.79, "source": "deprecation_message"} ], "pin_to_restore": "httpx<=0.27.2", "confidence": "high" }

That's the real explain_error answer from the published index, trimmed. The full answer also quotes the deprecation message DepTime found in httpx's own source, and adds a one-sentence explanation for your agent to pass on.

Status: alpha. The prebuilt index is rebuilt twice a day. Known gaps are tracked in BACKLOG.md.

How well it works

Each check's right answers were written down before DepTime first ran on it (bench/). Judge DepTime by the first run: the fixes since then were designed from its misses, so the later numbers are flattering.

Check	Cases	First run	Now
Right package, name and breaking release for a traceback from a GitHub issue	32 collected 2026-11-05	68.8%	96.9%
The same, on a holdout fixed in advance from TimeMachine-bench	29	72.4%	93.1%
Error kind and package read from the traceback: scripts, pytest, chained exceptions, `ExceptionGroup`, IPython, Python 3.10–3.14	736, holdout fixed in advance	93.8%	93.8%
Replacement hints at confidence ≥ 0.75 that are right	hints for 50 documented migrations	11 of 11	42 of 45
Documented migrations that get a right hint at ≥ 0.75	50	11	42 (32 without hand-checked hints from migration guides)
Names that exist at runtime but read as absent	2,428 sampled at runtime from 10 dynamic packages	5.1%	1.2%

Across all 196 real tracebacks in the benchmark, including the ones fixes were designed from, DepTime names the right package, name and release for 98.0%, and a right replacement is among its first three for 68.1%. CI re-scores the 196 and the holdout on every code change and every published index, and fails on a drop of more than 2 points.

Install

Requires uv.

# Claude Code. Cursor, Codex, VS Code and Claude Desktop take the same

command (uvx deptime mcp) in their MCP config.

claude mcp add deptime -- uvx deptime mcp

On first launch DepTime downloads its prebuilt index (one file from this repo's GitHub Releases) in the background, then checks for a newer one at most once a day. Set DEPTIME_OFFLINE=1 to never touch the network.

Claude Code users can also install the plugin in integrations/claude-code with /plugin marketplace add cschmertz/deptime, then /plugin install deptime@deptime. It adds a skill and a local hook that suggests DepTime when a Python version-change error appears in a command's output.

First launch timing out? uvx installs DepTime the first time a client starts it. On macOS with an x86_64 uv (an Intel Mac, or Intel Homebrew on Apple silicon), one dependency, cryptography, has no prebuilt wheel and is compiled, which can take longer than a client waits for a server to start. Run uvx deptime --help once beforehand.

Client compatibility

Checked 2026-11-05 with deptime 0.1.4 (details):

Client	Result
Claude Code 2.1.318	✅
Codex CLI 0.166.0	✅
MCP Python SDK clients 1.0–1.30 and TypeScript SDK clients 1.0–1.32 (protocols 2024-11-05 to 2025-11-25), over stdio and against `deptime serve`	✅
Cursor, VS Code, Claude Desktop	not checked yet; they take the same `uvx deptime mcp` command

Tools

Tool	Use it when
`explain_error(traceback, installed_versions?, pip_freeze?)`	An import or call into a library just failed
`symbol_history(package, path)`	Before trusting an API you remember
`check_symbols(package, version, symbols[{path, kwargs}])`	Pre-flight check of the symbols and kwargs you're about to use
`diff_versions(package, from_version \	date, to_version?, used_symbols?)`	Upgrading, or "what changed since my training cutoff?"
`coverage()`	What's indexed (53 fast-moving packages: AI/agent stack + libraries with known breaking changes)

Every answer carries evidence and a confidence level. If a package isn't covered, DepTime says so instead of guessing. The contracts are in docs/03-product-spec.md.

CLI

uvx deptime explain --installed httpx==0.28.1 < traceback.txt

uvx deptime history httpx Client.init uvx deptime check httpx 0.28.1 'httpx.Client:proxies,proxy' uvx deptime diff httpx 0.27.2 0.28.1 uvx deptime diff pydantic 2024-06-01 # everything since a date uvx deptime index status | pull

Hosting (optional)

Local mode covers coding agents. For web clients that only accept a URL, run deptime serve (MCP at /mcp, JSON at /v1/*) on any container host. The repo includes a Dockerfile and fly.toml, and the server applies anonymous rate limits. See docs/05-self-hosting.md.

Prior art and credits

griffe does the static analysis.
since-cutoff diffs your pinned dependencies against a model's training cutoff, locally and on demand. DepTime differs by shipping a prebuilt cross-version index and starting from a traceback.
Context7 and Ref serve version-specific docs. DepTime answers symbol-level "when and what replaced it" questions.

Contributing

The most useful contributions are wrong-answer reports, which become benchmark cases. See CONTRIBUTING.md. Development setup:

uv sync && uv run pytest

build a small local index from real PyPI wheels

uv run deptime ingest httpx --versions 0.27.2 0.28.1

Docs

Product spec · Architecture · Self-hosting · Risks & spikes · Privacy & security

License

MIT