Remote MCP server exposing the exocortex vault (via its git mirror) to Claude from anywhere.
Server has 4 tools with complete schemas and descriptions. Naming follows verb_noun pattern (query_, get_, capture_, leave_). Descriptions are detailed (100-250 chars) and explain WHAT/WHEN/WHY. However, parameter descriptions lack specificity on constraints (e.g., 'limit' has no min/max bounds), and output schemas are not formally documented. Error handling is present but generic. No tool annotations (readOnlyHint/destructiveHint). Composition is sound, tools are single-responsibility and chainable.
Capture a note to the vault's inbox for later filing. The capture is committed to the dedicated inbox-drops branch, never to main. A local consumer script copies drops into the vault's sources/inbox/ and resets the branch.
Read a page from the vault by path. Supports full content, frontmatter-only, or a named section. Directories list their contents.
Guest-tier tool: leave a note for the vault owner. The note is captured to the inbox with guest attribution and a filename prefix for easy identification.
Status-weighted search over the vault. Default scope 'all' covers the wiki (compiled knowledge: concepts, projects, people, life, connections), sources (frozen records of what was said — meeting transcripts, session captures, statements), and notes (the user's own words). Results are ranked with `verified` wiki pages weighted above `draft` — trust is graduated.
Parameter constraints missing: 'limit' in query_wiki has no min/max bounds; 'detail' and 'scope' enums are present but descriptions don't explain when to use each value. LLMs cannot infer valid ranges.
Output schemas not documented: tools return text responses but no formal schema describes the structure of 'WikiHit' objects, directory listings, or error payloads. LLMs cannot plan downstream calls without knowing return fields.
Tool name 'leave_note_for_<owner>' uses template syntax instead of a concrete name. This is inferred from code, not explicitly registered. Actual tool name registration is unclear.
No tool annotations: tools lack readOnlyHint (query_wiki, get_page are read-only) and destructiveHint (capture_to_inbox, leave_note_for_<owner> write to vault). Agents cannot distinguish safe from risky calls.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 65 | 2026-07-28+ | v2 |
Error handling is generic: code returns isError=true with text messages, but does not categorize errors as retryable/user-fixable/fatal or provide recovery guidance (e.g., 'Try search_users() first').