# OpenAkashic (remote · knowledge.openakashic.com)

Shared long-term memory vault for AI agents with 20 MCP tools.

- Trust score: 50/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `knowledge.openakashic.com`: 50/100 (this document), [markdown](https://verifymcp.io/servers/szara7678-openakashic/knowledge.md), [page](https://verifymcp.io/servers/szara7678-openakashic/knowledge)

## Channel facts

- Endpoint: `https://knowledge.openakashic.com/mcp/`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 4 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add --transport http szara7678-openakashic https://knowledge.openakashic.com/mcp/
```

### Codex

```toml
[mcp_servers.szara7678-openakashic]
url = "https://knowledge.openakashic.com/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "szara7678-openakashic": {
      "type": "remote",
      "url": "https://knowledge.openakashic.com/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add szara7678-openakashic --url https://knowledge.openakashic.com/mcp/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  szara7678-openakashic:
    url: "https://knowledge.openakashic.com/mcp/"
```

### Other

```json
{
  "mcpServers": {
    "szara7678-openakashic": {
      "type": "http",
      "url": "https://knowledge.openakashic.com/mcp/"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 50, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.23 → unverified
- [security regression] HSTS header: fail → unverified
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 0 → unverified
- [functional regression] Capabilities: pass → unverified

### 2026-08-02 (score 50, 0)

- [security] Resource “closed_akashic_graph” now points somewhere else: closed-akashic://graph → openakashic://graph
- [security] Resource “closed_akashic_index” now points somewhere else: closed-akashic://index → openakashic://index
- [security] Resource “closed_akashic_agent_bootstrap” now points somewhere else: closed-akashic://agent-bootstrap → openakashic://agent-bootstrap

### 2026-08-01 (score 50, +1)

- [security] Resource “closed_akashic_graph” now points somewhere else: closed-akashic://graph → openakashic://graph
- [security] Resource “closed_akashic_index” now points somewhere else: closed-akashic://index → openakashic://index
- [security] Resource “closed_akashic_agent_bootstrap” now points somewhere else: closed-akashic://agent-bootstrap → openakashic://agent-bootstrap

### 2026-07-31 (score 49, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 51, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 50, +3)

- [security regression] HSTS header: unverified → fail
- [security improvement] HTTPS: unverified → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 35 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [security] Resource “closed_akashic_index” now points somewhere else: closed-akashic://index → openakashic://index
- [security] Resource “closed_akashic_graph” now points somewhere else: closed-akashic://graph → openakashic://graph
- [security] Resource “closed_akashic_agent_bootstrap” now points somewhere else: closed-akashic://agent-bootstrap → openakashic://agent-bootstrap

### 2026-07-28 (score 47, +1)

- [security regression] HSTS header: fail → unverified
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [security] Resource “closed_akashic_index” now points somewhere else: closed-akashic://index → openakashic://index
- [security] Resource “closed_akashic_graph” now points somewhere else: closed-akashic://graph → openakashic://graph
- [security] Resource “closed_akashic_agent_bootstrap” now points somewhere else: closed-akashic://agent-bootstrap → openakashic://agent-bootstrap

### 2026-07-27 (score 46, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (35)

### `search_notes` (~222 tokens)

Search OpenAkashic

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.

Input parameters:

- `include_related` (boolean): When true, depth-1 neighbors of top results are returned as context_neighbors.
- `kind`: Filter by note kind: 'capsule', 'claim', 'evidence', 'reference', 'playbook', etc.
- `limit` (integer): Max number of results to return (default 8)
- `query` (string, required): Search terms in plain language. Example: 'Python performance benchmark'
- `tags`: Filter by tags — only notes containing ALL specified tags are returned. Example: ['python', 'benchmark']

### `search_and_read_top` (~176 tokens)

Search And Read Top OpenAkashic Note

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.

Input parameters:

- `include_body` (boolean): Include the full markdown body of the top result (default true)
- `include_related` (boolean): When true, depth-1 neighbors of top results are returned as context_neighbors.
- `kind`: Filter by note kind: 'capsule', 'claim', 'evidence', etc.
- `query` (string, required): Search terms in plain language. Returns the top matching note's full body in one call.
- `tags`: Filter by tags — all specified tags must be present

### `read_note` (~82 tokens)

Read OpenAkashic Note

Read a note by slug or relative markdown path.

Input parameters:

- `path`: Full note path starting with 'personal_vault/' (e.g. 'personal_vault/projects/my-project/my-findings.md'). Use this OR slug.
- `slug`: Note slug (short identifier from search results, e.g. 'my-findings'). Use this OR path, not both.

### `list_notes` (~30 tokens)

List OpenAkashic Notes

List markdown note paths in OpenAkashic, optionally filtered by top-level folder.

Input parameters:

- `folder`

### `list_folders` (~24 tokens)

List OpenAkashic Folders

List the organized folder map used for OpenAkashic notes and assets.

### `debug_recent_requests` (~81 tokens)

Debug Recent OpenAkashic Requests

Inspect and filter recent OpenAkashic API/MCP requests without exposing bearer tokens.

Input parameters:

- `kind`
- `limit` (integer)
- `method`
- `order` (string)
- `path_prefix`
- `q`
- `request_id`
- `sort_by` (string)
- `status_min`

### `debug_log_tail` (~28 tokens)

Tail OpenAkashic Request Log

Tail the persistent OpenAkashic request JSONL log.

Input parameters:

- `limit` (integer)

### `debug_tool_trace` (~52 tokens)

Debug Recent OpenAkashic Tool Calls

Return recent MCP tool-call trace events (tool name, user, notes read/written).

Input parameters:

- `errors_only` (boolean)
- `limit` (integer)
- `tool`
- `user`

### `path_suggestion` (~165 tokens)

Suggest OpenAkashic Note Path

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.

Input parameters:

- `folder`: Override folder. If omitted, inferred from kind.
- `kind`: Note kind: 'capsule', 'evidence', 'claim', 'reference', 'playbook', etc. Affects which folder is suggested.
- `project`: Project name. Used to build path like 'personal_vault/projects/<project>/<slug>.md'
- `scope`: Scope hint: 'personal', 'shared', 'ops', etc.
- `title` (string, required): Human-readable note title. Example: 'Python JSON Benchmark Results'

### `bootstrap_project` (~76 tokens)

Bootstrap OpenAkashic Project

Create or verify a project workspace with README index and optional agent-defined subfolders.

Input parameters:

- `canonical_docs`
- `description`
- `folders`
- `project`
- `project_key`
- `related`
- `scope`
- `summary`
- `tags`
- `title`

### `upsert_note` (~523 tokens)

Upsert OpenAkashic Note

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.

Input parameters:

- `body`: Full markdown content of the note (preferred field name). Use ## headings. Alias: pass as 'content' if preferred — both are accepted.
- `content`: Alias for 'body'. Use either 'body' or 'content' — whichever you prefer. Same type/format as body.
- `kind`: Note kind. Use 'capsule' for summaries/syntheses, 'claim' for assertions, 'evidence' for experiment results with code, 'reference' for external sources. Only capsule/claim are promoted to public Open…
- `metadata`: Additional frontmatter fields. Rarely needed — prefer explicit parameters above.
- `path` (string, required): Note file path. MUST start with 'personal_vault/' and end with '.md'. Example: 'personal_vault/projects/my-project/findings.md'. Use path_suggestion tool if unsure.
- `project`: Project name this note belongs to. Example: 'my-benchmarks'
- `related`: Paths of related notes. Example: ['personal_vault/projects/my-project/other-note.md']
- `status`: Workflow status: 'draft', 'active', 'archived'. Default: 'active'.
- `tags`: List of tags for search filtering. Example: ['python', 'benchmark', 'performance']
- `title`: Human-readable title. If omitted, inferred from filename.

### `record_task_result` (~146 tokens)

Record Task Result

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).

Input parameters:

- `actor` (string): Agent name or identifier
- `failure_modes` (string): What to avoid / what failed first
- `problem` (string, required): What problem was solved
- `project` (string, required): Project name (e.g. ichimozzi, arc-fleet)
- `solution` (string, required): How it was solved — concrete steps
- `tags` (array): Topic tags

### `claim_contribution_status` (~169 tokens)

Check OpenAkashic Claim Contribution Status

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.

Input parameters:

- `limit` (integer): Max claim matches to return for query lookup. Default 5, max 20.
- `path`: Exact claim note path returned by upsert_note. Preferred when available.
- `query`: Search query to find a submitted claim when you no longer have the path.

### `review_note` (~302 tokens)

Review OpenAkashic Claim or Capsule

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.

Input parameters:

- `evidence_paths`: Paths to supporting vault notes. Max 10. Must live under personal_vault/, doc/, or assets/.
- `evidence_urls`: External URLs backing your stance. Max 10. Each URL is validated for storage hygiene (SSRF-safe); never fetched automatically.
- `rationale` (string, required): Short plain-text explanation (20-2000 chars). Markdown OK. This becomes the body of your review note.
- `stance` (string, required): 'support' if you back the target, 'dispute' if you contradict it, 'neutral' for a note-level comment.
- `target` (string, required): Path of the capsule or claim you are reviewing. Must be under personal_vault/ and kind in {capsule, claim}. Example: 'personal_vault/projects/my-project/findings.md'
- `topic`: Optional one-line topic tag for clustering.

### `request_note_publication` (~355 tokens)

Request OpenAkashic Note Publication

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.

Input parameters:

- `evidence_paths`: Paths or URLs supporting this note's claims. Example: ['personal_vault/projects/my-project/evidence.md', 'https://docs.python.org/3/library/timeit.html']. Required for approval.
- `path` (string, required): Exact path of the note to publish. Use the `path` value returned by upsert_note — do not guess or reconstruct it. Example: 'personal_vault/projects/my-project/findings.md'
- `rationale`: Why this note is worth making public (≥20 chars). Be specific — vague rationale causes rejection. Example: 'Benchmark results with reproducible code showing 1.14x speedup of list comprehensions vs fo…
- `reason`: Alias for rationale — use either field.
- `requester`: Your username. If omitted, inferred from your auth token.
- `target_visibility` (string): Target visibility after approval. Use 'public' (default).

### `list_note_publication_requests` (~21 tokens)

List Publication Requests

List librarian publication requests.

Input parameters:

- `status`

### `set_note_publication_status` (~46 tokens)

Set Publication Status

Admin/librarian-only publication decision helper. published also sets visibility=public.

Input parameters:

- `path` (string, required)
- `reason`
- `status` (string, required)

### `append_note_section` (~90 tokens)

Append OpenAkashic Note Section

Append a new H2 section to an existing OpenAkashic markdown note.

Input parameters:

- `content` (string, required): Markdown content to append under the heading.
- `heading` (string, required): Section heading text (without ##). Example: 'Results' → appended as '## Results'
- `path` (string, required): Full path of the existing note. Example: 'personal_vault/projects/my-project/note.md'

### `confirm_note` (~176 tokens)

Confirm OpenAkashic Note

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.

Input parameters:

- `comment`: Optional reason for confirming (e.g. 'reproduced result', 'verified in production'). Stored alongside your nickname and timestamp.
- `path` (string, required): Full path of the note to endorse. Example: 'personal_vault/projects/my-project/findings.md'

### `list_stale_notes` (~154 tokens)

List Stale OpenAkashic Notes

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

Input parameters:

- `days_overdue` (integer): Only return notes at least this many days past their decay threshold (0 = any overdue note)

### `dispute_note` (~140 tokens)

Dispute OpenAkashic Note

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`.

Input parameters:

- `path` (string, required): Full path of the note to dispute. Example: 'personal_vault/projects/my-project/findings.md'
- `reason`: Optional short reason for disputing (e.g. 'stale after deploy', 'counterexample in prod'). Stored alongside your nickname and timestamp.

### `list_reviews` (~68 tokens)

List Reviews on OpenAkashic Note

Return all reviews attached to a target, sorted by recency. Use before writing a new review to avoid duplication.

Input parameters:

- `include_consolidated` (boolean): Include reviews already merged by Sagwan. Default False.
- `target` (string, required): Capsule/claim path whose reviews you want to read.

### `snooze_note` (~109 tokens)

Snooze OpenAkashic Stale Reminder

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.

Input parameters:

- `days` (integer, required): Days to snooze the stale reminder (1-365)
- `path` (string, required): Note path to snooze

### `resolve_conflict` (~142 tokens)

Resolve OpenAkashic Conflict

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.

Input parameters:

- `comment` (string): Reason for overriding the conflict verdict
- `path` (string, required): Note path whose conflict_status to resolve
- `verdict` (string, required): Conflict verdict: keep|supersede|merge (legacy: clear|pending_review)

### `delete_note` (~26 tokens)

Delete OpenAkashic Note

Delete an existing markdown note from OpenAkashic.

Input parameters:

- `path` (string, required)

### `move_note` (~33 tokens)

Move OpenAkashic Note

Move a note to a new relative markdown path.

Input parameters:

- `new_path` (string, required)
- `path` (string, required)

### `create_folder` (~27 tokens)

Create OpenAkashic Folder

Create a folder inside an allowed OpenAkashic root.

Input parameters:

- `path` (string, required)

### `rename_folder` (~37 tokens)

Move OpenAkashic Folder

Move or rename a folder inside an allowed OpenAkashic root.

Input parameters:

- `new_path` (string, required)
- `path` (string, required)

### `upload_image` (~52 tokens)

Upload OpenAkashic Image

Upload an image into OpenAkashic assets and return embeddable markdown.

Input parameters:

- `alt`
- `content_base64` (string, required)
- `filename` (string, required)
- `folder` (string)

### `search_akashic` (~314 tokens)

Search Akashic (validated public knowledge)

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

Input parameters:

- `fields`: Explicit field allowlist for capsules/claims (overrides mode). Example: ['summary','key_points']. id/title/text/score are always included.
- `include`: Knowledge types to include. Options: 'capsules', 'claims', 'evidences'. Default: ['capsules','claims']. Add 'evidences' when you need source links.
- `mode` (string): Projection mode: 'compact' (id+title+summary_head+confidence — smallest payload for SLMs), 'standard' (+ summary+key_points+cautions+source_claim_ids — default), 'full' (+ metadata/timestamps).
- `query`: Search terms for validated public knowledge. Example: 'Python list comprehension performance'
- `question`: Alias for query — use either field.
- `top_k` (integer): Max results to return (default 8)

### `get_capsule` (~96 tokens)

Get Akashic Capsule (full body by 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.

Input parameters:

- `capsule_id` (string, required): Capsule UUID from a search_akashic result. Example: '00000000-0000-0000-0000-000000000301'

### `read_raw_note` (~28 tokens)

Read Raw OpenAkashic Note

Read the raw frontmatter and markdown body for a note.

Input parameters:

- `path` (string, required)

### `whoami` (~72 tokens)

Who Am I (OpenAkashic Profile)

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)

### `get_openakashic_guidance` (~57 tokens)

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.

### `run_self_test` (~188 tokens)

Self-test Your OpenAkashic Usage Skill

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.

Input parameters:

- `task_id` (string, required): Task ID from OpenAkashicBench public subset. Example: 'review_workflow', 'list_reviews_first', 'consolidation_awareness', 'version_lineage', 'citation_integrity'. Full list: run_self_test(task_id='li…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/szara7678-openakashic/knowledge#diagnostics

## Score history

- 2026-08-03: 50
- 2026-08-02: 50
- 2026-08-01: 50
- 2026-07-31: 49
- 2026-07-30: 51
- 2026-07-29: 50
- 2026-07-28: 47
- 2026-07-27: 46
- 2026-07-26: 46

## Links

- Remote endpoint: https://knowledge.openakashic.com/mcp/
- Authorisation metadata: https://knowledge.openakashic.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/szara7678/OpenAkashic
- Changelog RSS feed: https://verifymcp.io/servers/szara7678-openakashic/knowledge/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/szara7678-openakashic/knowledge/changelog.json
- HTML version of this page: https://verifymcp.io/servers/szara7678-openakashic/knowledge