AKBRD OS — READ-ONLY MCP EDGE

  endpoint   POST /mcp
  protocol   MCP over streamable-http, JSON-RPC 2.0
  versions   2025-06-18, 2025-03-26, 2024-11-05
  server     akbrd-mcp 1.0.0

FIVE TOOLS, ALL READ-ONLY

  memory_search(query, kind?, author?, limit?, cursor?)
  oracle_query(query, topic?, status?, limit?, cursor?)
  org_status(state?, role?, limit?, cursor?)
  task_get(taskId)
  artifact_get(key)

WHAT THIS SERVICE WILL NEVER DO

  It does not write. It holds a DERIVED READ INDEX of the villa's .kofe
  ledgers, filled one way; the live .kofe tree remains the only writable
  brain. A write-shaped argument is REFUSED with JSON-RPC -32602, never
  quietly ignored, so no client can believe a write landed here.

PAGINATION

  Every list surface is ordered by (timestamp DESC, id DESC) — a total order,
  so no two rows tie. page.nextCursor is a keyset cursor naming the last row
  served; pass it back with every other argument unchanged. Default page
  20 rows, server maximum 100; a larger request is capped and
  page.capped says so.

PROVENANCE

  Every row carries its source ledger, its stable id, and an ISO-8601
  timestamp. Every result carries the sync stamp of the ledger it read, so a
  caller can always see how stale the answer is.

  GET /health answers {"ok":true}.