io.github.xlight/deepseek-visionary
DeepSeek Visionary
Is the DeepSeek Visionary MCP server down? Yes. It has given no valid answer since 2026-10-31: not found.
DeepSeek web vision model as an MCP server with browser auto-login.
not found down since 2026-10-31 · probed 2026-11-14 · unchanged since 2026-11-07
command not found: visionary-server
- Bundle
- https://github.com/xlight/deepseek-visionary/releases/download/v0.2.2/visionary-server-aarch64-apple-darwin.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
- Host
- github.com
- Repository
- https://github.com/xlight/deepseek-visionary
- Registry
- active, updated 2026-08-10 · registry entry
Compare this server with others.
More servers
Other registry entries on github.com, the ones next to this name; all of them.
- Apple Notes Snapshot io.github.xiaojiou176-open/apple-notes-snapshot · not found
- Campus Copilot MCP io.github.xiaojiou176-open/campus-copilot-mcp · not found
- io.github.xixi048/create-all-cg-save · alive
- io.github.xixi048/publish-to-all-skill-stores · alive
- Dropify io.github.xozxro/dropify-mcp · alive
- XTELL Serial io.github.xtell-cn/xtell-serial · error
- xaffinity MCP io.github.yaniv-golan/xaffinity-mcp · alive
- io.github.ydnikolaev/a2ahub · not found
Servers that mention visionary or deepseek.
- io.github.NeousAxis/aya-registry · alive
- Webhound ai.webhound/webhound · needs auth
- 中文 AI 可引用性（GEO/AEO）体检 cn.savantcat/geo-cn · alive
- com.jojapi/swift-ai · alive
- Store API com.store-api/store-api · alive
- GEON Monitor com.usegeon/geon · needs auth
- TopxAI Models com.topxea.ai/models · alive
- Kourier sh.kourier/info · 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
- No valid answer since 2026-10-31, 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.