io.github.terrorproforma/explore-better
Explore Better
Is the Explore Better MCP server down? Yes. It has given no valid answer since 2026-10-30: not found.
AI-native Windows file manager for scoped discovery, disk analysis, and recoverable operations.
not found down since 2026-10-30 · probed 2026-11-15 · unchanged since 2026-11-06
command not found: /work/bundle/server/ExploreBetterMcp
- Bundle
- https://github.com/terrorproforma/explore-better/releases/download/v0.2.8/ExploreBetter-MCP-0.2.8-windows-x64.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
- Host
- github.com
- Repository
- https://github.com/terrorproforma/explore-better
- Registry
- active, updated 2026-09-25 · registry entry
Compare this server with others.
More servers
Other registry entries on github.com, the ones next to this name; all of them.
- sudo-proxy io.github.tarides/sudo-proxy · alive
- Patina io.github.taxmanhaven/patina · alive
- vex io.github.tenatarika/vex · crashed on start
- io.github.teologov/snipper-mcp · crashed on start
- Limoni io.github.thebanri/limoni-mcp · alive
- io.github.thecolourfoundation/rune · needs env
- battlemap-mcp io.github.thekannen/battlemap-mcp · alive
- el-mcp-server io.github.thekuwayama/el-mcp-server · crashed on start
Servers that mention explore.
- ai.myriade/myriade · needs auth
- ScoreIA Open Labyrinth ai.scoreia/open-labyrinth · alive
- ai.smithery/BigVik193-reddit-user-mcp · not found
- ai.switchapp/switch · alive
- ai.smithery/Phionx-mcp-hello-server · not found
- ai.smithery/afgong-sqlite-mcp-server · not found
- ai.smithery/arjunkmrm-ahoy2 · not found
- ai.smithery/arjunkmrm-bobo · not found
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.