io.github.hyperpolymath/poly-db-mcp
Polyglot Database MCP
Is the Polyglot Database MCP server down? Yes. It has given no valid answer since 2026-10-26: not found.
Unified MCP for 20 databases: SurrealDB, ArangoDB, Virtuoso, CouchDB, Cassandra, and more
not found down since 2026-10-26 · probed 2026-11-14 · unchanged since 2026-11-02
Error response from daemon: error from registry: denied denied
- Run it
- docker run -i --rm ghcr.io/hyperpolymath/poly-db-mcp:main (stdio, probed in a container with the network off)
- Host
- ghcr.io
- Repository
- https://github.com/hyperpolymath/poly-db-mcp
- Registry
- active, updated 2025-12-14 · registry entry
Compare this server with others.
More servers
Other registry entries on ghcr.io, the ones next to this name; all of them.
- io.github.hughhan1/mysql · not probed
- droidmap io.github.hussainshirazi/droidmap · crashed on start
- HydraDNS io.github.hydradns/hydra-mcp · not found
- ultra-e2e-test tasks io.github.hynix666/ultra-e2e-test · not found
- Polyglot SSG MCP io.github.hyperpolymath/poly-ssg-mcp · not found
- io.github.ibeal/tidal-mcp · needs env
- io.github.iflytek/dolphin-mcp-pilot · not probed
- JDBC MCP Server io.github.igorolv/jdbc-mcp-server · alive
Servers that mention poly.
- Liquid Agent ai.liquidagent.api/liquid-agent · alive
- app.oddsrail/polymarket-kalshi-trading · needs auth
- cc.ticktape/mcp · alive
- Crosswire — Polymarket & Kalshi Arbitrage com.crosswire-api/crosswire-polymarket-kalshi-arbitrage · alive
- DaedalMap Administrative Boundaries (loc_id to polygon) com.daedalmap/boundaries · alive
- DepthFeed com.depthfeed/depthfeed · alive
- EloEdge: Kalshi model probabilities com.eloedge/kalshi-prediction-markets · needs auth
- EloEdge Data: prediction-market and price history com.eloedge/prediction-market-data · needs auth
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
- No valid answer since 2026-10-26, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.