mcpbeat Sign in

Hexa MCP Server

answering

Hexa is answering right now. Last checked 9 min ago.

Shared company knowledge, workflows, and connected apps for the AIs your team already uses.

Uptime history 25 days of history
25 days agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
714 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Hexa every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

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

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

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.hexahq.ai/mcp streamable-http sign-in 673 ms 9 min ago

Alternatives to Hexa

same job, measured the same way
Contextium Io
by contextium-io

Your team's knowledge, always in context. SOPs, coding standards, and workflows for Claude.

174 installs/wk local only
Kindex
by wandercom

Persistent knowledge graph and MCP server for AI workflows with git-tracked project context.

1 685 installs/wk local only
Kindex
by jmcentire

Persistent knowledge graph and MCP server for AI workflows with git-tracked project context.

local only
NoCrash
by nocrash

Know when your n8n workflows, URLs, and AI apps break, before your customers do.

answering
Ux MCP Server
by elsahafy

UX toolkit: 28 knowledge resources, 23 analysis tools & 4 workflow prompts for any MCP client

98 installs/wk local only
Algolia Productivity
by algolia

Connect LLM tools to your Algolia account with user-scoped access for internal workflows.

answering
Handoff MCP Server
by josephibra

Durable agent-to-agent handoffs and shared scratchpad for multi-agent workflows.

3 tools answering
n8n MCP Server
by rpgmais

The most complete MCP server for n8n — 43 tools for workflows, data tables, and more.

37 installs/wk local only

Hexa — questions

Answers built from our own checks of this server.

Why is there no tool list for Hexa?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Hexa 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 714 ms. The bar chart above shows every period we have measured.
How do I connect Hexa?
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. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Hexa?
No API key is involved. Hexa answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Hexa?
It answers our handshake in 714 ms on average, which is faster than 16% 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.