# DayHeart (remote · dayheart.app)

Day planner: work shifts with earnings, classes with homework, tasks. Read your day and add to it.

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

## Components

- remote · `dayheart.app`: 78/100 (this document), [markdown](https://verifymcp.io/servers/app-dayheart-dayheart/dayheart.md), [page](https://verifymcp.io/servers/app-dayheart-dayheart/dayheart)

## Channel facts

- Endpoint: `https://dayheart.app/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-21.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1755 tokens (~219/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 6 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 3 additions.
- **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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 9 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 DayHeart MCP server?

DayHeart is a hosted endpoint at https://dayheart.app/mcp, so there is nothing to install locally. 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 --transport http app-dayheart-dayheart 'https://dayheart.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-dayheart-dayheart": {
      "url": "https://dayheart.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-dayheart-dayheart": {
      "type": "http",
      "url": "https://dayheart.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-dayheart-dayheart]
url = "https://dayheart.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-dayheart-dayheart": {
      "type": "remote",
      "url": "https://dayheart.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-dayheart-dayheart --url 'https://dayheart.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-dayheart-dayheart:
    url: "https://dayheart.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-dayheart-dayheart": {
      "Transport": "http",
      "Url": "https://dayheart.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-dayheart-dayheart -t streamable-http -u 'https://dayheart.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-dayheart-dayheart": {
      "type": "http",
      "url": "https://dayheart.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-17 (score 78, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [cosmetic] “change_study” reworded the description of “url”

### 2026-11-16 (score 78, −2)

- [security regression] Stability: unverified → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [security regression] Tool “add_class” was removed
- [security regression] Tool “add_homework” was removed
- [security regression] Tool “add_task” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] New tool “delete”, which the server declares destructive
- [security] Tool “get_classes” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 130 → 211
- [functional] Destructive annotations: pass → 100
- [functional] New tool “change_study”
- [functional] New tool “change_tasks”

### 2026-11-15 (score 80, +41)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

### 2026-11-08 (score 39)

First indexed and scored.

## MCP tools (8)

### `get_day` (~39 tokens)

My day

Everything on one day: work shifts, classes, tasks and what the shifts earned.

Input parameters:

- `date` (string): YYYY-MM-DD. Default: today

### `get_shifts` (~79 tokens)

Work shifts

Work shifts in a date range with job, start and end time and, if allowed, the money each shift earned.

Input parameters:

- `from` (string): First day, YYYY-MM-DD. Default: today
- `to` (string): Last day, YYYY-MM-DD, at most 92 days after from. Default: a week from "from"

### `get_classes` (~98 tokens)

Classes

Classes (university or school timetable) in a date range: subject, time, room, teacher, homework, materials (links); subjects the user marked closed, with their result; and materials attached to whole subjects.

Input parameters:

- `from` (string): First day, YYYY-MM-DD. Default: today
- `to` (string): Last day, YYYY-MM-DD, at most 92 days after from. Default: a week from "from"

### `get_tasks` (~85 tokens)

Tasks

Tasks with a date in a date range, done or not, and open tasks without a date (inbox, newest first, up to 50).

Input parameters:

- `from` (string): First day, YYYY-MM-DD. Default: today
- `to` (string): Last day, YYYY-MM-DD, at most 92 days after from. Default: a week from "from"

### `get_earnings` (~98 tokens)

Earnings

Money earned by work shifts in a date range, in total and per job (overtime included), before tax; net after tax and fixed salary when the person set them. Default: this month so far.

Input parameters:

- `from` (string): First day, YYYY-MM-DD. Default: today
- `to` (string): Last day, YYYY-MM-DD, at most 92 days after from. Default: a week from "from"

### `change_tasks` (~204 tokens)

Change tasks

Add, change, complete or reopen a task in DayHeart. add needs a title (date and time optional; time needs a date). update changes the title, date, time, length, important or urgent. complete marks the task done; reopen marks it not done. Notes and private tasks are not available.

Input parameters:

- `action` (string, required): What to do with the task
- `date` (string): YYYY-MM-DD; empty string removes the date
- `duration_minutes` (integer): How long the task takes, 1 to 1440 minutes; only with a time
- `id` (string): Task id, for update, complete and reopen
- `important` (boolean): Mark the task important
- `time` (string): HH:MM, 24-hour; needs a date; empty string removes the time
- `title` (string): What to do, up to 180 characters
- `urgent` (boolean): Mark the task urgent

### `change_study` (~733 tokens)

Change classes and homework

Change the user's timetable and homework in DayHeart. add_class adds a class once, every week or every other week until a date. add_homework adds homework on a new line of a class's homework (the same text is not added twice). set_homework replaces it with a short line (what and for when) and optional details; clear_homework removes it. close_subject marks a subject closed with its result; reopen_subject opens it again. add_material attaches a link to a class (class_id) or to the whole subject (subject): DayHeart keeps links, not files, so put the file on the user's cloud drive first and attach its link; remove_material removes one (material_id or url). In a shared group timetable the whole group sees classes, homework and materials; a closed subject is the user's own mark.

Input parameters:

- `action` (string, required): What to do
- `class_id` (string): id of the class, for homework or a material of this class
- `date` (string): YYYY-MM-DD: the (first) day of a new class, or the day of the class the homework is for
- `details` (string): For set_homework: everything else about the homework, up to 4000 characters
- `end` (string): HH:MM, 24-hour: end of a new class
- `folder` (string): For add_material: folder inside the subject's materials, e.g. "Tests" (empty: no folder); for a link that is already there, moves it
- `grade` (string): For close_subject with a grade: the grade as the user says it, up to 12 characters
- `kind` (string): Kind of class: lecture, practice, lab or seminar
- `link` (string): Link to an online class
- `material_id` (string): For remove_material: id of the material, as listed with the class or subject
- `place` (string): Place of study (group) name; needed only when the user has several
- `repeat` (string): once (default), weekly or biweekly, for a new class
- `result` (string): For close_subject: passed as a credit, with a grade, or without a result
- `room` (string): Room or building, as the user writes it
- `start` (string): HH:MM, 24-hour: start of a new class
- `subject` (string): Subject as in the timetable, e.g. "Anatomy (Pr)": the class to add, the class for homework when there is no class_id, the subject to close or reopen, or the subject a material belongs to
- `teacher` (string): Teacher's name
- `text` (string): Homework: the text to add (up to 1000 characters), or for set_homework the short line, what and for when (up to 300)
- `title` (string): For add_material: name to show, up to 120 characters, e.g. "Lecture 3.docx"
- `until` (string): YYYY-MM-DD: last day for weekly or biweekly; at most 90 classes
- `url` (string): For add_material: https link to the file or page (for example a Google Drive file). In a shared place of study the whole group opens it, so the file must be viewable by anyone with the link; the answ…

### `delete` (~56 tokens)

Delete a task or a class

Delete a task or a class from DayHeart for good. This cannot be undone; in a shared group timetable the class disappears for the whole group.

Input parameters:

- `id` (string, required): Its id
- `kind` (string, required): What to delete

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-dayheart-dayheart/dayheart#diagnostics

## Score history

- 2026-11-21: 78
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 78
- 2026-11-17: 78
- 2026-11-16: 78
- 2026-11-15: 80
- 2026-11-14: 39
- 2026-11-13: 39
- 2026-11-12: 39
- 2026-11-11: 39
- 2026-11-10: 39
- 2026-11-09: 39
- 2026-11-08: 39

## Common questions

### What is the DayHeart MCP server?

DayHeart is an MCP server listed in the public MCP registry as app.dayheart/dayheart. Day planner: work shifts with earnings, classes with homework, tasks. Read your day and add to it. This page covers its hosted endpoint (https://dayheart.app/mcp).

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

DayHeart scores 78 out of 100 on VerifyMCP. 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 DayHeart MCP server expose?

DayHeart exposes 8 tools: get_day, get_shifts, get_classes, get_tasks, get_earnings, and 3 more. Their descriptions and schemas cost roughly 1,392 tokens of context every time the server is loaded.

### Does the DayHeart MCP server require authentication?

Yes. DayHeart asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the DayHeart MCP server still maintained?

DayHeart is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the DayHeart MCP server?

VerifyMCP ran 13 checks on DayHeart, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://dayheart.app/mcp
- Website: https://dayheart.app/en/connect-ai
- Changelog RSS feed: https://verifymcp.io/servers/app-dayheart-dayheart/dayheart.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-dayheart-dayheart/dayheart/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-dayheart-dayheart/dayheart.json
- HTML version of this page: https://verifymcp.io/servers/app-dayheart-dayheart/dayheart
