Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Nothing to run from here
Data Olympus is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
94/100
trust score
1
downloads a day
local
runs on your machine
190
downloads in 30d
What it does
Governance-grade knowledge-base format (OKF-compatible) plus CLI and single-writer MCP server
Quickstart
This package runs as a local HTTP server (Streamable HTTP), not over stdio, so a client cannot start it as a process. Start it in a terminal with uvx --from data-olympus data-olympus-mcp and keep it running, then add the address it listens on to your client as a remote server; that address is not recorded here, so there is no entry to copy.
Publishernot claimed
KNAll 1 server
knaisoma1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Data Olympus as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This package runs as a local HTTP server (Streamable HTTP), not over stdio, so a client cannot start it as a process. Start it in a terminal with uvx --from data-olympus data-olympus-mcp and keep it running, then add the address it listens on to your client as a remote server; that address is not recorded here, so there is no entry to copy.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Data Olympus or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 94 / 100
Release 0.11.1 · scanned 14 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score94
Findings11 threat · 2 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digestf22b6200774d4222705b624bfa9a8082e7129d83fb5c82886bc98c578559d6a3
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (20 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
8 of the 20 recovered tools are registered only when config.embeddings_enabled and embedder is not None is false (src/data_olympus/server.py:644) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
12 of the 20 recovered tools are registered only when not read_only holds (src/data_olympus/server.py:1075) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
No tool is registered unconditionally · (1) 8 only when config.embeddings_enabled and embedder is not None is false (src/data_olympus/server.py:644) · (2) 12 only when not read_only holds (src/data_olympus/server.py:1075) — typically when a key or option is configured. All 20 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| kb_health conditional (1) | no tags | |
| kb_outline conditional (1) | no tags | |
| kb_curate conditional (1) | no tags | |
| kb_search conditional (1) | no tags | |
| kb_get conditional (1) | no tags | |
| kb_list conditional (1) | no tags | |
| kb_onboarding_status conditional (1) | no tags | |
| kb_cleanup_plan conditional (1) | no tags | |
| kb_propose_memory conditional (2) | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| kb_propose_edit conditional (2) | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| kb_resolve_pending conditional (2) | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| kb_list_pending conditional (2) | no tags | |
| kb_get_pending conditional (2) | no tags | |
| kb_audit conditional (2) | no tags | |
| kb_session_recap conditional (2) | no tags | |
| kb_bootstrap_project conditional (2) | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| kb_consult conditional (2) | state-write | state-write: declares readOnlyHint: false |
| kb_gate_check conditional (2) | state-write | state-write: declares readOnlyHint: false |
| kb_compliance conditional (2) | no tags | |
| kb_record_event conditional (2) | state-write | state-write: declares readOnlyHint: false |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestf22b6200774d4222
Scanned2026-10-14
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.11.1. Pin a release below and the command asks for exactly that one.
0.11.1
9 Oct 2026
latestNo release note was published with this version.
0.11.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Data Olympus can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.