io.github.BitmapAsset/dear-agent
NPM · DEAR-AGENT · SCANNED SEP 24
Your AI agent keeps your diary for you. Local-first, private, works in any agent.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 (MIT).Pass
- Actively maintained (last published 85 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 740 tokens (~56/item across 13 items; 11 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 44% 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
How do I install the io.github.BitmapAsset/dear-agent MCP server?
io.github.BitmapAsset/dear-agent runs locally as an npm package, launched with npx -y dear-agent. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · dear-agent
claude mcp add bitmapasset-dear-agent -- npx -y dear-agent
{
"mcpServers": {
"bitmapasset-dear-agent": {
"command": "npx",
"args": [
"-y",
"dear-agent"
]
}
}
} {
"servers": {
"bitmapasset-dear-agent": {
"command": "npx",
"args": [
"-y",
"dear-agent"
]
}
}
} codex mcp add bitmapasset-dear-agent -- npx -y dear-agent
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bitmapasset-dear-agent": {
"type": "local",
"command": [
"npx",
"-y",
"dear-agent"
],
"enabled": true
}
}
} openclaw mcp add bitmapasset-dear-agent --command npx --arg -y --arg dear-agent
mcp_servers:
bitmapasset-dear-agent:
command: "npx"
args: ["-y", "dear-agent"] {
"McpServers": {
"bitmapasset-dear-agent": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"dear-agent"
]
}
}
} assistant mcp add bitmapasset-dear-agent -t stdio -c npx -a -y dear-agent
{
"mcpServers": {
"bitmapasset-dear-agent": {
"command": "npx",
"args": [
"-y",
"dear-agent"
]
}
}
} 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.
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Sept 26 −3
- Stability: pass → 0.80 functional
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
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 24 Sept 2026 · Analysed npm/dear-agent@0.2.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
add_entry ~124
Record a text moment in the user's diary. Capture whenever they share something worth remembering — an event, feeling, win, or decision. The user never types into an app; you keep the diary for them.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Day: "today" (default), "yesterday", or YYYY-MM-DD. |
| mood | string | – | Optional one-word mood. |
| tags | array | – | Optional short tags, e.g. work, family, health. |
| text | string | yes | What happened, in the user's own meaning, first person where it fits. |
No output schema declared.
No examples provided.
add_photo ~81
Save a photo into the user's diary for a day (local path or base64), with an optional caption.
| Name | Type | Req | Description |
|---|---|---|---|
| caption | string | – | – |
| data | string | – | – |
| date | string | – | Day: "today" (default), "yesterday", or YYYY-MM-DD. |
| filename | string | – | – |
| path | string | – | – |
No output schema declared.
No examples provided.
add_voice_note ~83
Save a voice note into the user's diary for a day (local path or base64), with an optional transcript.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | – | – |
| date | string | – | Day: "today" (default), "yesterday", or YYYY-MM-DD. |
| filename | string | – | – |
| path | string | – | – |
| transcript | string | – | – |
No output schema declared.
No examples provided.
get_day ~49
Read back one day's full diary entry, including any photos and voice notes filed that day.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Day: "today" (default), "yesterday", or YYYY-MM-DD. |
No output schema declared.
No examples provided.
get_range ~31
Read diary entries between two dates (inclusive).
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | – |
| start | string | yes | – |
No output schema declared.
No examples provided.
list_days ~21
List every day that has a diary entry, oldest to newest.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
on_this_day ~56
Resurface entries from this same calendar date in past years (true anniversaries). The memory people fall in love with.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Day: "today" (default), "yesterday", or YYYY-MM-DD. |
No output schema declared.
No examples provided.
recall ~113
Turn the diary into living memory of the person. With `about`, returns everything the diary knows about a person/place/topic across time. Without it, returns a profile digest (recurring people, themes, mood pattern, open commitments) for you to synthesize into who this person is. This is what makes Dear Agent a memory, not just a notebook.
| Name | Type | Req | Description |
|---|---|---|---|
| about | string | – | A person, place, project, or topic to recall. Omit for a whole-life profile digest. |
| limit | integer | – | – |
No output schema declared.
No examples provided.
reflect ~84
Get reflection material so you can proactively talk back to the user: patterns, progress, open loops, and on-this-day memories over the last week or month. Use for a daily check-in or weekly recap so the diary feels alive.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Day: "today" (default), "yesterday", or YYYY-MM-DD. |
| period | string | – | – |
No output schema declared.
No examples provided.
search ~37
Search the whole diary for a word or phrase; returns matching days with snippets.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
weekly_digest ~50
Pull the last 7 days of entries so you can write the user a short weekly reflection.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Day: "today" (default), "yesterday", or YYYY-MM-DD. |
No output schema declared.
No examples provided.
What is the io.github.BitmapAsset/dear-agent MCP server?
io.github.BitmapAsset/dear-agent is an MCP server listed in the public MCP registry as io.github.BitmapAsset/dear-agent. Your AI agent keeps your diary for you. Local-first, private, works in any agent. This page covers its npm package (dear-agent).
Is the io.github.BitmapAsset/dear-agent MCP server safe to use?
io.github.BitmapAsset/dear-agent scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. 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 io.github.BitmapAsset/dear-agent MCP server expose?
io.github.BitmapAsset/dear-agent exposes 11 tools: add_entry, add_photo, add_voice_note, get_day, get_range, and 6 more. Their descriptions and schemas cost roughly 729 tokens of context every time the server is loaded.
Is the io.github.BitmapAsset/dear-agent MCP server still maintained?
io.github.BitmapAsset/dear-agent is still listed as active in the MCP registry. We last reached this channel on 24 September 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 io.github.BitmapAsset/dear-agent MCP server under?
io.github.BitmapAsset/dear-agent declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.