# Alpic Alpichack 3c740d01 Alpichack MCP server

Source: https://glimind.com/server/mcp-registry%2Flive.alpic.alpichack-3c740d01%2Falpichack
Registry id: `mcp-registry/live.alpic.alpichack-3c740d01/alpichack`
Status: auth-required (checked 2026-10-27T07:34:14.208Z)

## Verdict

Alpic Alpichack 3c740d01 Alpichack MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 269 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (100/100) across 12 tools, costing an agent about 1,531 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 269 ms | 65% of MCP servers |
| p95 handshake latency | 601 ms | — |
| Checks in 30 days | 219 | — |
| Outages, 90 days | 0 | — |
| Median recovery | — | — |
| Agent-readiness score | 100/100 (A) | 93% of MCP servers |
| Tools | 12 | — |
| Tool-list size for an agent | ~1,531 tokens | 58% of MCP servers |
| Days observed | 27 | — |

## Install

```json
{
  "mcpServers": {
    "alpic-alpichack-3c740d01-alpichack-mcp-s": {
      "type": "http",
      "url": "https://alpichack-3c740d01.alpic.live"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http alpic-alpichack-3c740d01-alpichack-mcp-s https://alpichack-3c740d01.alpic.live
```

## Tools (12)

- `connect-provider`: Internal — initiate an OAuth connection flow for a provider.
- `fetch-analysis`: Fetch LLM analysis (findings + solutions) for a ticket.
- `get-agent-config`: Internal — load saved agent.md content for a role.
- `get-connection-status`: Internal — get current connection status for all providers.
- `hitl-execute`: Internal — approve a candidate solution and create issues on the target platform (Jira stories or GitHub issues).
- `hitl-reject`: Internal — reject a BrainFlow HITL item with a rework reason.
- `list-github-repos`: Internal — list the user's GitHub repositories for repo selection.
- `list-jira-projects`: Internal — list the user's Jira projects for project selection.
- `open-ticket`: Open a specific ticket to see its details, MCP findings, and candidate solutions.
- `save-agent-config`: Internal — save agent.md content for a role.
- `setup`: Open the BrainFlow onboarding wizard. Use this when the user wants to configure BrainFlow, connect a task system (GitHub, Jira, or Slack), or change their role.
- `triage`: Show open tickets from connected task systems with triage classification. When the user asks for tickets from a specific system (e.g. 'show Jira tickets' or 'Gi

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.