BrainFlow
REMOTE · ALPICHACK-3C740D01.ALPIC.LIVE
AI-powered ticket triage and workflow automation
Available components
Last scanned (4 hours ago)
Scores higher than 16% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Project Management
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 → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 28 Sept 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
- 25 Sept 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
- 26 Aug 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
- 25 Aug 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.97 → unverified ▼ security
- Authorization: partial → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 24 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
- 23 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
- 22 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
- 21 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
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 5 Nov 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 M04,O=Amazon,C=US | 23 Sept 2026 | 8 Apr 2027 | RSA 2048 | SHA256-RSA | 41ca0c3068063f7c713f936a81919aa |
| SANs: *.alpic.live | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of alpichack-3c740d01.alpic.live. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| live. | present | 4724, 36322 | 8, 8 | Verified |
| alpic.live. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 403 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 3 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://alpichack-3c740d01.alpic.live | Auth required | 403 | |
| sse | https://alpichack-3c740d01.alpic.live | Auth required | 403 | |
| http (plaintext) | http://alpichack-3c740d01.alpic.live | HTTPS enforced | 301 | https://alpichack-3c740d01.alpic.live/ |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
connect-provider ~29
Internal — initiate an OAuth connection flow for a provider.
| 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.
| 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.
| 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 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).
| 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.
| 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 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 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.
| 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.
| 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 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.
| 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.
How do I install the BrainFlow MCP server?
BrainFlow is a hosted endpoint at https://alpichack-3c740d01.alpic.live/, 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.
remote · alpichack-3c740d01.alpic.live
claude mcp add --transport http live-alpic-alpichack-3c740d01-alpichack 'https://alpichack-3c740d01.alpic.live/'
What is the BrainFlow MCP server?
BrainFlow is an MCP server listed in the public MCP registry as live.alpic.alpichack-3c740d01/alpichack. AI-powered ticket triage and workflow automation. This page covers its hosted endpoint (https://alpichack-3c740d01.alpic.live).
Is the BrainFlow MCP server safe to use?
BrainFlow scores 33 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 BrainFlow MCP server expose?
BrainFlow exposes 12 tools: setup, triage, open-ticket, get-agent-config, save-agent-config, and 7 more. Their descriptions and schemas cost roughly 795 tokens of context every time the server is loaded.
Does the BrainFlow MCP server require authentication?
Yes. BrainFlow asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the BrainFlow MCP server still maintained?
BrainFlow is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.