com.deerdawn/deerdawn

REMOTE · API.DEERDAWN.COM · 2 COMPONENTS · SCANNED AUG 3

AI session memory: the brief your AI reads before every session so no session starts cold.

Available components

remote · api.deerdawn.com 75 npm · @deerdawn/mcp-server 61

+10 this week 75 75 Trust /100

Trust breakdown (6 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 →

Endpoint Security94

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
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. View diagnostics → Pass
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability40

AI-judged instruction clarity (poor).Fail
Context-footprint check failed: tool/resource definitions use about 2638 tokens (~114/item across 23 items; 23 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 Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · api.deerdawn.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http com-deerdawn-deerdawn https://api.deerdawn.com/api/v1/mcp

# ~/.codex/config.toml

[mcp_servers.com-deerdawn-deerdawn]
url = "https://api.deerdawn.com/api/v1/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-deerdawn-deerdawn": {
      "type": "remote",
      "url": "https://api.deerdawn.com/api/v1/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add com-deerdawn-deerdawn --url https://api.deerdawn.com/api/v1/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  com-deerdawn-deerdawn:
    url: "https://api.deerdawn.com/api/v1/mcp"

// mcp.json

{
  "mcpServers": {
    "com-deerdawn-deerdawn": {
      "type": "http",
      "url": "https://api.deerdawn.com/api/v1/mcp"
    }
  }
}

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

Changelog Show cosmetic changes

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.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
1 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
29 Jul 26 +1
- Schema quality: 2196 → 2638 ▼ functional
- New tool “cleanup_context” functional
- New tool “mark_resolved” functional
- New tool “list_skills” functional
- New tool “get_skill” functional
- New tool “get_next_best_context” functional
- “update_context” added an optional parameter “commands” cosmetic
27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 64

First indexed and scored.

Show 6 earlier entries Hide earlier entries

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 3 Aug 2026 · Probed https://api.deerdawn.com/api/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=api.deerdawn.com	CN=YE2,O=Let's Encrypt,C=US	6 Jul 2026	4 Oct 2026	ECDSA 256	ECDSA-SHA384	5ebcf3f49db939c7b3b2b552ce8cd8eb4a4
SANs: api.deerdawn.com
CN=YE2,O=Let's Encrypt,C=US (CA)	CN=Root YE,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	ECDSA 384	ECDSA-SHA384	4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA)	CN=ISRG Root X2,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	ECDSA-SHA384	872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	SHA256-RSA	6c8f1dc727c7117f7baf853ac980f9cd

DNSSEC insecure

Validation of api.deerdawn.com. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
com.	present	19718	13	Verified
deerdawn.com.	absent			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://api.deerdawn.com/.well-known/oauth-protected-resource"

Bearer resource_metadata="https://api.deerdawn.com/.well-known/oauth-protected-resource"

Header	Value
strict-transport-security	max-age=31536000; includeSubDomains; preload
content-security-policy	default-src 'none';script-src 'self';style-src 'self';img-src 'self' data:;connect-src 'self' https://api.clerk.com https://*.stripe.com;frame-ancestors 'none';form-action 'self';base-uri 'self';font-src 'self' https: data:;object-src 'none';script-src-attr 'none';upgrade-insecure-requests
x-content-type-options	nosniff
x-frame-options	SAMEORIGIN
referrer-policy	strict-origin-when-cross-origin

Protected resource metadata

Document	https://api.deerdawn.com/.well-known/oauth-protected-resource
Retrieved	Yes
Resource	https://api.deerdawn.com/api/v1/mcp
Authorisation server	https://api.deerdawn.com

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://api.deerdawn.com/api/v1/mcp	Verified	200
http (plaintext)	http://api.deerdawn.com/api/v1/mcp	HTTPS enforced	301	https://api.deerdawn.com/api/v1/mcp

MCP tools — 23 exposed · ~2,148 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.

Tool Tokens

archive_project ~92

Archive a dead or finished project so it stops cluttering list_projects and never auto-resolves as the active project. Preserves all history. Pass unarchive:true to restore it. Refuses to archive an umbrella that still has live subprojects.

Input Output Examples

Name	Type	Req	Description
project_id	string	yes	The project to archive (or restore).
unarchive	boolean	—	Set true to restore a previously archived project instead of archiving.

Name	Type	Req	Description
archived	boolean	—	—
project_id	string	yes	—
project_name	string	yes	—

No examples provided.

cleanup_context ~94

Clean up task context at handoff/finish time. Marks the finished task as completed, clears open-task command history, and returns unresolved questions that still need answers.

Input Output Examples

Name	Type	Req	Description
ask_questions	boolean	—	Include open follow-up questions that should be answered.
complete_task	boolean	—	Force-complete and close the active task now.
project_id	string	—	Optional project ID. Omit to use the active project.

Name	Type	Req	Description
text	string	yes	The formatted brief, ready to read.

No examples provided.

create_project ~118

Create a new DeerDawn project to track a codebase, feature, or initiative. Pass parent_project_id to create it as a subproject under an umbrella (e.g. a workstream of a larger product) — subprojects keep their own task and board.

Input Output Examples

Name	Type	Req	Description
description	string	—	Brief description of what this project is
parent_project_id	string	—	Optional. Create this as a subproject under the given top-level project. The hierarchy is one level deep.
project_name	string	yes	Name of the project

Name	Type	Req	Description
parent_project_id	string	—	—
project_id	string	yes	—
project_name	string	yes	—

No examples provided.

find_known_paths ~86

Search durable path memory (hot paths, surfaces, debugging notes) before doing a repo-wide search. Use a path-oriented query like "auth modal" or "signup route".

Input Output Examples

Name	Type	Req	Description
limit	number	—	Maximum number of paths to return (default 10).
project_id	string	—	Optional project ID to scope the search.
query	string	yes	Path-oriented query.

Name	Type	Req	Description
paths	array	yes	Matching hot paths, surfaces, and debugging notes.

No examples provided.

get_context ~111

Get the current context for a specific project — task, status, decisions, goals, and open questions. If you have not called start_session yet this session, call it first. Call list_projects if you don't have a project_id.

Input Output Examples

Name	Type	Req	Description
project_id	string	yes	Project ID from list_projects
sections	array	—	Which sections to include. Omit for task+status. Use board (or todos) for the task board.
verbosity	string	—	How much detail to return per section.

Name	Type	Req	Description
project_id	string	—	—
text	string	yes	The formatted project context.

No examples provided.

get_next_best_context ~78

Return the most relevant next context to fetch or use for the current task/session, including open questions and pending decisions ranked for relevance and token efficiency.

Input Output Examples

Name	Type	Req	Description
limit	number	—	Max ranked suggestions to return (default 5).
project_id	string	—	Optional active project override.
tool	string	—	Optional active tool surface.

Name	Type	Req	Description
suggestions	array	—	Ranked next-best context suggestions.
text	string	yes	Formatted summary + ranked suggestions.

No examples provided.

get_project_map ~87

Return the durable project map: hot paths, entrypoints, named surfaces, and recent debugging notes. Call this BEFORE searching the codebase — the file may already be known. Omit project_id to use the active project.

Input Output Examples

Name	Type	Req	Description
project_id	string	—	Project ID. Omit to use the active project.
verbosity	string	—	How much of the project map to return.

Name	Type	Req	Description
project_id	string	—	—
text	string	yes	The formatted project map.

No examples provided.

get_skill ~50

Fetch one shared skill in full (including markdown body) by slug. Call after list_skills when a skill is relevant to the current task.

Input Output Examples

Name	Type	Req	Description
slug	string	yes	Skill slug from list_skills.

Name	Type	Req	Description
name	string	—	—
slug	string	—	—
text	string	yes	The skill markdown body.

No examples provided.

get_workspace_entities ~138

Query typed workspace knowledge — services, capabilities, patterns, environments, and workflows — for architecture-level orientation.

Input Output Examples

Name	Type	Req	Description
limit	number	—	Maximum number of entities to return (default 10).
project_id	string	—	Optional project to rank against.
query	string	—	Optional text query.
scope	string	—	Limit to workspace-wide or project-scoped entities.
status	string	—	Optional status filter (active, shipped, planned, stale, resolved).
surface	string	—	Optional surface filter (mcp_tool, api, dashboard, …).
types	array	—	Optional entity types to filter.

Name	Type	Req	Description
entities	array	yes	—

No examples provided.

get_workspace_overview ~59

Get a full overview of your workspace — all projects, durable knowledge, and capabilities.

Input Output Examples

Name	Type	Req	Description
mode	string	—	startup for a compact brief, overview for full details
verbosity	string	—	How much detail to include in the overview.

Name	Type	Req	Description
text	string	yes	The formatted brief, ready to read.

No examples provided.

list_projects ~23

List all your DeerDawn projects with their current task and project ID.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
projects	array	yes	—

No examples provided.

list_skills ~61

List available shared skills (name + description, no body). Use on web tools (ChatGPT, Claude.ai) that cannot read skill files from disk.

Input Output Examples

Name	Type	Req	Description
project_id	string	—	Optional project ID to scope skills. Omit for workspace-wide skills.

Name	Type	Req	Description
skills	array	yes	—

No examples provided.

manage_todos ~209

Manage the active project's task board — a scrum-style board where every task is a card that moves across phase columns: Backlog → Blocked → In Progress → Integration → Testing → Done. Actions: add (new cards, default to Backlog or a named phase), move (re-column a card), complete (shorthand for → Done), remove (delete a mistaken card), list (show the board grouped by column). The single task tracker for the project.

Input Output Examples

Name	Type	Req	Description
action	string	yes	add new cards, move a card to another phase, mark cards complete (→ Done), remove erroneous cards, or list the board.
phase	string	—	For add: the column new cards land in (default backlog). For move: the destination column (required).
project_id	string	—	Optional project ID. Omit to use the active project.
todos	array	—	For add: card titles. For move/complete/remove: card IDs or title substrings to match.

Name	Type	Req	Description
action	string	yes	The action performed.
affected	array	—	Requested cards that actually matched and were changed by add/move/complete/remove.
board	array	—	Present for action=list — the board grouped by phase column.
phase	string	—	—
unmatched	array	—	Requested cards (move/complete/remove) that matched no existing card — a no-op, distinct from a real change.

No examples provided.

mark_resolved ~134

Mark a knowledge or decision entity as resolved so it stops appearing in normal context loads. Resolved entries are still retrievable via get_workspace_entities({ status: "resolved" }). Use when a decision has been implemented, a known issue has been fixed, or a knowledge entry is no longer relevant.

Input Output Examples

Name	Type	Req	Description
entity_type	string	—	Optional entity type filter. Omit to match any type.
notes	string	—	Optional brief note on why/how it was resolved.
project_id	string	—	Optional project ID to scope the search.
title	string	yes	Title or key phrase matching the entity to resolve.

Name	Type	Req	Description
text	string	yes	The formatted brief, ready to read.

No examples provided.

record_debug_finding ~120

Record a durable debugging finding, optionally tied to file paths and a commit/diff ref, after diagnosing a bug or tracing a non-obvious handoff.

Input Output Examples

Name	Type	Req	Description
added_at	string	—	Optional ISO timestamp override.
commit_ref	string	—	Optional commit SHA/ref containing the fix.
diff_ref	string	—	Optional PR/diff URL or identifier.
paths	array	—	Optional related file paths.
project_id	string	yes	Project ID to attach the finding to.
summary	string	yes	Concise factual finding.

Name	Type	Req	Description
project_id	string	—	—
project_name	string	—	—
recorded	boolean	yes	—

No examples provided.

record_hot_paths ~75

Record durable file/folder hot paths AFTER you discover them, so future sessions find them before searching. Append nodes — do not restate the whole tree.

Input Output Examples

Name	Type	Req	Description
items	array	yes	Hot paths to append — one entry per file or folder worth remembering.
project_id	string	yes	Project ID to attach hot paths to.

Name	Type	Req	Description
project_id	string	—	—
project_name	string	—	—
recorded	number	yes	Number of hot paths recorded.

No examples provided.

rename_project ~78

Rename a project (umbrella or subproject). Use to tidy inconsistent, unclear, or shouty project names — the change is immediate and flows into every future brief. Junk names (file paths, "Untitled") are rejected.

Input Output Examples

Name	Type	Req	Description
project_id	string	yes	The project to rename.
project_name	string	yes	The new name.

Name	Type	Req	Description
project_id	string	yes	—
project_name	string	yes	—

No examples provided.

search_context ~92

Search across all your DeerDawn projects by keyword or topic. If you have not called start_session yet this session, call it first — it may already answer the question without a search.

Input Output Examples

Name	Type	Req	Description
limit	number	—	Maximum number of results to return (1-10, default 5).
query	string	yes	What to search for — e.g. "auth decisions" or "projects using PostgreSQL"

Name	Type	Req	Description
results	array	yes	—

No examples provided.

set_project_parent ~115

Re-parent an existing project: nest it under a top-level umbrella by passing parent_project_id, or promote it back to top-level by omitting parent_project_id. Use this to organize related projects into one umbrella after the fact. One level deep; the umbrella must be top-level and the project being moved must have no subprojects of its own.

Input Output Examples

Name	Type	Req	Description
parent_project_id	string	—	The umbrella to nest under. Omit to promote the project to top-level.
project_id	string	yes	The project to move.

Name	Type	Req	Description
parent_project_id	string	—	—
project_id	string	yes	—
project_name	string	yes	—

No examples provided.

start_session ~43

Call at the start of every session. Returns your active project context — current task, recent decisions, open questions — so you can resume without re-explaining the project.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
text	string	yes	The formatted brief, ready to read.

No examples provided.

switch_subproject ~119

Set which subproject is active for this codebase, so start_session, update_context, and manage_todos target it by default. The choice is remembered per workspace until you switch again. Keyed to the codebase (workspace_key), which the Claude Code / Cursor MCP sends automatically.

Input Output Examples

Name	Type	Req	Description
project_id	string	yes	The subproject (or project) to make active for this workspace.
workspace_key	string	yes	Repo identity for the codebase this pin applies to (normalized git remote or root). Sent automatically by the local MCP.

Name	Type	Req	Description
project_id	string	yes	—
project_name	string	yes	—
workspace_key	string	—	—

No examples provided.

update_context ~101

Update the context for a project. Call this after a decision is made, a task changes, or a feature ships.

Input Output Examples

Name	Type	Req	Description
commands	array	—	Key runnable commands to store. Stored by label — overwrites existing entry with the same label.
project_id	string	yes	Project ID to update
summary	string	yes	What changed or was decided — 1-2 sentences
tool	string	—	Which tool surface the update originated from.

Name	Type	Req	Description
last_updated	string	—	—
project_id	string	yes	—
project_name	string	—	—

No examples provided.

upsert_workspace_entities ~65

Create or update typed workspace entities (services, capabilities, patterns) and relationships. Use for durable architecture knowledge that should persist beyond a single project note.

Input Output Examples

Name	Type	Req	Description
entities	array	yes	Typed workspace entities to create or update.
relations	array	—	Optional relationships between entities.

Name	Type	Req	Description
entities_upserted	number	yes	—
relations_recorded	number	—	—

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	64
27 Jul	65
28 Jul	65
29 Jul	66
30 Jul	67
31 Jul	73
1 Aug	74
2 Aug	74
3 Aug	75