io.github.amkkoussay/mersad

Mirsad

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

Shared memory for AI agents: bi-temporal facts, first-class decisions, owner-resolved conflicts.

crashed on start no valid answer since 2026-11-15 · probed 2026-11-15

MCP error -32000: Connection closed
sqlite3.OperationalError: unable to open database file
  File "/work/uv/mirsad-mcp/lib/python3.12/site-packages/mirsad/core.

Run it: uvx mirsad-mcp@0.2.2 (stdio, probed in a container with the network off)
Host: pypi.org
Registry: active, updated 2026-11-15 · registry entry

Compare this server with others.

More servers

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

Philips TV (JointSpace + ADB) io.github.amineutron/pylips-mcp · alive
Plane Workflow io.github.amirhosseinkz/plane-workflow-mcp · alive
India Company Diligence io.github.amit043/india-company-diligence · alive
io.github.amitsingh-24/pixlint · needs mcp<2
paper-preflight io.github.amos689/paper-preflight · crashed on start
Talamus io.github.ampres-ai/talamus · needs args
YAAC io.github.amyodov/yet-another-agentic-chat · install failed
git-into-gsoc io.github.anandkaranubc/git-into-gsoc · 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-15. 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.