io.github.nvdigitalsolutions/nvoos-mcp-gateway

NV oOS Gateway

Is the NV oOS Gateway MCP server down? No. It is up and needs auth (HTTP 403), probed 2026-11-01.

Streamable HTTP MCP gateway for NV oOS fleets — one API key, namespaced tools, quotas and policy.

needs auth probed 2026-11-01 · HTTP 403

Streamable HTTP error: Error POSTing to endpoint: <!DOCTYPE html><html lang="en-US"><head><title>Just a moment...</title><meta http-equiv="Content-Type" content

Endpoint: https://mcp.nvoos.pro/mcp (streamable-http)
Host: mcp.nvoos.pro
Getting access: The server answers HTTP 403 with no WWW-Authenticate header and no OAuth metadata, so the publisher's documentation is the only guide.
Read from the server's public OAuth metadata, without a token. Method.
Repository: https://github.com/nvdigitalsolutions/mcp-ai-wpoos
Website: https://mcp.nvoos.pro/
Registry: active, updated 2026-10-31 · registry entry

Compare this server with others.

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.

Atom feed

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

The server answers HTTP 403 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.

Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.