mcpbeat

BrainFlow MCP Server

live.alpic.alpichack-3c740d01/alpichack
answering

BrainFlow is answering right now. Last checked 10 min ago. It exposes 12 tools.

AI-powered ticket triage and workflow automation

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
12
Tools
read from the server
1418 ms
Response time
average over 24h
open, no key
Access
sse

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add alpichack --transport http https://alpichack-3c740d01.alpic.live
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "alpichack": {
      "url": "https://alpichack-3c740d01.alpic.live"
    }
  }
}
~/.codex/config.toml
[mcp_servers.alpichack]
url = "https://alpichack-3c740d01.alpic.live"
.cursor/mcp.json
{
  "mcpServers": {
    "alpichack": {
      "url": "https://alpichack-3c740d01.alpic.live"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "alpichack": {
      "url": "https://alpichack-3c740d01.alpic.live"
    }
  }
}

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

hitl
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.
agent
get-agent-config
Internal — load saved agent.md content for a role.
analysis
fetch-analysis
Fetch LLM analysis (findings + solutions) for a ticket.
connect
connect-provider
Internal — initiate an OAuth connection flow for a provider.
connection
get-connection-status
Internal — get current connection status for all providers.
github
list-github-repos
Internal — list the user's GitHub repositories for repo selection.
jira
list-jira-projects
Internal — list the user's Jira projects for project selection.
open
open-ticket
Open a specific ticket to see its details, MCP findings, and candidate solutions.
save
save-agent-config
Internal — save agent.md content for a role.
setup
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. Guides the user through role selection and OAuth connection in a step-by-step widget.
triage
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 'GitHub issues'), pass the matching source in the sources array.

Endpoints

URLTransportStateLatencyChecked
https://alpichack-3c740d01.alpic.live sse answering 463 ms 10 min ago

BrainFlow — questions

Answers built from our own checks of this server.

What can BrainFlow do?
It exposes 12 tools, read directly from the server on our last check. Among them: connect-provider, fetch-analysis, get-agent-config, get-connection-status, hitl-execute, hitl-reject and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is BrainFlow working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 1418 ms. The bar chart above shows every period we have measured.
How do I connect BrainFlow?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does BrainFlow need an API key?
No. BrainFlow completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is BrainFlow?
It answers our handshake in 1418 ms on average, which is faster than 2% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.