Data Olympus

Install

Pick your client. Read the repository before you give any tool access to your data.

About

Use cases: knowledge-base, documentation

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Tools

13 read · 5 write · 2 delete

Secrets

None asked for

Install scripts

None found

Runs as

Python package

Tools (20)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• kb_auditKB Auditread-only

  Return recent audit events, most-recent first. Optional filters: since (unix ts), agent (agent_identity), status (event status).

• kb_bootstrap_projectKB Bootstrap Project

  Bootstrap a new workspace/component. Only valid when status=absent or partial. High confidence commits atomically; low confidence enqueues pending.

• kb_cleanup_planKB Cleanup Planread-only

  Read-only. Classify local project-repo docs against KB content for this workspace/component and return thin-pointer replacements for duplicates. The agent applies confirmed edits locally; the server writes nothing. Use this when migrating a workspace's local docs into the KB by identifying redundant content; use `kb_propose_edit` or `kb_propose_memory` instead when you are ready to write the actual KB content.

• kb_complianceKB Complianceread-only

  Aggregate enforcement events (consult / gate_*) overall and per agent. Use this to review enforcement posture across agents for a reporting period; use `kb_audit` instead when you need the raw event log or per-event details.

• kb_consultKB Consult

  Record a consultation for (source_session, workspace) and return the governing rules for the intent. Call before code/architectural work. trigger is 'explicit' (default: a deliberate consult, clears the gate) or 'prompt_hook' (an installer auto-consult: audited, never clears). Retrieval is hard-filtered to the in-force class (active/accepted/ approved, within its validity window, and never a memory-inbox doc): an unreviewed proposed memory, a retired/superseded decision, an expired doc, or a legacy/forged inbox file is never returned as a governing rule. pending_actions, when present, lists …

• kb_curateKB Curateread-only

  List in-force governed documents that are due for review, most overdue first. Advisory only: this tool RECOMMENDS -- it never proposes, edits, promotes, or demotes anything, and takes no confirmation or approval action of its own. Use it to find what to look at next, then act through `kb_get` (to read the document) and `kb_propose_edit` (to actually update it) as separate, deliberate steps. A document is review-due when its `recheck_by` date has passed, or (when the operator has set `KB_REVIEW_DUE_AFTER_DAYS` and no `recheck_by` overrides it) when its `last_verified` is older than that many d…

• kb_gate_checkKB Gate Check

  Return a verdict (allow | consult_required) for a pending code action. Governed actions require a fresh consultation on record. Records each check to the audit log (non-destructive; `readOnlyHint=false` is intentional). Use this in a PreToolUse hook to verify a specific pending action before execution; use `kb_consult` instead when proactively reading governing rules at the start of a session rather than checking individual actions.

• kb_getKB Get Documentread-only

  Retrieve a document by id (STD-U-001, ADR-002, T-NNN, etc.). Returns the full content markdown plus metadata. Use this when you have a specific id (from `kb_search` results or session memory); use `kb_search` instead when you need to find a document by topic. Always resolves regardless of expiry (ids never dangle): an expired document is still returned, with its full `validity` object and a computed `freshness` indicator (`stale`/`expired`/`upcoming`). Derivation cues (ids only, for a person to review; nothing is filtered or demoted because of them): `derived_from` lists the documents this o…

• kb_get_pendingKB Get Pendingread-only

  Read back a parked proposal's own text. Returns the postimage to the principal that made the proposal, or to one that could resolve it. The content is PENDING: it is not in force and governs nothing until approved.

• kb_healthKB Healthread-only

  Return service health: kb_commit, index_built_at, staleness, degraded flag, and write-side state (pending_count, push_queue_size, last_index_*). verbose: False (default) returns a token-compact shape that keeps the core snapshot and OMITS diagnostic fields that are null/empty (e.g. last_index_error, remote_head_sha when unset). verbose=True returns every field including the nulls. pending_actions, when present, lists open maintenance items (missing `status` fields, recently-expired/expiring-soon docs) computed at the last index build; it is omitted when the corpus is clean. Surface it to the…

• kb_listKB List Documentsread-only

  List doc ids in the given tier (and optional category), ordered by id. Use this to enumerate all docs in a tier when auditing coverage or iterating a full category; use `kb_search` when you need topic-based discovery, or `kb_outline` for counts without the full id list. verbose: False (default) drops per-entry `path` (fetch via kb_get(id)) and omits a null category. verbose=True restores the full shape with paths.

• kb_list_pendingKB List Pendingread-only

  List currently pending proposals awaiting operator decision.

• kb_onboarding_statusKB Onboarding Statusread-only

  Compute onboarding status for a workspace + optional component. State is one of: absent, partial, onboarded, rename_candidate. Use this to check whether a workspace is registered in the KB and what documentation is missing; use `kb_search` or `kb_get` instead when you need to read existing KB content for the workspace rather than check its registration state.

• kb_outlineKB Outlineread-only

  Return the tree of tiers and categories with doc counts. Use this to get a structural map of the KB before tier exploration; use `kb_search` when you have a topic query, or `kb_list` when you know the tier and want the document id list. verbose: kb_outline is already lean, so compact and full modes return the same shape; the parameter exists for interface consistency.

• kb_propose_editKB Propose Editcan change or delete data

  Propose an edit to an existing (or new) markdown file under an indexed tier. High confidence auto-commits + queues for push; low confidence enters the pending queue for operator review. evidence: optional supporting-context strings (max 10 items, 500 chars each), persisted in pending meta / audit events and surfaced by kb_pending (not rendered into the postimage: unlike kb_propose_memory, the postimage here is caller-supplied verbatim). contest: optional contest declaration indicating intent to dispute existing indexed knowledge, specifying contradicted document IDs and optional contest reas…

Signals

Stars

30

Forks

7

Open issues

37

Weekly downloads

1,122

Last commit

Oct 19, 2026 (11 days ago)

Last release

Oct 25, 2026 (5 days ago)

Last package publish

Oct 20, 2026 (10 days ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name

io.github.knaisoma/data-olympus

Version

0.11.4

Auth

No auth

Packages

pypi data-olympus

License

Apache-2.0

Repository

github.com/knaisoma/data-olympus

Website

github.com/knaisoma/data-olympus

First seen

Oct 24, 2026

Last checked

Oct 26, 2026

Source

Official MCP Registrygithub-graphql