mcpcost

io.github.kartegagithub/laviya

Laviya

Is the Laviya MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.

Laviya project management: read and update tasks, wikis, sprints and test cases.

needs auth probed 2026-11-14 · HTTP 401 · Bearer

Streamable HTTP error: Error POSTing to endpoint: {"error":"unauthorized","error_description":"Missing access token. Connect Laviya again."}
Endpoint
https://api.laviya.app/api/mcp (streamable-http)
Host
api.laviya.app
Package
The publisher's package npm:laviya-mcp-server did not list its tools in the container: crashed on start, MCP error -32000: Connection closed Error: Invalid environment configuration: Required at file:///work/node_modules/laviya-mcp-server/dist/index.js:37:1 .
Getting access
OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://api.laviya.app/api/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server api.laviya.app, 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/kartegagithub/laviya-agent-skills
Website
https://laviya.app
Registry
active, updated 2026-11-10 · registry entry

Compare this server with others.

More servers

Servers that mention laviya or management or project.

Badge for the README

mcpcost: needs auth

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

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