ru.nova-amocrm/amocrm
NOVA amoCRM / Kommo
Is the NOVA amoCRM / Kommo MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-03.
Remote MCP for amoCRM and Kommo: leads, contacts, tasks, pipelines, chats, Salesbot. OAuth.
needs auth probed 2026-11-15 · unchanged since 2026-11-03 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error": "unauthorized"}- Endpoint
- https://sp1-nova.ru/api/mcp-server/mcp/ (streamable-http)
- Host
- sp1-nova.ru
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://sp1-nova.ru/api/mcp-server/mcp/ registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server sp1-nova.ru, PKCE S256, grants authorization_code, refresh_token.
Scopes mcp.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://nova-amocrm.ru/widgets/mcp_server
- Registry
- active, updated 2026-11-01 · registry entry
- Changes
- 2 recorded, reachable in 1 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Servers that mention amocrm or kommo or nova.
- Kommo io.github.mcp-dir/kommo-mcp · alive
- io.github.theYahia/amocrm-mcp · alive
- RallyProp: SBIR, OTA & Federal Innovation Funding ai.rallyprop/gov-funding · needs auth
- ZP Nexus br.com.sistemasinovadores/zp-nexus · needs auth
- Blogger Agent by Nova (CIVAI) co.civai.nova/blogger-agent · alive
- Browser Automation Agent by Nova (CIVAI) co.civai.nova/browsergpt-agent · alive
- Calendar Agent by Nova (CIVAI) co.civai.nova/calendar-agent · alive
- Code Interpreter Agent by Nova (CIVAI) co.civai.nova/code-interpreter-agent · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-03 11:45 | needs auth | ||||
| 2026-11-02 12:03 | timeout |
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.