EpicMeBLOCK
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
This is an example of an application that's exclusively accessible via Model Context Protocol (MCP).
Everything from user registration and authentication to interacting with user data is handled via MCP tools.
The goal is to demonstrate a possible future of applications where users interact with our apps via natural language with LLMs and the MCP protocol. This will also be the basis upon which I will teach how to build MCP tools on EpicAI.pro.
How to Use
⚠️ Important Disclaimer: This is an experimental playground, not a production service. There are no SLAs, guarantees of data privacy, or data retention policies. Use at your own risk and don't store anything important or sensitive.
Server URL
The EpicMe MCP server is deployed at:
https://epic-me-mcp.kentcdodds.workers.dev/mcp
What You Can Do
EpicMe is a personal journaling application that allows you to:
- Create and manage journal entries with titles, content, mood, location,
weather, and privacy settings
- Organize entries with tags for better categorization and filtering
- Get AI-powered tag suggestions for your entries
- Summarize your journal entries with optional filtering by tags or date
range
- Mark entries as favorites and set privacy levels
Getting Started
- Connect to the MCP server using your preferred MCP client (like
- Authenticate by providing your email address - you'll receive a
validation code
- Start journaling using natural language commands
Authentication Flow
The authentication is unique because it works with users who don't exist yet:
- Use the
authenticatetool with your email address - Check your email for a TOTP validation code
- Use the
validate_tokentool with the code to complete authentication - You're now logged in and can access all authenticated features
Available Tools
Authentication Tools
e2ab4a07c87eOBSERVED · 2026-10-07Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add epicme-mcp -- npx -y epicme-mcp
{
"mcpServers": {
"epicme-mcp": {
"command": "npx",
"args": [
"-y",
"epicme-mcp"
]
}
}
}Exposed tools (19)
12 read · 5 write · 2 destructive. Blast radius: 2 tools can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.
| Tool | Risk | Description |
|---|---|---|
add_tag_to_entry | write | |
authenticate | read | |
create_entry | write | |
create_tag | write | |
delete_entry | destructive | |
delete_tag | destructive | |
get_entry | read | |
get_journal_insights_instructions | read | |
get_tag | read | |
get_tag_suggestions_instructions | read | |
list_entries | read | |
list_tags | read | |
logout | read | |
update_entry | write | |
update_tag | write | |
validate_token | read | |
view_entry | read | |
view_journal | read | |
whoami | read |
Trust audit
BLOCKgrade D · trust 69/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | FAIL |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (1 observation(s))
- Network
- declared (5 observation(s))
- Shell
- declared (2 observation(s))
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (8)
exec(input?: (string | URLPatternInit), baseURL?: string): URLPatternResult | null;
exec(query: string): Promise<D1ExecResult>;
delete_entry, delete_tag
.prettierignore
atob(data: string): string;
declare function atob(data: string): string;
@cloudflare/workers-oauth-provider, @epic-web/invariant, @epic-web/totp, @mcp-ui/server, @modelcontextprotocol/sdk, agents, isbot, react
Gates applied: no_behavioural_pass, no_license.
e2ab4a07c87efull audit observations/trust-audit/mcp-server/epicweb-dev__epicme.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-07 | e2ab4a07c87e | BLOCK | D | 69 | first audit |
Questions
What tools does EpicMe expose?
19 in total: 12 read-only, 5 that write, and 2 that can delete or overwrite (delete_entry, delete_tag). Every one is listed on this page with its risk.
Is EpicMe safe to connect to an agent?
No — not without reading the findings first. The audit graded it D (69/100) and found 2 critical or high issues in the source. Each one is listed on this page with the file and line it is on. Separately from the audit: 2 of its tools can destroy data, so scope the token you give it to what you actually need.
What credentials does EpicMe need?
No credential environment variables were found in its source, so it appears to need none.
How current is this page?
The grade is for one exact copy of the source (e2ab4a07c87e), read on 2026-10-07. The repository is watched and re-audited when it changes.