DepTime
PYPI · DEPTIME
What changed in a Python library, in which release, and what replaces it. Answered locally.
Available components
Last scanned (11 hours ago)
Scores higher than 88% of PyPI servers
Category Developer Tools
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 2 of 36 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 cschmertz/deptime). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +16
- Tool safety: pass → unverified ▼ security
- Stability: 0.10 → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.3 → 0.1.4 functional
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 +1
- Malware scan: unverified → pass ▲ security
- Schema quality: 133 → 185 ▼ functional
- Tool coverage: 57% → 100% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- Package version: 0.1.2 → 0.1.3 functional
- 28 Oct 26 65
First indexed and scored.
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 5 Nov 2026 · Analysed pypi/deptime@0.1.4
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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | cschmertz/deptime |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/cschmertz/deptime/.github/workflows/release.yml@refs/tags/v0.1.4 |
| Rekor log index | 3635670050 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:8b08de277fbd70ac8a8379213fc3a6842c6b92727cbbe671334dfd040fa66d9c |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 36 packages
| Packages resolved | 36 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| 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 →
check_symbols Check symbols and kwargs against an installed version ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | yes | PyPI distribution name, e.g. 'langchain-core'. |
| symbols | array | yes | Up to 100 symbols, each a public dotted path plus the keyword arguments you plan to pass. |
| version | string | yes | Installed version, e.g. '0.28.1'. |
| Name | Type | Req | Description |
|---|---|---|---|
| exact | boolean | yes | – |
| note | – | – | – |
| package | string | yes | – |
| requested_version | string | yes | – |
| resolved_version | – | yes | Nearest indexed version <= requested_version. |
| results | array | yes | – |
No examples provided.
coverage What DepTime indexes ~42
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| configured_but_not_indexed | array | – | – |
| index_built_at | – | yes | – |
| packages | array | yes | – |
| policy | string | yes | – |
No examples provided.
diff_versions Breaking changes between versions ~210
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from_version | string | yes | 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | yes | – |
| from_version | – | yes | – |
| note | – | – | – |
| package | string | yes | – |
| to_version | – | yes | – |
| truncated | boolean | – | – |
No examples provided.
explain_error Explain a Python import/attribute/signature error ~195
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| installed_versions | – | – | Installed versions, e.g. {"httpx": "0.28.1"}. |
| pip_freeze | – | – | Output of `pip freeze` / `uv pip freeze` / `pip list`. |
| traceback | string | yes | Traceback text, or at least the final 'SomeError: message' line. Long logs are fine: only the last 20,000 characters are analysed. |
| Name | Type | Req | Description |
|---|---|---|---|
| findings | array | yes | – |
| not_covered | array | – | Packages involved in the error that DepTime does not index. |
| note | – | – | – |
| signal | – | yes | – |
No examples provided.
symbol_history Version history of one symbol ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | yes | PyPI distribution name, e.g. 'langchain-core'. |
| path | string | yes | Public dotted path; the package prefix may be omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | – | – |
| ever_seen | boolean | – | False means no indexed version ever exposed this public path. |
| first_seen | – | – | – |
| indexed | boolean | yes | False when the package is not in DepTime's coverage; see the `coverage` tool. |
| last_seen | – | – | – |
| latest_indexed_version | – | – | – |
| note | – | – | – |
| package | string | yes | – |
| path | string | yes | – |
| present_in_latest | boolean | – | – |
| replacements | array | – | – |
| signature_at_last_seen | – | – | – |
No examples provided.
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.
pypi · deptime
claude mcp add cschmertz-deptime -- uvx deptime mcp
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 85 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 16 checks on DepTime, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.