io.komuta/mcp
Komuta
Is the Komuta MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-12.
Deploy and run your apps by asking your AI: services, Postgres, logs, traces, rollbacks, costs.
needs auth probed 2026-11-15 · unchanged since 2026-11-12 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"Authorization required; connect with Komuta OAuth or a Komuta AP- Endpoint
- https://mcp.komuta.io/mcp (streamable-http)
- Host
- mcp.komuta.io
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.komuta.io/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server auth.komuta.io, PKCE S256, grants authorization_code, implicit, password, client_credentials, refresh_token.
Scopes komuta:mcp offline_access.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://www.komuta.io/docs/mcp/mcp-setup
- Registry
- active, updated 2026-11-11 · registry entry
Compare this server with others.
More servers
Servers that mention rollbacks 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.