Developer · Remote MCP server
Heystack
Observability for AI apps: investigate traces, logs, LLM usage, replays and crashes; manage alerts.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.heystack/heystack- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-17
- Updated
- 2026-09-17
- Publisher
- dev.heystack
- Namespace
- Namespace verified by the MCP Registry via the domain heystack.dev · how
- Website
- heystack.dev/docs/mcp
- Repository
- github.com/heystack-hq/heystack-plugins
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.heystack.dev/mcp | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Heystack
Heystack is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.heystack.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Hex GraphDeterministic layered code graph MCP server with framework overlays and SCIP interop. | Local · stdio |
| Hex LineHash-verified file editing MCP server with token efficiency hook for AI coding agents. | Local · stdio |
| Hex SSHToken-efficient SSH MCP with hash-verified files and persistent tmux sessions. 14 tools. | Local · stdio |
| HeyReachAutomate your HeyReach workspace - manage campaigns, leads, unibox, webhooks, and pull analytics. | Remote · HTTPLive check: sign-in required |
| HiberdenRead and verify your local media archive's 3-2-1 coverage across tape, disk, NAS, and cloud. | Local · stdio |
| Hicortex - AI Fleet MemoryShared fleet memory for AI agents: nightly self-correction, recall every prompt (supported agents). | Local · stdio |
| HIG DoctorApple Human Interface Guidelines search, lookup, and project audits for AI coding agents. | Local · stdio |
| Hindsight MCPMCP server for AI-assisted coding with development history: git, tests, Copilot. | Local · stdio |