io.github.omkardongre/veilquota
VeilQuota
Is the VeilQuota MCP server down? Yes. It has given no valid answer since 2026-10-16: not found.
Private OCR, web search, and attested AI chat, paid with anonymous credits bought with shielded ZEC
not found down since 2026-10-16 · probed 2026-11-15 · unchanged since 2026-10-30
npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /
- Run it
- npx -y @veilquota/mcp@0.3.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/omkardongre/veilquota
- Website
- https://veilquota-web-140011936420.us-central1.run.app
- Registry
- active, updated 2026-10-11 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- hush io.github.omarei-omoto/hush · alive
- io.github.omer907/mcp-server · alive
- io.github.omer907/melt-mcp-server · alive
- io.github.omitly/omitly-mcp · alive
- Planka MCP io.github.omnicoreos/planka-mcp · needs env
- io.github.omnigami-ai/mcp · alive
- io.github.omoshola-o/xap · crashed on start
- io.github.onchainvanguard/scytheradar-mcp · alive
Servers that mention anonymous or attested.
- Clearvoyance ai.clearvoyance/clearvoyance · alive
- OpenSwitchboard ai.openswitchboard/switchboard · needs auth
- Race Calendar F1 app.racecalendar/f1 · alive
- FlightSweeper app.vercel.flightsweeper-webmcp/public · not found
- at.memebo/memeboat-mcp · alive
- JassWiki — Swiss Jass Authority (AMCP v0.1) ch.jassverband/jasswiki · alive
- Agent Observatory com.agent-observatory/agent-observatory · alive
- Genchi com.genchi/genchi · 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-16, 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.