Habitscore

tech.mydev-toolsPublished by mydev-tools.techv1.0.1Updated Oct 30, 2026

Reliability scoring for agent jobs and habit analytics. Pay per call via x402 (USDC on Base).

VerifiedSTDIODesktop onlyFinanceData & Analytics

Overview

AI-generated overview

Local MCP server that scores recurring tasks and habits for reliability and adherence, paid per call in USDC on Base via x402.

What you can do
  • Score recurring tasks, jobs, pipelines and scheduled workflows for reliability, with grades, lapse risk, latency-trend warnings and priority-ranked remediation
  • Score habits and recurring activities for adherence, consistency, streak momentum, lapse-risk flags, highlights and watchouts
  • Rank next-best actions per habit with rationale and priority scores
  • Extract condensed behavioural insights, patterns, correlations and risk signals
  • Build a multi-week plan for a single habit with weekly targets and dated milestones
When to use it
Useful when an assistant needs deterministic, rule-based scoring over completion history it already holds — operational reliability reviews of scheduled jobs, habit or routine adherence monitoring, or planning next steps for a routine. It is stateless and does not store or read any history itself, so the caller supplies all the numbers.
Requirements
Runs locally via npx (Node.js) over stdio, desktop clients only. Needs network access to the API origin and a Base RPC endpoint (BASE_RPC_URL, default mainnet.base.org). Paid calls need HABITSCORE_PRIVATE_KEY, the key of a Base wallet holding USDC; HABITSCORE_MAX_SPEND_USD caps spend per call. Without the key it runs in quote-only mode.
Before you install
Paid tools spend real USDC on Base: $0.03 to $0.10 per call, so agent retry loops can cost money; HABITSCORE_MAX_SPEND_USD is the only per-call cap. HABITSCORE_PRIVATE_KEY is a wallet private key — use a dedicated wallet holding only what you intend to spend. Input data is sent to a third-party API. Output is not medical, psychological or financial advice.

Installation

In SourceWeft

  1. Open Habitscore in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

habitscore-mcp

MCP server for Habitscore — analytics over anything with a recurring completion history.

Two families of tools, one engine:

  • Operational reliability — score recurring tasks, jobs, pipelines and scheduled workflows. Success rate, streak recovery, lapse risk, latency-trend warnings, and remediation ranked by priority.
  • Behavioural analytics — the same scoring over habit and routine data. Adherence, consistency, momentum, lapse risk, next-best actions, multi-week plans.

Pays per call with x402: USDC on Base, no account, no API key, no subscription. From $0.03 per call.

Walkthrough with a working x402 client example: https://mydev-tools.tech/agents/reliability/

Why it works this way

The server runs on your machine with your wallet. It signs payments locally and the private key never leaves the process. Nothing is custodied on our side and there is no account to create — the same promise the HTTP API makes.

Without a wallet configured, every tool still works in quote-only mode: it returns the price and the payment terms instead of erroring, so you can see what a call would cost before funding anything.

Install

jsonc
// Claude Desktop: claude_desktop_config.json// Cursor:         ~/.cursor/mcp.json{  "mcpServers": {    "habitscore": {      "command": "npx",      "args": ["-y", "habitscore-mcp"],      "env": {        "HABITSCORE_PRIVATE_KEY": "0x…",        "HABITSCORE_MAX_SPEND_USD": "0.25"      }    }  }}

Omit HABITSCORE_PRIVATE_KEY to start in quote-only mode.

Wallet

Use a dedicated wallet holding only what you intend to spend. Fund it with a small amount of USDC on Base (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913). You do not need ETH: under EIP-3009 you sign the authorisation off-chain and the facilitator submits the transaction and pays the gas.

HABITSCORE_MAX_SPEND_USD caps what a single tool call may spend, and is checked against the price the server actually quotes before anything is signed. An agent loop that retries a paid tool can otherwise spend without bound, and you are the one paying — so a server that quotes more than you authorised is refused rather than paid.

Tools

ToolPriceReturns
analyze_reliability$0.08Reliability score and grade per task, lapse risk, latency-trend warnings, priority-ranked remediation
analyze_behaviour$0.05Adherence and consistency scores, streak momentum, lapse-risk flags, highlights, watchouts, recommendations
recommend_next_actions$0.03Ranked next-best action per habit with rationale and priority
extract_insights$0.05Condensed patterns, correlations and risk signals
build_habit_plan$0.10Multi-week plan for one habit: weekly targets and dated milestones

Price is per call, not per habit. analyze_behaviour accepts up to 25 habits for the same $0.05, so batching is by far the cheapest way to use this.

Input

Reliability:

json
{  "system": "billing-pipeline",  "tasks": [    {      "name": "nightly-etl",      "success_rate": 0.83,      "current_streak": 0,      "best_streak": 52,      "runs": 210,      "latency_trend": "rising",      "p95_latency_ms": 38000,      "cadence": "daily",      "critical": true    }  ]}

name, success_rate (0–1), current_streak and best_streak are required. Note that latency_trend: "rising" is the degradation signal — the opposite polarity to the behavioural tools, where a falling trend is the warning.

Behavioural:

json
{  "habits": [    {      "name": "Morning run",      "completion_rate": 0.72,      "current_streak": 9,      "best_streak": 21,      "average_mood": 7.4,      "energy_trend": "rising"    }  ]}

name, completion_rate (0–1), current_streak and best_streak are required. average_mood, mood_correlation, energy_trend and risk_score are optional and sharpen the result.

"Habit" is the domain vocabulary, but the analysis applies to any recurring activity with completion history — training schedules, medication adherence, study routines, recurring operational tasks.

What it does not do

The engine is deterministic and CPU-only: threshold rules and arithmetic over the numbers you supply. Same input, same output, every time.

It is not a language model and does not generate prose beyond composing its findings. It does not store anything — the agent endpoints are stateless, accept no user identifier, and cannot read or infer any stored history. It is not medical, psychological or financial advice.

Environment

VariableDefaultPurpose
HABITSCORE_PRIVATE_KEY—Wallet key for signing payments. Omit for quote-only mode.
HABITSCORE_MAX_SPEND_USD0.25Hard cap per tool call, enforced before signing.
HABITSCORE_API_URLhttps://api.mydev-tools.techAPI origin.
BASE_RPC_URLhttps://mainnet.base.orgBase RPC for balance reads and signing context.

Verifying a charge

Every successful paid call appends the settlement transaction hash to the tool output. Open it on basescan.org to confirm the amount and recipient independently of anything this server reports.

Links

Volume rebate

Verified spend earns credits back — 5% from $10 lifetime, 10% from $100, 15% from $1,000, with higher rate limits at each tier. Credits are returned inline in the response that earns them and are redeemed with an X-Agent-Credit header on a later call.

MIT licensed.

Source: README.md at commit 03b22a9

Tools

5

analyze_reliability

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.

Parameterstasksrequiredsystem

analyze_behaviour

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.

Parametershabitsrequired

recommend_next_actions

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.

Parametershabitsrequired

extract_insights

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.

Parametershabitsrequired

build_habit_plan

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.

Parametershabitrequiredhorizon_days

Version history

1
  1. v1.0.1LatestOct 30, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts