Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Nothing to run from here
Enhanciar — company brain 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.
12
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Ask your team's code, Slack and docs from any MCP client. Every answer cited to source. Early access
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http enhanciar-company-brain-mcp https://enhanciar.in/enhanciar/mcp/
# 2 — ask your agent for something these tools do
# list_pages, search_wiki, get_page and 9 more
Enhanciar — company brain costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ENAll 1 server
enhanciar1 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. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http enhanciar-company-brain-mcp https://enhanciar.in/enhanciar/mcp/Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add — but its publisher asks for a key of their own on every call.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
12 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.
List every wiki page the caller can see in the key's workspace. Returns a list of `{category, name, title} records — feed each one to get_page to fetch the full markdown body. Use this first when you want a directory view; for a specific question prefer query` which handles retrieval for you.
No parameter schema on file.
Substring search across the wiki pages in the key's workspace. Cheap and deterministic — no embedding required. Returns up to `limit (default 20, max 50) {category, name, title, snippet} hits. The snippet is a short window around the first match, safe to surface in chat as a citation preview. For semantic / natural-language questions prefer query`.
No parameter schema on file.
Fetch a single wiki page from the key's workspace. Args: category: One of `entities | concepts | people | decisions | sources | flows | infrastructure | tickets. name: Page slug (without .md extension), as returned by list_pages / search_wiki. Returns {category, name, content} — content is the full markdown body including YAML frontmatter. Returns
No parameter schema on file.
Ask Enhanciar a natural-language question grounded in the key's workspace. This is the high-level tool — use it for any "what does X do", "why did we choose Y", "where is Z handled" question. It runs the full retrieval + synthesis pipeline and returns the answer plus citations. Args: question: Natural-language question. model: Optional model id override (`gemini-2.5-flash, `g
No parameter schema on file.
Compute the blast radius of changing `target` in the key's workspace. Use this before editing code to see what a change ripples into: direct callers/callees, every affected file, the affected tests, the transitive dependency set, and example dependency paths with per-path facts (hops, dependents at the endpoint, whether it lands in a test). There is deliberately no risk score. There was one —
No parameter schema on file.
Return the community/knowledge graph manifest for visualisation. Useful when the calling agent wants the high-level structure of the key's workspace (clusters, hub nodes, cross-references) rather than the contents of any one page. Returns `{nodes, edges, communities, stats} — exact shape mirrors the /api/wiki/graph` REST endpoint.
No parameter schema on file.
List the repos ingested into the key's workspace. Returns `{full_name, branch, last_ingested_at} records. Use this when the agent needs to know what context is available before asking a question. Reads what ingest actually recorded for this namespace: repos.json (the repo→clone map every other read path resolves through) plus the per-repo _state` files that carry the branch and the las
No parameter schema on file.
List the compiled skills (recurring procedures) in the key's workspace. Skills are agent-executable SKILL.md pages mined from that workspace's wiki by the skills compiler. Returns `{name, title, description, confidence, last_compiled, sources} records — feed a name to get_skill` for the full markdown. Empty list = nothing compiled yet (the user can run a compile from Enhanciar's UI or A
No parameter schema on file.
Fetch one compiled skill by name (slug from `list_skills). Returns {name, markdown, meta} — markdown is the full agent-executable SKILL.md content (frontmatter + steps), meta is the parsed frontmatter. Includes an error` key when the skill doesn't exist (with the available names).
No parameter schema on file.
Return the "living map of how the company works" for the key's workspace. A graph of process nodes (compiled skills), the external systems they touch (GitHub, Slack, Jira, …), the wiki docs they were derived from, and team groups — with derived_from / uses / references edges. Use this when the agent wants the high-level operational structure rather than one skill's steps.
No parameter schema on file.
List the key's workspace's proposed actions (the approval queue). Read-only. Optionally filter by `status (proposed / approved / executing / done / failed / dismissed). Returns {id, action_type, status, source, title, source_doc_id, external_id}` per proposal. NOTE: MCP can read and PROPOSE actions but deliberately cannot approve or execute them — a human approves every action in the app U
No parameter schema on file.
Propose a new action for human approval (does NOT execute it). `action_type is a registered executor id (e.g. jira.create_issue, linear.create_issue, github.create_issue). The proposal lands in the key's workspace's approval queue where a person picks the target and approves it — approve/execute are intentionally NOT exposed over MCP. Returns the created `{id, action_type, status}
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 Enhanciar — company brain 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: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.2.
1.0.2
undated
latestNo release note was published with this version.
—
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 Enhanciar — company brain 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.