Is the Enhanciar MCP server down?

mcp-registry/in.enhanciar/enhanciar · v1.27.0

unknown
Last checked 2026-10-17 14:38 UTC · handshake 2.4s

As of 2026-10-17 14:38 UTC, the Enhanciar MCP server is unknown with a Glimind reliability score of 89/100 (grade B). It is reachable and asks for credentials (normal for servers that need an account or API key). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 11 minutes.

uptime (30d checks)
99.9%
checks observed
2,936
outages (90d)
2
tools
12

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

Install Enhanciar MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http enhanciar-mcp-server https://enhanciar.in/enhanciar/mcp/

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (76/100)

C (76/100): 0 error(s), 4 warning(s) across 12 tool(s); ~2,055 tokens of tool definitions.
Scores higher than 14% of 15,356 MCP servers Glimind has audited.
Its tool list costs an agent ~2,055 tokens per session — more than 45% of servers.
76 → 76 since 2026-10-17
no tool-poisoning patterns
Schemas86
Descriptions49
Safety hints30
Token cost100
Client compatibility100
Protocol100
Reliability85
Stability96

What to fix (6)

12 of 12 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: get_graph, get_page, get_process_map, get_skill, impact and 7 more

18 parameter(s) across 7 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: get_page, get_skill, impact, list_proposed_actions, propose_action and 2 more

1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: get_page

Handshake + tools/list takes ~1,999 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

Requires authentication (Bearer); tool definitions could not be read anonymously.

If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.

In the last 30 days: 0 tool(s) removed and 1 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Auto-fix: 10 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 7 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fin.enhanciar%2Fenhanciar/fixes

get_graph 1 change
{
  "name": "get_graph",
  "description": "Return the community/knowledge graph manifest for visualisation.\n\nUseful when the calling agent wants the high-level structure of the\nkey's workspace (clusters, hub nodes, cross-references) rather than\nthe contents of any one page. Returns ``{nodes, edges, communities,\nstats}`` — exact shape mirrors the ``/api/wiki/graph`` REST endpoint.\n",
  "inputSchema": {
    "type": "object",
    "title": "get_graphArguments",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_page 2 changes
{
  "name": "get_page",
  "description": "Fetch a single wiki page from the key's workspace.\n\nArgs:\n    category: One of ``entities | concepts | people | decisions |\n        sources | flows | infrastructure | tickets``.\n    name: Page slug (without ``.md`` extension), as returned by\n        ``list_pages`` / ``search_wiki``.\n\nReturns ``{category, name, content}`` — ``content`` is the full\nmarkdown body including YAML frontmatter. Returns ``{error: \"...\"}``\nif the page doesn't exist.\n",
  "inputSchema": {
    "type": "object",
    "title": "get_pageArguments",
    "properties": {
      "name": {
        "title": "Name",
        "default": "",
        "type": "string"
      },
      "page": {
        "title": "Page",
        "default": "",
        "type": "string"
      },
      "path": {
        "title": "Path",
        "default": "",
        "type": "string"
      },
      "slug": {
        "title": "Slug",
        "default": "",
        "type": "string"
      },
      "title": {
        "title": "Title",
        "default": "",
        "type": "string"
      },
      "category": {
        "title": "Category",
        "default": "",
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_process_map 1 change
{
  "name": "get_process_map",
  "description": "Return the \"living map of how the company works\" for the key's workspace.\n\nA graph of process nodes (compiled skills), the external systems\nthey touch (GitHub, Slack, Jira, …), the wiki docs they were\nderived from, and team groups — with derived_from / uses /\nreferences edges. Use this when the agent wants the high-level\noperational structure rather than one skill's steps.\n",
  "inputSchema": {
    "type": "object",
    "title": "get_process_mapArguments",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/in.enhanciar/enhanciar"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/in.enhanciar/enhanciar"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fin.enhanciar%2Fenhanciar.svg)](https://glimind.com/server/mcp-registry%2Fin.enhanciar%2Fenhanciar?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fin.enhanciar%2Fenhanciar?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fin.enhanciar%2Fenhanciar.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fin.enhanciar%2Fenhanciar.svg
   :target: https://glimind.com/server/mcp-registry%2Fin.enhanciar%2Fenhanciar?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:26e80ebafcbc7bb3…, first seen 2026-10-17, included at leaf 15370 of 20,567. Version history · verify what your client received.

Tools (12)

Compare: most reliable knowledge servers · most reliable code servers · most reliable productivity servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Enhanciar MCP server down right now?

As of 2026-10-17 14:38 UTC, the Enhanciar MCP server is unknown with a Glimind reliability score of 89/100 (grade B). It is reachable and asks for credentials (normal for servers that need an account or API key). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 11 minutes.

How many tools does Enhanciar MCP server provide?

Enhanciar MCP server advertises 12 tools, including get_graph, get_page, get_process_map, get_skill, impact.

How do I install Enhanciar MCP server?

Point your MCP client at this streamable-http endpoint: https://enhanciar.in/enhanciar/mcp/

Is the Enhanciar MCP server safe to connect to an AI agent?

Glimind scanned all 12 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Enhanciar MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.