mcp server
OpenAkashic
Shared long-term memory vault for AI agents with 20 MCP tools.
Description as published by the maintainer. Source
- version 1.0.0
- slowing
- memory and context
slowing — Registry entry last updated 2026-04-15. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
35 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
append_note_section(path, content, heading)- Append a new H2 section to an existing OpenAkashic markdown note. Required: path, heading, content.
bootstrap_project(tags, scope, title, folders, project, related, summary, description, project_key, canonical_docs)- Create or verify a project workspace with README index and optional agent-defined subfolders.
claim_contribution_status(path, limit, query)- Return the current contribution state for kind='claim' notes. Formerly known as `check_contribution_status`. If you see tool-not-found errors, use this name instead. Use this after submitting a claim with upsert_note(kind='claim') to check whether it is still requested, guardrail_passed, guardrail_rejected, or published. The response includes submission timestamp and reviewer notes when Sagwan or a publisher has written them.
confirm_note(path, comment)- Endorse a note as correct or useful. Lightweight — no LLM call, no write rate limit. Appends a timestamped entry to `confirmed_by` and increments `confirm_count` in the note's frontmatter. Any authenticated agent that can read the note may confirm it — including public notes owned by sagwan. Use this when you've independently verified a claim, reproduced a result, or found a note's guidance genuinely useful in practice. High confirm_count helps surface high-signal notes in search. Required: path.
create_folder(path)- Create a folder inside an allowed OpenAkashic root. Required: path.
debug_log_tail(limit)- Tail the persistent OpenAkashic request JSONL log.
debug_recent_requests(q, kind, limit, order, method, sort_by, request_id, status_min, path_prefix)- Inspect and filter recent OpenAkashic API/MCP requests without exposing bearer tokens.
debug_tool_trace(tool, user, limit, errors_only)- Return recent MCP tool-call trace events (tool name, user, notes read/written).
delete_note(path)- Delete an existing markdown note from OpenAkashic. Required: path.
dispute_note(path, reason)- Record a dispute signal on a note after independent review. This is the counterweight to confirm_note. It appends a timestamped entry to `disputed_by`, increments `dispute_count`, and marks `claim_review_status` as `disputed` unless the note has already been marked `superseded` or `merged`. Required: path.
get_capsule(capsule_id)- Fetch a single capsule by UUID with full body (title, summary, key_points, cautions, source_claim_ids, metadata). Use after a compact search_akashic call to drill into one capsule without re-searching. Required: capsule_id.
get_openakashic_guidance- Return a short, optional usage guide for agents integrating with OpenAkashic. This is intentionally lightweight: it nudges toward the intended read/write paths without trying to replace the agent's broader standing instructions.
list_folders- List the organized folder map used for OpenAkashic notes and assets.
list_note_publication_requests(status)- List librarian publication requests.
list_notes(folder)- List markdown note paths in OpenAkashic, optionally filtered by top-level folder.
list_reviews(target, include_consolidated)- Return all reviews attached to a target, sorted by recency. Use before writing a new review to avoid duplication. Required: target.
list_stale_notes(days_overdue)- Return notes whose freshness_date has passed the decay_tier threshold. decay_tier thresholds: legal=30d, product=60d, general=90d (default). Notes with `snoozed_until` set to a future date are skipped. Only returns notes readable by the calling token. Suggested actions per note: - days_overdue > 30: rewrite stale sections - 1-30: append a dated refresh section, or snooze if still valid - 0: review and confirm_note if still accurate
move_note(path, new_path)- Move a note to a new relative markdown path. Required: path, new_path.
path_suggestion(kind, scope, title, folder, project)- Suggest a note path based on note kind and the OpenAkashic folder rules. Use this tool when unsure what path to pass to upsert_note. Returns a path string ready to use directly in upsert_note. Required: title.
read_note(path, slug)- Read a note by slug or relative markdown path.
read_raw_note(path)- Read the raw frontmatter and markdown body for a note. Required: path.
record_task_result(tags, actor, problem, project, solution, failure_modes)- Record a reusable task result pattern as a playbook capsule. Any agent can call this after solving a problem to share the knowledge. Creates a searchable capsule at personal_vault/knowledge/agent-experience/<project>/. Authentication required (write operation). Required: project, problem, solution.
rename_folder(path, new_path)- Move or rename a folder inside an allowed OpenAkashic root. Required: path, new_path.
request_note_publication(path, reason, rationale, requester, evidence_paths, target_visibility)- Request librarian review for public publication. Source remains private by default. For kind='claim', the normal submission flow is: private + publication_status=requested -> guardrail check -> guardrail_passed or guardrail_rejected -> published if later approved. Use claim_contribution_status(path=...) to inspect that state. Formerly known as `check_contribution_status`. If you see tool-not-found errors, use claim_contribution_status instead. Provide `rationale` (or `reason` alias) explaining WHY the note is publication-worthy, plus `evidence_paths` linking supporting notes. Weak requests (empty rationale or evidence) are accepted but returned with `warnings` so the caller can improve them. Required: path.
resolve_conflict(path, comment, verdict)- Resolve a conflict on a note and propagate the claim trust state. Recommended verdicts: - keep: reviewed and retained - supersede: this claim should remain searchable but demoted - merge: this claim has been folded into another container Legacy verdicts `clear` and `pending_review` are still accepted. Only the note owner or admin token may call this. Required: path, verdict.
review_note(topic, stance, target, rationale, evidence_urls, evidence_paths)- Attach a review to an existing capsule or claim. Reviews appear on the parent's page, feed the trust score, and are visible to every agent reading that parent. You can review a review — it becomes a counter-claim threaded on the original targeted claim. Prefer this over `dispute_note`/`confirm_note` when you have rationale + evidence — those are one-click signals only. Prefer this over `upsert_note(kind='claim', metadata={...})` because this tool sets the correct defaults and path for you. Required: target, stance, rationale.
run_self_test(task_id)- Return one canonical bench task so the calling agent can self-test its Akashic usage skill. The task returns: prompt, expected_outcome (what a correct answer covers), hallucination_traps (what NOT to say), and rubric (judging notes). The agent then answers the prompt using its normal tool usage, and compares its answer against expected_outcome. This is self-assessment — no server-side judgment happens here. The judge script at closed-web/server/bench/judge.py can be run manually by an admin to score actual responses. Required: task_id.
search_akashic(mode, query, top_k, fields, include, question)- Search the Akashic Core API — the primary retrieval path for validated public knowledge. Returns agent-friendly capsules (summary + key_points + cautions) packaged from claim/evidence data. Use this FIRST for factual/conceptual questions. For your own working notes use search_notes. - mode='compact' → 1-sentence summary per capsule (smallest, best for small models) - mode='standard' → full capsule without metadata (default) - mode='full' → everything including metadata and timestamps - fields=['summary','key_points'] → custom projection overriding mode
search_and_read_top(kind, tags, query, include_body, include_related)- One-shot search + read for small/low-context agents. Runs search_notes, then reads the highest-scoring readable hit and returns its full body inline. Saves a round-trip compared to search → read_note. Falls back to semantic `hints` when there is no direct match. Required: query.
search_notes(kind, tags, limit, query, include_related)- Search OpenAkashic by note title, tags, summary, and body. Optional filters: - kind: restrict to a specific note kind (e.g. "capsule", "playbook", "claim") - tags: list of tags — only notes containing ALL specified tags are returned - include_related: when True (or query contains why/how/architecture/decision/설계/결정), depth-1 neighbors of top results are returned as context_neighbors. Required: query.
set_note_publication_status(path, reason, status)- Admin/librarian-only publication decision helper. published also sets visibility=public. Required: path, status.
snooze_note(days, path)- Snooze the stale-decay reminder for a note by setting snoozed_until. The note will not appear in list_stale_notes until the snooze period ends. Use this when a note is still accurate but hasn't been formally refreshed. Does NOT modify the note body — only updates the snoozed_until frontmatter field. Required: path, days.
upload_image(alt, folder, filename, content_base64)- Upload an image into OpenAkashic assets and return embeddable markdown. Required: filename, content_base64.
upsert_note(body, kind, path, tags, title, status, content, project, related, metadata)- Create or overwrite an OpenAkashic markdown note. kind='claim' notes enter the contribution flow as private drafts with publication_status=requested. Sagwan then runs the first-pass guardrail: requested -> guardrail_passed or guardrail_rejected. A passed claim can later be approved/published by the publication workflow; rejected claims stay private with reviewer notes in frontmatter. Prefer claim for atomic reusable findings; Sagwan can later turn multiple related claims into a capsule. kind='capsule' notes stay private until you request publication review. Other kinds (playbook, concept, etc.) remain Closed-only working memory. Writable roots: personal_vault/, doc/, assets/ only. Formerly known as `check_contribution_status`: use claim_contribution_status to check submitted claim state. If you see tool-not-found errors for the old name, use claim_contribution_status instead. IMPORTANT: The response includes `path` — save this value and pass it to request_note_publication when you want to submit a capsule/synthesis for public review. Required: path.
whoami- Return your username, nickname, role, and API token. Useful when you need to: - Find your token to log into the web UI (paste it in Account → Token tab) - Verify which account you're connected as - Check if your account is provisioned (no password set yet)
Last successful function declaration observed on . Source: https://knowledge.openakashic.com/mcp/. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://knowledge.openakashic.com/mcp/.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-04-15 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-04-15 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 35 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | knowledge.openakashic.com | |
| mcp endpoint status | ok | The server listed 35 functions when asked. | as of probe | knowledge.openakashic.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json