tech.mydev-tools/habitscore
NPM · HABITSCORE-MCP
Reliability scoring for agent jobs and habit analytics. Pay per call via x402 (USDC on Base).
Available components
Last scanned (23 hours ago)
Scores higher than 51% of npm servers
Category Monitoring and Observability
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 111 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Ialyahya96/habitscore-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 523 tokens (~104/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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 60
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 4 Nov 2026 · Analysed npm/habitscore-mcp@1.0.1
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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Ialyahya96/habitscore-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Ialyahya96/habitscore-mcp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3539150652 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b1ad40e0b0c6f10811524c3fe6a9293e456a9a60044fac6267b4818bd87806f2bc18a169aa781abf58545d2633fa088c80f50e248f1d21f5eb7d7d2ff |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 111 packages
| Packages resolved | 111 |
|---|---|
| Stale | 30 |
| 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 →
analyze_behaviour ~108
Behavioural analysis over up to 25 habits or recurring activities in one call. Returns adherence and consistency scores, streak momentum, lapse-risk flags, highlights, watchouts and recommendations. Use for adherence monitoring, routine optimisation, engagement and churn-risk signals, and streak analysis. Costs $0.05 in USDC on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| habits | array | yes | Up to 25 habits. Price is per CALL, not per habit — batch aggressively, sending 25 costs the same as sending one. |
No output schema declared.
No examples provided.
analyze_reliability ~178
Reliability analysis for up to 25 recurring tasks, jobs, pipelines or scheduled workflows in one call. Returns a reliability score and grade (healthy/degrading/unstable/failing) per task, lapse risk, streak recovery, latency-trend warnings, and remediation actions ranked by priority so the list is actionable top-down. Use for cron and pipeline monitoring, flaky-job triage, SLA and uptime adherence, agent task reliability, and deciding what to fix first. Deterministic threshold analysis over the figures you supply — no model, no log parsing, no root-cause inference. Costs $0.08 in USDC on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| system | string | – | Optional label to correlate the response with a system. |
| tasks | array | yes | Price is per CALL, not per task — sending 25 costs the same as sending one. |
No output schema declared.
No examples provided.
build_habit_plan ~63
Multi-week plan for ONE habit: weekly targets and dated milestones over a chosen horizon. The most compute-intensive endpoint. Costs $0.10 in USDC on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| habit | object | yes | – |
| horizon_days | integer | – | Planning horizon in days. |
No output schema declared.
No examples provided.
extract_insights ~86
Condensed behavioural highlights and watchouts — patterns, correlations and risk signals — without the full aggregate breakdown. Use when you want the narrative rather than the numbers. Costs $0.05 in USDC on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| habits | array | yes | Up to 25 habits. Price is per CALL, not per habit — batch aggressively, sending 25 costs the same as sending one. |
No output schema declared.
No examples provided.
recommend_next_actions ~88
Ranked next-best action per habit, each with a rationale and a priority score. The cheapest endpoint, deterministic and CPU-only, so it is suitable for high-frequency loops. Costs $0.03 in USDC on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| habits | array | yes | Up to 25 habits. Price is per CALL, not per habit — batch aggressively, sending 25 costs the same as sending one. |
No output schema declared.
No examples provided.
How do I install the tech.mydev-tools/habitscore MCP server?
tech.mydev-tools/habitscore runs locally as an npm package, launched with npx -y habitscore-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · habitscore-mcp
claude mcp add tech-mydev-tools-habitscore -- npx -y habitscore-mcp
What is the tech.mydev-tools/habitscore MCP server?
tech.mydev-tools/habitscore is an MCP server listed in the public MCP registry as tech.mydev-tools/habitscore. Reliability scoring for agent jobs and habit analytics. Pay per call via x402 (USDC on Base). This page covers its npm package (habitscore-mcp).
Is the tech.mydev-tools/habitscore MCP server safe to use?
tech.mydev-tools/habitscore scores 75 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. 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 tech.mydev-tools/habitscore MCP server expose?
tech.mydev-tools/habitscore exposes 5 tools: analyze_reliability, analyze_behaviour, recommend_next_actions, extract_insights, build_habit_plan. Their descriptions and schemas cost roughly 523 tokens of context every time the server is loaded.
Is the tech.mydev-tools/habitscore MCP server still maintained?
tech.mydev-tools/habitscore 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 tech.mydev-tools/habitscore MCP server under?
tech.mydev-tools/habitscore declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.