vision.rdp/servers
Rdp.Vision
Is the Rdp.Vision MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-13.
Order and manage Windows RDP and Linux VPS servers paid with crypto: deploy, power, renew, top up.
needs auth probed 2026-11-14 · unchanged since 2026-11-13 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","id":null,"error":{"code":-32001,"message":"Send an Rdp.Vision API key as 'Authorization: Bea- Endpoint
- https://rdp.vision/mcp (streamable-http)
- Host
- rdp.vision
- Getting access
- A key or token from the publisher, sent in the Authorization header (Bearer). The server publishes no OAuth metadata. Store the key once: npx mcpcost auth https://rdp.vision/mcp --header "Authorization: Bearer …".
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://rdp.vision/docs/api/mcp
- Registry
- active, updated 2026-11-12 · registry entry
Compare this server with others.
More servers
Servers that mention vision.
- Contabo (VPS) MCP Server ai.com.mcp/contabo · alive
- ai.inflowpay.app/inflow · needs auth
- ai.oddsockets/remote-mcp · alive
- ai.primateintelligence/mcp · needs auth
- Reka ai.reka/mcp · alive
- ai.syntheticbrew/syntheticbrew · needs auth
- ai.roc/mcp · timeout
- Contendeo app.contendeo/contendeo · 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
- The server answers HTTP 401 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.