io.github.leemour/acme-crm-cli

Acme CRM example

Is the Acme CRM example MCP server down? It gave no valid answer in the probe of 2026-11-09: crashed on start. One failed probe is not an outage.

An example WireCat CLI for a made-up CRM, synthetic data. Sign a profile in with acme-crm first.

crashed on start no valid answer since 2026-11-08 · probed 2026-11-14 · unchanged since 2026-11-09

MCP error -32000: Connection closed
{"error":{"code":"configuration_error","reason":"config.invalid","message":"no acme-crm profile on this computer yet — set o

Run it: npx -y @leemour/acme-crm-cli@0.3.0 (stdio, probed in a container with the network off)
Host: npmjs.com
Repository: https://github.com/leemour/acme-crm-cli
Website: https://github.com/leemour/acme-crm-cli#readme
Registry: active, updated 2026-11-08 · registry entry

Compare this server with others.

More servers

Other registry entries on npmjs.com, the ones next to this name; all of them.

MCP for Adobe Premiere Pro io.github.leancoderkavy/premiere-pro · alive
io.github.learningloons-hash/lithtrix · alive
io.github.leejpsd/nextjs-cache-handler-mcp · alive
Personae io.github.leek-emperor/personae · alive
io.github.legalithm/legalithm-mcp-server · alive
io.github.legann/repovine · crashed on start
io.github.legolev/mediamcp · alive
io.github.lelianto/capimail · needs env

Servers that mention acme.

com.ritzademo/acme-todo · TLS error
OPNsense MCP Server io.github.itunified-io/opnsense · no executable
CertBridge MCP io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/certbridge · alive
Forge AI Accountability io.github.forgeorbital/forge-ai-accountability · alive
SimpleACME DNS-01 setup com.simpleacme/dns-setup · alive

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.

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

The package did not start as an MCP server at its probe on 2026-11-09. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
The process exited on start before it answered initialize. The error output is above.