io.github.neverinfamous/mysql-mcp
io.github.neverinfamous/mysql-mcp
Is the io.github.neverinfamous/mysql-mcp MCP server down? Yes. It has given no valid answer since 2026-10-30: not found.
Enterprise-grade MySQL MCP Server with OAuth 2.0, 106 tools, and Docker deployment
not found down since 2026-10-30 · probed 2026-11-14 · unchanged since 2026-11-06
Error response from daemon: failed to resolve reference "docker.io/writenotenow/mysql-mcp:v1.0.0": docker.io/writenotenow/mysql-mcp:v1.0.0: not found
- Run it
- docker run -i --rm docker.io/writenotenow/mysql-mcp:v1.0.0 (stdio, probed in a container with the network off)
- Host
- docker.io
- Repository
- https://github.com/neverinfamous/mysql-mcp.git
- Registry
- active, updated 2025-12-13 · registry entry
Compare this server with others.
More servers
Other registry entries on docker.io, the ones next to this name; all of them.
- io.github.magurelabs/web-search · not probed
- io.github.magurelabs/zoom · not probed
- DNS MCP Server io.github.mclose/dns-mcp · alive
- io.github.neverinfamous/memory-journal-mcp · not found
- PostgreSQL MCP Server io.github.neverinfamous/postgres-mcp-server · not found
- Nhost io.github.nhost/mcp · not probed
- io.github.noisy/noisy-coding · not probed
- GitLab Documentation MCP Server io.github.nunolima/gitlab-docs-mcp · not found
Servers that mention mysql.
- ai.getvda/elasticsearch-redis-mysql-stack-generator · newer protocol
- ai.getvda/mysql-redis-compose-generator · newer protocol
- ai.getvda/mysql-redis-compose-generator-adminer · newer protocol
- ai.getvda/mysql-redis-compose-generator-nginx · newer protocol
- ai.getvda/nats-mysql-redis-stack-generator · newer protocol
- ai.getvda/rabbitmq-elasticsearch-mysql-stack-generator · newer protocol
- HostingFor.AI ai.hostingfor/hosting · needs auth
- co.thinair/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-30, 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.