com.rivtor/rivtor
Rivtor
Is the Rivtor MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.
Deploy full-stack apps (frontend, backend, Postgres, Redis) from your agent and get live URLs.
needs auth probed 2026-11-14 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"status":"failed","retryable":false,"stage":"auth","code":"unauthorized","cause":"Missing or invalid API toke- Endpoint
- https://api.rivtor.com/mcp (streamable-http)
- Host
- api.rivtor.com
- Package
- The publisher's package npm:rivtor did not list its tools in the container: crashed on start, MCP error -32000: Connection closed Use from AI agents: claude mcp add rivtor -- npx -y rivtor mcp rivtor skills install --target claude Env: RIVTOR_TOKEN, .
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://api.rivtor.com/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server api.rivtor.com, PKCE S256, grants authorization_code, refresh_token.
Scopes mcp.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/shyamolkonwar/rivtor-cli
- Website
- https://rivtor.com
- Registry
- active, updated 2026-11-10 · registry entry
Compare this server with others.
More servers
Servers that mention frontend or postgres.
- Ekwo OS — open source accounting: ledger, invoices and VAT on your own Supabase or Postgres ai.ekwo/mcp · needs auth
- ai.getvda/kafka-and-postgres-monitoring-stack · newer protocol
- ai.getvda/minio-postgres-redis-stack-generator · newer protocol
- ai.getvda/postgres-grafana-stack-generator · newer protocol
- ai.getvda/postgres-kafka-prometheus-stack-generator · newer protocol
- ai.getvda/postgres-kafka-stack-generator · newer protocol
- ai.getvda/postgres-minio-stack-generator · newer protocol
- ai.getvda/postgres-prometheus-stack-generator · newer protocol
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.