BrainFlow

REMOTE · ALPICHACK-3C740D01.ALPIC.LIVE · SCANNED AUG 3

AI-powered ticket triage and workflow automation

Available components

remote · alpichack-3c740d01.alpic.live 75

+6 this week 75 75 Trust /100

Trust breakdown (6 categories)

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. How we score →

Endpoint Security74

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability81

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 875 tokens (~54/item across 16 items; 12 tools + 4 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Supports UI / widget rendering.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · alpichack-3c740d01.alpic.live

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.toml

[mcp_servers.live-alpic-alpichack-3c740d01-alpichack]
url = "https://alpichack-3c740d01.alpic.live/"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "live-alpic-alpichack-3c740d01-alpichack": {
      "type": "remote",
      "url": "https://alpichack-3c740d01.alpic.live/",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add live-alpic-alpichack-3c740d01-alpichack --url https://alpichack-3c740d01.alpic.live/ --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  live-alpic-alpichack-3c740d01-alpichack:
    url: "https://alpichack-3c740d01.alpic.live/"

// mcp.json

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

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

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 +1
- Resource “triage” now points somewhere else: ui://views/apps-sdk/triage.html?v=2bcb0532 → ui://views/ext-apps/triage.html?v=2bcb0532 security
- Resource “setup” now points somewhere else: ui://views/apps-sdk/setup.html?v=050a9d25 → ui://views/ext-apps/setup.html?v=050a9d25 security
2 Aug 26 0
- Resource “setup” now points somewhere else: ui://views/apps-sdk/setup.html?v=050a9d25 → ui://views/ext-apps/setup.html?v=050a9d25 security
- Resource “triage” now points somewhere else: ui://views/apps-sdk/triage.html?v=2bcb0532 → ui://views/ext-apps/triage.html?v=2bcb0532 security
1 Aug 26 +1
- Resource “triage” now points somewhere else: ui://views/apps-sdk/triage.html?v=2bcb0532 → ui://views/ext-apps/triage.html?v=2bcb0532 security
- Resource “setup” now points somewhere else: ui://views/apps-sdk/setup.html?v=050a9d25 → ui://views/ext-apps/setup.html?v=050a9d25 security
31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +1
- Resource “triage” now points somewhere else: ui://views/apps-sdk/triage.html?v=2bcb0532 → ui://views/ext-apps/triage.html?v=2bcb0532 security
- Resource “setup” now points somewhere else: ui://views/apps-sdk/setup.html?v=050a9d25 → ui://views/ext-apps/setup.html?v=050a9d25 security
28 Jul 26 +1
- Resource “triage” now points somewhere else: ui://views/apps-sdk/triage.html?v=2bcb0532 → ui://views/ext-apps/triage.html?v=2bcb0532 security
- Resource “setup” now points somewhere else: ui://views/apps-sdk/setup.html?v=050a9d25 → ui://views/ext-apps/setup.html?v=050a9d25 security
27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional

Show 3 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://alpichack-3c740d01.alpic.live

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=*.alpic.live	CN=Amazon RSA 2048 M01,O=Amazon,C=US	23 Oct 2025	21 Nov 2026	RSA 2048	SHA256-RSA	2f102c87e3a6a1adcfbddc95579fdc1
SANs: *.alpic.live
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA)	CN=Amazon Root CA 1,O=Amazon,C=US	23 Aug 2022	23 Aug 2030	RSA 2048	SHA256-RSA	77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA)	CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US	25 May 2015	31 Dec 2037	RSA 2048	SHA256-RSA	67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

DNSSEC insecure

Validation of alpichack-3c740d01.alpic.live. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
live.	present	36322	8	Verified
alpic.live.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Transports 3 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://alpichack-3c740d01.alpic.live	Verified	200
sse	https://alpichack-3c740d01.alpic.live	Verified	200
http (plaintext)	http://alpichack-3c740d01.alpic.live	HTTPS enforced	301	https://alpichack-3c740d01.alpic.live/

MCP tools — 12 exposed · ~795 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

connect-provider ~29

Internal — initiate an OAuth connection flow for a provider.

Input Output Examples

Name	Type	Req	Description
provider	string	yes	Provider to connect

Name	Type	Req	Description
redirectUrl	string	yes	OAuth authorization URL to redirect the user to

No examples provided.

fetch-analysis ~42

Fetch LLM analysis (findings + solutions) for a ticket.

Input Output Examples

Name	Type	Req	Description
ticketId	string	yes	The ticket source_id, e.g. KAN-1

Name	Type	Req	Description
findings	array	yes	—
solutions	array	yes	—

No examples provided.

get-agent-config ~40

Internal — load saved agent.md content for a role.

Input Output Examples

Name	Type	Req	Description
role	string	yes	Role identifier, e.g. 'engineer' or 'pm'

Name	Type	Req	Description
content	string	yes	The saved agent.md content, or empty string if none
role	string	yes	—

No examples provided.

get-connection-status ~20

Internal — get current connection status for all providers.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
connections	object	yes	Connection status for each supported provider

No examples provided.

hitl-execute ~221

Internal — approve a candidate solution and create issues on the target platform (Jira stories or GitHub issues).

Input Output Examples

Name	Type	Req	Description
jira_project_key	string	—	Jira project key, e.g. KAN (Jira only)
notes	string	—	PM/engineer notes
owner	string	—	GitHub repo owner (required when platform=github)
platform	string	yes	Target platform. 'jira' for PM creating Jira stories, 'github' for engineer creating GitHub issues.
repo	string	—	GitHub repo name (required when platform=github)
solution_effort	string	—	Effort estimate (Jira only)
solution_id	string	yes	The chosen solution id
solution_risk	string	—	Risk level (Jira only)
solution_summary	string	—	Summary of the chosen solution
solution_title	string	—	Title of the chosen solution
source	string	yes	Source system the ticket came from
ticket_id	string	yes	The ticket identifier

Name	Type	Req	Description
createdIssues	array	—	—
creationErrors	array	—	—
selectedSolution	object	yes	—

No examples provided.

hitl-reject ~83

Internal — reject a BrainFlow HITL item with a rework reason.

Input Output Examples

Name	Type	Req	Description
reason	string	yes	Short explanation of why all candidate solutions were rejected and what needs to change
source	string	yes	The source system the ticket came from
ticket_id	string	yes	The ticket identifier, e.g. GH-123 or sc-1842

Name	Type	Req	Description
rejected	boolean	yes	True when the rejection was persisted successfully
ticketId	string	yes	—

No examples provided.

list-github-repos ~23

Internal — list the user's GitHub repositories for repo selection.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
repos	array	yes	User's GitHub repositories

No examples provided.

list-jira-projects ~22

Internal — list the user's Jira projects for project selection.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
projects	array	yes	User's Jira projects

No examples provided.

open-ticket ~81

Open a specific ticket to see its details, MCP findings, and candidate solutions.

Input Output Examples

Name	Type	Req	Description
role	string	—	User role — determines Jira tickets (PM) or GitHub issues (engineer)
ticketId	string	yes	The ticket ID to open, e.g. sc-1842 or GH-123. Use the id field from triage results.

Name	Type	Req	Description
role	string	—	User role
ticket	object	yes	—

No examples provided.

save-agent-config ~52

Internal — save agent.md content for a role.

Input Output Examples

Name	Type	Req	Description
content	string	yes	The agent.md content to save
role	string	yes	Role identifier, e.g. 'engineer' or 'pm'

Name	Type	Req	Description
role	string	yes	—
saved	boolean	yes	—

No examples provided.

setup ~59

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. Guides the user through role selection and OAuth connection in a step-by-step widget.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
step	string	yes	The initial wizard step to display

No examples provided.

triage ~123

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 'GitHub issues'), pass the matching source in the sources array.

Input Output Examples

Name	Type	Req	Description
jira_project	string	—	Jira project/space key to filter tickets (e.g. KAN). Only used when sources includes jira.
sources	array	—	Filter tickets to specific sources. Pass ['jira'] for Jira only, ['github'] for GitHub only, etc. Omit to show tickets from all connected sources.

Name	Type	Req	Description
loading	boolean	—	True when the view is fetching fresh data in background
tickets	array	yes	Classified open tickets

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	69
27 Jul	69
28 Jul	70
29 Jul	71
30 Jul	71
31 Jul	73
1 Aug	74
2 Aug	74
3 Aug	75