# DepTime (pypi · deptime)

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

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `deptime`: 70/100 (this document), [markdown](https://verifymcp.io/servers/cschmertz-deptime/deptime.md), [page](https://verifymcp.io/servers/cschmertz-deptime/deptime)

## Channel facts

- Registry: `pypi`
- Package: `deptime`
- Version: `0.1.5`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 2 of 36 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to cschmertz/deptime).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 926 tokens (~185/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the DepTime MCP server?

DepTime runs locally as a PyPI package, launched with uvx deptime mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cschmertz-deptime -- uvx deptime mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cschmertz-deptime": {
      "command": "uvx",
      "args": [
        "deptime",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cschmertz-deptime": {
      "command": "uvx",
      "args": [
        "deptime",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cschmertz-deptime -- uvx deptime mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cschmertz-deptime": {
      "type": "local",
      "command": [
        "uvx",
        "deptime",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cschmertz-deptime --command uvx --arg deptime --arg mcp
```

### Hermes

```yaml
mcp_servers:
  cschmertz-deptime:
    command: "uvx"
    args: ["deptime", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cschmertz-deptime": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "deptime",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cschmertz-deptime -t stdio -c uvx -a deptime mcp
```

### Other

```json
{
  "mcpServers": {
    "cschmertz-deptime": {
      "command": "uvx",
      "args": [
        "deptime",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 70, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.1.4 → 0.1.5

### 2026-11-03 (score 84, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 68, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-01 (score 83, +16)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.10 → unverified
- [security improvement] Malware scan: unverified → pass
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.1.3 → 0.1.4

### 2026-10-31 (score 67, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-30 (score 82, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-29 (score 66, +1)

- [security improvement] Malware scan: unverified → pass
- [functional regression] Schema quality: 133 → 185
- [functional improvement] Tool coverage: 57% → 100%
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → excellent
- [functional] Package version: 0.1.2 → 0.1.3

### 2026-10-28 (score 65)

First indexed and scored.

## MCP tools (5)

### `explain_error` (~195 tokens)

Explain a Python import/attribute/signature error

Call this when a third-party Python library raises ImportError ('cannot import name'), ModuleNotFoundError, AttributeError ('has no attribute'), or TypeError ('unexpected keyword argument' / 'missing required argument'). Returns what changed, in which release, the deprecation message, replacement candidates with evidence, and the version pin that restores the old API. Pass installed versions for an exact answer. An error DepTime can't explain returns empty findings rather than a guess; check `note` and `not_covered`.

Input parameters:

- `installed_versions`: Installed versions, e.g. {"httpx": "0.28.1"}.
- `pip_freeze`: Output of `pip freeze` / `uv pip freeze` / `pip list`.
- `traceback` (string, required): Traceback text, or at least the final 'SomeError: message' line. Long logs are fine: only the last 20,000 characters are analysed.

Output parameters:

- `findings` (array)
- `not_covered` (array): Packages involved in the error that DepTime does not index.
- `note`
- `signal`

### `symbol_history` (~132 tokens)

Version history of one symbol

Version history of one public symbol, e.g. package='httpx', path='httpx.Client.__init__': first and last release it exists in, signature changes, deprecations, removals, and replacement candidates. Use before writing code against an API you remember from training data. A path no indexed release has is not an error: it returns ever_seen=false. For many symbols at one installed version, use check_symbols.

Input parameters:

- `package` (string, required): PyPI distribution name, e.g. 'langchain-core'.
- `path` (string, required): Public dotted path; the package prefix may be omitted.

Output parameters:

- `events` (array)
- `ever_seen` (boolean): False means no indexed version ever exposed this public path.
- `first_seen`
- `indexed` (boolean): False when the package is not in DepTime's coverage; see the `coverage` tool.
- `last_seen`
- `latest_indexed_version`
- `note`
- `package` (string)
- `path` (string)
- `present_in_latest` (boolean)
- `replacements` (array)
- `signature_at_last_seen`

### `check_symbols` (~143 tokens)

Check symbols and kwargs against an installed version

Batch-check that symbols, and the keyword arguments you plan to pass, exist in a specific version of a package. Returns present/missing per symbol, rejected kwargs, deprecation notes, and hints. Use it to preflight code against the version you have installed; for one symbol across all releases use symbol_history, and after an exception use explain_error.

Input parameters:

- `package` (string, required): PyPI distribution name, e.g. 'langchain-core'.
- `symbols` (array, required): Up to 100 symbols, each a public dotted path plus the keyword arguments you plan to pass.
- `version` (string, required): Installed version, e.g. '0.28.1'.

Output parameters:

- `exact` (boolean)
- `note`
- `package` (string)
- `requested_version` (string)
- `resolved_version`: Nearest indexed version <= requested_version.
- `results` (array)

### `diff_versions` (~210 tokens)

Breaking changes between versions

Breaking changes and deprecations of a package between two versions, or since a date such as your training cutoff ('YYYY-MM-DD'). Optionally restrict to the symbols your code uses. Most severe first. Use it when upgrading, or for code written against an older release; for a single symbol use symbol_history.

Input parameters:

- `from_version` (string, required): Version, or a date 'YYYY-MM-DD' (nearest release on/before).
- `include_added` (boolean): Also list symbols added in the range. Off by default: breaking changes and deprecations only.
- `limit` (integer): Maximum events to return (1-500), most severe first; `truncated` is true when more exist.
- `package` (string, required): PyPI distribution name, e.g. 'langchain-core'.
- `to_version`: Defaults to the latest indexed release.
- `used_symbols`: Public dotted paths your code uses (up to 500); only changes on these paths or their members are returned.

Output parameters:

- `events` (array)
- `from_version`
- `note`
- `package` (string)
- `to_version`
- `truncated` (boolean)

### `coverage` (~42 tokens)

What DepTime indexes

Lists indexed packages and version ranges. If a package is missing, DepTime cannot answer about it. Takes no arguments; call it first when unsure whether a package is covered.

Output parameters:

- `configured_but_not_indexed` (array)
- `index_built_at`
- `packages` (array)
- `policy` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/cschmertz-deptime/deptime#diagnostics

## Score history

- 2026-11-05: 70
- 2026-11-04: 84
- 2026-11-03: 84
- 2026-11-02: 68
- 2026-11-01: 83
- 2026-10-31: 67
- 2026-10-30: 82
- 2026-10-29: 66
- 2026-10-28: 65

## Common questions

### What is the DepTime MCP server?

DepTime is an MCP server listed in the public MCP registry as io.github.cschmertz/deptime. What changed in a Python library, in which release, and what replaces it. Answered locally. This page covers its PyPI package (deptime).

### Is the DepTime MCP server safe to use?

DepTime scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 DepTime MCP server expose?

DepTime exposes 5 tools: explain_error, symbol_history, check_symbols, diff_versions, coverage. Their descriptions and schemas cost roughly 722 tokens of context every time the server is loaded.

### Is the DepTime MCP server still maintained?

DepTime is still listed as active in the MCP registry. We last reached this channel on 5 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 DepTime MCP server under?

DepTime declares the MIT 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 DepTime MCP server?

VerifyMCP ran 15 checks on DepTime, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about DepTime: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/deptime/
- Socket report: https://socket.dev/pypi/package/deptime
- Repository: https://github.com/cschmertz/deptime
- Changelog RSS feed: https://verifymcp.io/servers/cschmertz-deptime/deptime.xml
- Changelog JSON feed: https://verifymcp.io/servers/cschmertz-deptime/deptime/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cschmertz-deptime/deptime.json
- HTML version of this page: https://verifymcp.io/servers/cschmertz-deptime/deptime