# Enhanciar — company brain (remote · enhanciar.in)

Ask your team's code, Slack and docs from any MCP client. Every answer cited to source. Early access

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `enhanciar.in`: 64/100 (this document), [markdown](https://verifymcp.io/servers/in-enhanciar-enhanciar/enhanciar-mcp.md), [page](https://verifymcp.io/servers/in-enhanciar-enhanciar/enhanciar-mcp)

## Channel facts

- Endpoint: `https://enhanciar.in/enhanciar/mcp/`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1743 tokens (~145/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Enhanciar — company brain MCP server?

Enhanciar — company brain is a hosted endpoint at https://enhanciar.in/enhanciar/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http in-enhanciar-enhanciar 'https://enhanciar.in/enhanciar/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "in-enhanciar-enhanciar": {
      "url": "https://enhanciar.in/enhanciar/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "in-enhanciar-enhanciar": {
      "type": "http",
      "url": "https://enhanciar.in/enhanciar/mcp/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.in-enhanciar-enhanciar]
url = "https://enhanciar.in/enhanciar/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "in-enhanciar-enhanciar": {
      "type": "remote",
      "url": "https://enhanciar.in/enhanciar/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add in-enhanciar-enhanciar --url 'https://enhanciar.in/enhanciar/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  in-enhanciar-enhanciar:
    url: "https://enhanciar.in/enhanciar/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "in-enhanciar-enhanciar": {
      "Transport": "http",
      "Url": "https://enhanciar.in/enhanciar/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add in-enhanciar-enhanciar -t streamable-http -u 'https://enhanciar.in/enhanciar/mcp/'
```

### Other

```json
{
  "mcpServers": {
    "in-enhanciar-enhanciar": {
      "type": "http",
      "url": "https://enhanciar.in/enhanciar/mcp/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 64)

First indexed and scored.

## MCP tools (12)

### `list_pages` (~79 tokens)

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.

Output parameters:

- `result` (array)

### `search_wiki` (~106 tokens)

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``.

Input parameters:

- `limit` (integer)
- `query` (string, required)

Output parameters:

- `result` (array)

### `get_page` (~127 tokens)

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 ``{error: "..."}``
if the page doesn't exist.

Input parameters:

- `category` (string, required)
- `name` (string, required)

### `query` (~261 tokens)

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``,
        ``gpt-4o``, ``claude-sonnet-4-5``, etc.). If omitted the
        saved default is used — the workspace's in a team workspace,
        the caller's own in a personal one.

Returns ``{answer, sources, model}`` — ``sources`` is a list of
\``{category, name, url}`` citations the LLM grounded its answer
in. Surface them to the human so they can verify. When the workspace
has nothing ingested at all you get ``{answer, empty_brain: true}``
and no sources: that is a statement about the workspace, not a failed
search, so rephrasing the question will not change it.

Input parameters:

- `model`
- `question` (string, required)

### `impact` (~246 tokens)

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 — thresholds on the
transitive count — and it was a verdict the caller could not check or
argue with. The counts it was computed from are all here; judge from
those.

Args:
    target: A graph node id, wiki page name, file path
        (``micrograd/engine.py``), or a function fqn (``engine.py::func``).
    depth: How many hops to traverse the call graph (default 2).

Returns the impact dict — ``{target, label, found, direct_callers,
direct_callees, affected_files, affected_tests, transitive_nodes,
transitive_count, paths, path_facts}``.

Input parameters:

- `depth` (integer)
- `target` (string, required)

### `get_graph` (~82 tokens)

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.

### `list_repos` (~220 tokens)

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 last run's
timestamp.

It used to read a Firestore subcollection ``users/{uid}/repos``, which
was wrong twice over. It was keyed by the person rather than the
workspace — the bug this module was fixed for — and nothing in the
codebase has ever written to that path, so the tool returned an empty
list to everyone, forever. Hence ``branch`` rather than the old
\``default_branch``: the state file records the branch that was actually
ingested, and no caller can be depending on a key that never had a row
under it.

Output parameters:

- `result` (array)

### `list_skills` (~104 tokens)

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 API).

Output parameters:

- `result` (array)

### `get_skill` (~89 tokens)

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).

Input parameters:

- `name` (string, required)

### `get_process_map` (~93 tokens)

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.

### `list_proposed_actions` (~108 tokens)

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 UI.

Input parameters:

- `status` (string)

Output parameters:

- `result` (array)

### `propose_action` (~134 tokens)

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}`` or an ``error``.

Input parameters:

- `action_type` (string, required)
- `description` (string)
- `evidence` (string)
- `title` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/in-enhanciar-enhanciar/enhanciar-mcp#diagnostics

## Score history

- 2026-09-20: 64

## Common questions

### What is the Enhanciar — company brain MCP server?

Enhanciar — company brain is an MCP server listed in the public MCP registry as in.enhanciar/enhanciar. Ask your team's code, Slack and docs from any MCP client. Every answer cited to source. Early access. This page covers its hosted endpoint (https://enhanciar.in/enhanciar/mcp/).

### Is the Enhanciar — company brain MCP server safe to use?

Enhanciar — company brain scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Enhanciar — company brain MCP server expose?

Enhanciar — company brain exposes 12 tools: list_pages, search_wiki, get_page, query, impact, and 7 more. Their descriptions and schemas cost roughly 1,649 tokens of context every time the server is loaded.

### Does the Enhanciar — company brain MCP server require authentication?

No. We connected to Enhanciar — company brain without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Enhanciar — company brain MCP server still maintained?

Enhanciar — company brain is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://enhanciar.in/enhanciar/mcp/
- Authorisation metadata: https://enhanciar.in/.well-known/oauth-protected-resource/enhanciar/mcp
- Website: https://enhanciar.in/
- Changelog RSS feed: https://verifymcp.io/servers/in-enhanciar-enhanciar/enhanciar-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/in-enhanciar-enhanciar/enhanciar-mcp.json
- HTML version of this page: https://verifymcp.io/servers/in-enhanciar-enhanciar/enhanciar-mcp