Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DayHeart

REMOTE · DAYHEART.APP

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

Available components

+39 this week 78 Trust /100

Last scanned (17 hours ago)

Scores higher than 71% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Productivity and Notes

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security97
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 6 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 9 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 17 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • “change_study” reworded the description of “url” cosmetic
  • 16 Nov 26 −2
    • Stability: unverified → fail ▼ security
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “add_class” was removed ▼ security
    • Tool “add_homework” was removed ▼ security
    • 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 security
    • Schema quality: 130 → 211 ▼ functional
    • Destructive annotations: pass → 100 functional
    • New tool “change_study” functional
    • New tool “change_tasks” functional
  • 15 Nov 26 +41
    • Transport: unverified → pass ▲ security
    • 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. security
    • MCP protocol: unverified → pass ▲ functional
    • 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 functional
  • 8 Nov 26 39

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://dayheart.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dayheart.app CN=WE1,O=Google Trust Services,C=US 12 Nov 2026 10 Feb 2027 ECDSA 256 ECDSA-SHA256 59b1cd69ea08351913709029a98267c5
SANs: dayheart.app, zb-u42anh.dayheart.app, *.zb-u42anh.dayheart.app
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of dayheart.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
dayheart.app. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://dayheart.app/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Sign in to DayHeart to use this tool"

Bearer resource_metadata="https://dayheart.app/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Sign in to DayHeart to use this tool"
Header Value
strict-transport-security max-age=31536000
content-security-policy default-src 'self'; script-src 'self' https://telegram.org https://accounts.google.com/gsi/client https://appleid.cdn-apple.com/appleauth/static/jsapi/appleid/1/; style-src 'self' 'unsafe-inline' https://accounts.google.com/gsi/style; img-src 'self' data: https://static.klipy.com https://static1.klipy.com https://static2.klipy.com; connect-src 'self' https://accounts.google.com/gsi/ https://oauth.telegram.org/auth/get https://api.klipy.com https://www.googleapis.com/drive/v3/ https://www.googleapis.com/upload/drive/v3/; frame-src https://accounts.google.com/gsi/; frame-ancestors 'self' https://web.telegram.org https://*.telegram.org; base-uri 'none'; form-action 'self'
x-content-type-options nosniff
referrer-policy no-referrer

Protected resource metadata

Document https://dayheart.app/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://dayheart.app/mcp
Authorisation server https://dayheart.app

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://dayheart.app/mcp Verified 200
http (plaintext) http://dayheart.app/mcp HTTPS enforced 301 https://dayheart.app/mcp
MCP tools · 8 exposed · ~1,392 tokens

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 →

Tool Tokens
change_study ~733

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.

NameTypeReqDescription
actionstringyesWhat to do
class_idstring–id of the class, for homework or a material of this class
datestring–YYYY-MM-DD: the (first) day of a new class, or the day of the class the homework is for
detailsstring–For set_homework: everything else about the homework, up to 4000 characters
endstring–HH:MM, 24-hour: end of a new class
folderstring–For add_material: folder inside the subject's materials, e.g. "Tests" (empty: no folder); for a link that is already there, moves it
gradestring–For close_subject with a grade: the grade as the user says it, up to 12 characters
kindstring–Kind of class: lecture, practice, lab or seminar
linkstring–Link to an online class
material_idstring–For remove_material: id of the material, as listed with the class or subject
placestring–Place of study (group) name; needed only when the user has several
repeatstring–once (default), weekly or biweekly, for a new class
resultstring–For close_subject: passed as a credit, with a grade, or without a result
roomstring–Room or building, as the user writes it
startstring–HH:MM, 24-hour: start of a new class
subjectstring–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
teacherstring–Teacher's name
textstring–Homework: the text to add (up to 1000 characters), or for set_homework the short line, what and for when (up to 300)
titlestring–For add_material: name to show, up to 120 characters, e.g. "Lecture 3.docx"
untilstring–YYYY-MM-DD: last day for weekly or biweekly; at most 90 classes
urlstring–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…

No output schema declared.

No examples provided.

change_tasks ~204

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.

NameTypeReqDescription
actionstringyesWhat to do with the task
datestring–YYYY-MM-DD; empty string removes the date
duration_minutesinteger–How long the task takes, 1 to 1440 minutes; only with a time
idstring–Task id, for update, complete and reopen
importantboolean–Mark the task important
timestring–HH:MM, 24-hour; needs a date; empty string removes the time
titlestring–What to do, up to 180 characters
urgentboolean–Mark the task urgent

No output schema declared.

No examples provided.

delete ~56

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.

NameTypeReqDescription
idstringyesIts id
kindstringyesWhat to delete

No output schema declared.

No examples provided.

get_classes ~98

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.

NameTypeReqDescription
fromstring–First day, YYYY-MM-DD. Default: today
tostring–Last day, YYYY-MM-DD, at most 92 days after from. Default: a week from "from"

No output schema declared.

No examples provided.

get_day ~39

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

NameTypeReqDescription
datestring–YYYY-MM-DD. Default: today

No output schema declared.

No examples provided.

get_earnings ~98

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.

NameTypeReqDescription
fromstring–First day, YYYY-MM-DD. Default: today
tostring–Last day, YYYY-MM-DD, at most 92 days after from. Default: a week from "from"

No output schema declared.

No examples provided.

get_shifts ~79

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

NameTypeReqDescription
fromstring–First day, YYYY-MM-DD. Default: today
tostring–Last day, YYYY-MM-DD, at most 92 days after from. Default: a week from "from"

No output schema declared.

No examples provided.

get_tasks ~85

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

NameTypeReqDescription
fromstring–First day, YYYY-MM-DD. Default: today
tostring–Last day, YYYY-MM-DD, at most 92 days after from. Default: a week from "from"

No output schema declared.

No examples provided.

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.

remote · dayheart.app

# add to Claude Code
claude mcp add --transport http app-dayheart-dayheart 'https://dayheart.app/mcp'
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.