Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Nothing to run from here
MCAI Knowledge Base 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.
95/100
trust score
12
downloads a day
local
runs on your machine
364
downloads in 30d
What it does
MCAI Knowledge Base turns the Meta-Consciousness Theory into machine-readable assets: 64 term definitions, 122 curated Q&A pairs, 270 typed relations and 213 source citations, each traceable to a document and a character range.
Five MCP tools:- mcai_answer — definition with citations (or citations-only mode)- mcai_concept — full entry with sources, relations and disambiguation- mcai_search — normalized search across terms, aliases and definitions- mcai_related — core/derived relations, with mention edges optional- mcai_list — catalog of all terms
Runs locally over stdio: uvx --from mcai-knowledge mcai-mcp. A read-only Streamable HTTP endpoint is also available at https://mcai-mcp-public-338698-11-1316838521.sh.run.tcloudbase.com/mcp (no token needed).
Content CC BY-NC-SA 4.0; code MIT.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user mcai-knowledge-base-mcp '--' uvx --from mcai-knowledge mcai-mcp
# 2 — ask your agent for something these tools do
# mcai-knowledge, mcai_concept, mcai_search and 7 more
MCAI Knowledge Base costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publisher
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 MCAI Knowledge Base 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.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user mcai-knowledge-base-mcp '--' uvx --from mcai-knowledge mcai-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take MCAI_HOME (Optional project directory containing data/kb.json; the bundled knowledge base is used when unset.) if you want to set it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
回答关于元意识学说的整句问题，返回权威定义、原文引证与相关概念。适合：用户用自然语言提问、且没有明确指定只要某一条词条时，例如“什么是元意识”“元识和元知是什么关系”“序生智能体如何解释 AI 涌现”。分工：若已知确切术语、想拿完整词条（别名、出处、引证、关系），用 mcai_concept；若不确定术语写法，先用 mcai_search；只看目录用 mcai_list；只看关系用 mcai_related。边界：只基于本知识库语料回答，未收录的概念会返回 type=none；不要据此推断、补写或引入库外语义。
No parameter schema on file.
按术语名、别名或 slug 获取单个概念的完整词条：定义、别名、出处、文献引证与关系。适合在已经知道术语名、需要完整资料时使用。分工：不确定术语写法时先用 mcai_search；整句问题用 mcai_answer；只看关系用 mcai_related。边界：只返回本知识库已收录的词条，查不到时返回明确错误。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| term | string | yes | 精确的术语名、别名或 slug，例如 元意识 / MCAI / meta-consciousness；不确定写法时先用 mcai_search。 |
在术语库中检索概念，支持中文关键词、英文词与别名，可按体系过滤。适合用户只记得大概说法、或需要先确认术语名称时使用。分工：拿到术语名后用 mcai_concept 取完整词条；整句问题用 mcai_answer；看全目录用 mcai_list。边界：只做词条匹配，不做语义推理。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | 检索关键词（建议 2–20 字，不要传整句），支持中文、英文或别名，例如 元意识 / progenerative agent / 序生。 |
| limit | integer | no | 返回条数上限，默认 8，范围 1–30。 |
| category | string | no | 按体系过滤，取值必须是：元意识体系 / 本体论模型 / 序生体系 / 元子社会；留空则返回全部 |
获取一个概念的关系子图（含衍生关系），用于解释概念之间的因果、结构与层级。适合回答“A 和 B 有什么关系”“这个概念的上位/下位概念是什么”。分工：需要完整词条用 mcai_concept；需要整句解释用 mcai_answer；需要找词用 mcai_search。边界：只返回库内已登记的关系，没有关系时明确说明。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| term | string | yes | 中心术语名，必须是库内已收录的术语，例如 元意识 / 序生智能体；不确定时先用 mcai_search。 |
| depth | integer | no | 关系展开深度：1 只取直接关系，2 取两跳；默认 1。 |
列出知识库中的全部术语（可按体系过滤），用于了解覆盖范围、或让用户从目录中选择。当用户问“这套学说有哪些概念”“你们收录了什么”时使用。分工：按关键词找词用 mcai_search；要某条完整词条用 mcai_concept。边界：只返回术语名与分类，不返回定义全文。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | 按体系过滤，取值必须是：元意识体系 / 本体论模型 / 序生体系 / 元子社会；留空则返回全部 |
用元意识学说的定义解释一个术语，要求区分同名概念。
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 MIT
- 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 MCAI Knowledge Base 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 95 / 100
Release 0.3.2 · scanned 1 Nov 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 score95
Findings2 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationnone
Surface digest10c35940a9591ee01ab0ed6d2241127597c043e62b4ed2a792b8174204a26f11
Score vectorthreat 100 → client 95
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | none | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read | −2 |
| 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 surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
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. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can start a fixed program (a process-spawning capability, not arbitrary code execution)
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 digest10c35940a9591ee0
Scanned2026-11-01
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.3.2. Pin a release below and the command asks for exactly that one.
0.3.2
1 Nov 2026
latestNo release note was published with this version.
0.3.1
1 Nov 2026
No release note was published with this version.
0.3.0
31 Oct 2026
No release note was published with this version.
0.2.9
31 Oct 2026
No release note was published with this version.
0.2.7
30 Oct 2026
No release note was published with this version.
0.2.6
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 MCAI Knowledge Base 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.