NeuroDock Chronometric
PYPI · NEURODOCK-MCP-CHRONOMETRIC
Externalises time-of-day, session boundaries, and break prompts for time-blind users.
Available components
Last scanned (21 hours ago)
Scores higher than 63% of PyPI servers
Category Productivity and Notes
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 Security50
- Malware scan not yet available for this package.Unverified
- 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
- 1 of 17 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (AGPL-3.0-or-later).Pass
- Actively maintained (last published 138 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 191 tokens (~38/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 5 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
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.
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.97 functional
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 0
- Stability: pass → 0.97 functional
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 4 Nov 2026 · Analysed pypi/neurodock-mcp-chronometric@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 17 packages
| Packages resolved | 17 |
|---|---|
| Stale | 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 →
get_time_context Get Time Context ~32
Return current wall-clock time, day, time since last prompt, current session length, and a heuristic energy_zone.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
idle_status Idle Status ~37
Return OS idle seconds, a coarse hyperfocus_signal, and a consent flag. CONSENT-GATED via profile.privacy.os_idle_consent.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
mark_session_end Mark Session End ~39
Close the currently open session, optionally attaching a summary. Closes only the most recent open session; takes no session_id.
| Name | Type | Req | Description |
|---|---|---|---|
| summary | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
mark_session_start Mark Session Start ~41
Open a new work session anchored to a stated intent. Auto-closes any prior unterminated session and surfaces its metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| intent | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
request_break_if_needed Request Break If Needed ~42
Return a coarse break suggestion when the open session has run past `threshold_minutes`, or null when no break is warranted.
| Name | Type | Req | Description |
|---|---|---|---|
| threshold_minutes | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
How do I install the NeuroDock Chronometric MCP server?
NeuroDock Chronometric runs locally as a PyPI package, launched with uvx neurodock-mcp-chronometric. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · neurodock-mcp-chronometric
claude mcp add tlennon-ie-neurodock-mcp-chronometric -- uvx neurodock-mcp-chronometric
What is the NeuroDock Chronometric MCP server?
NeuroDock Chronometric is an MCP server listed in the public MCP registry as io.github.tlennon-ie/neurodock-mcp-chronometric. Externalises time-of-day, session boundaries, and break prompts for time-blind users. This page covers its PyPI package (neurodock-mcp-chronometric).
Is the NeuroDock Chronometric MCP server safe to use?
NeuroDock Chronometric scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. 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 NeuroDock Chronometric MCP server expose?
NeuroDock Chronometric exposes 5 tools: get_time_context, mark_session_start, mark_session_end, request_break_if_needed, idle_status. Their descriptions and schemas cost roughly 191 tokens of context every time the server is loaded.
Is the NeuroDock Chronometric MCP server still maintained?
NeuroDock Chronometric is still listed as active in the MCP registry. We last reached this channel on 4 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 NeuroDock Chronometric MCP server under?
NeuroDock Chronometric declares the AGPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.