io.github.stackql/stackql-mcp
StackQL MCP Server
Is the StackQL MCP server down? No. It is up and needs network, probed 2026-11-06.
SQL-native query and provisioning engine for cloud infrastructure, served over MCP.
needs network probed 2026-11-14 · unchanged since 2026-11-06
MCP error -32000: Connection closed stackql-mcp: downloading stackql-mcp-linux-x64.mcpb (first run only) ... stackql-mcp: fetch failed
- Run it
- npx -y @stackql/mcp-server@1.0.888 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/stackql/stackql
- Website
- https://stackql.io
- Registry
- active, updated 2026-11-05 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.stabem/newsintel · alive
- io.github.stabgan/openrouter-multimodal · alive
- io.github.stabgan/steelmind · alive
- io.github.stablevoy/stablevoy-mcp · crashed on start
- codemcp io.github.stackunseen/codemcp · alive
- Phonebook io.github.stag-build/phonebook · alive
- io.github.staminna/directus-mcp-server · alive
- io.github.standardbeagle/dart-query · alive
Servers that mention infrastructure or provisioning.
- BorealHost ai.borealhost/mcp · alive
- Cloud World Model ai.cloudworldmodel/cloud-world-model · alive
- Contabo (VPS) MCP Server ai.com.mcp/contabo · alive
- ColdState — Deterministic Knowledge Infrastructure ai.coldstate/knowledge · alive
- Data Center Index ai.datacenterindex/datacenterindex · needs auth
- GreenlandAI ai.greenlandai/greenlandai · alive
- InfraPulse ai.infrapulse/infrapulse · rejects our protocol version
- Infrabase ai.infrabase/directory · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server tries to reach the network on start. The probe runs in a container with the network off, so a server that connects lazily, on the first tool call, is measured.