io.github.lumidb/lumidb

LumiDB

Is the LumiDB MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.

Search, describe, render and measure volumes in point clouds and rasters stored in LumiDB.

needs auth probed 2026-11-15 · unchanged since 2026-11-14 · HTTP 401 · Basic

Streamable HTTP error: Error POSTing to endpoint: {"status_code":401,"status_text":"Unauthorized","reason":"No authentication method provided"}

Endpoint: https://api.lumidb.com/api/mcp (streamable-http)
Host: api.lumidb.com
Getting access: A key or token from the publisher, sent in the Authorization header (Basic). The server publishes no OAuth metadata. Store the key once: npx mcpcost auth https://api.lumidb.com/api/mcp --header "Authorization: Basic …".
Read from the server's public OAuth metadata, without a token. Method.
Website: https://docs.lumidb.com/integrations/connecting-ai-assistants-mcp
Registry: active, updated 2026-11-14 · registry entry

More servers

Servers that mention describe or measure.

Advisors AI — Route a Store Need to a Service ai.advisorsai/service-navigator · alive
AppDeploy ai.appdeploy/deploy-app · needs auth
Buron ai.buron/buron · paid (402)
DABYTE AI Visibility Index ai.dabyte/visibility-index · alive
Council of AI GSPC ai.councilof/gspc · alive
DABLOCK AI Visibility Index ai.dablock/visibility-index · alive
ai.nullary/nullary · alive
ai.openhelm/dev-changes · needs auth

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.

Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.