io.github.mdfifty50-boop/compliance-shield

Is the io.github.mdfifty50-boop/compliance-shield MCP server down? Yes. It has given no valid answer since 2026-10-17: crashed on start.

ZATCA, UAE CT, EU AI Act regulatory compliance for AI agents

crashed on start down since 2026-10-17 · probed 2026-11-15 · unchanged since 2026-10-31

MCP error -32000: Connection closed
Error: Could not locate the bindings file. Tried:
    '/work/node_modules/better-sqlite3/lib/binding/node-v127-linux-x64/bet

Run it: npx -y compliance-shield-mcp@0.1.3 (stdio, probed in a container with the network off)
Host: npmjs.com
Repository: https://github.com/mdfifty50-boop/compliance-shield-mcp
Registry: active, updated 2026-04-24 · registry entry

Compare this server with others.

More servers

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

io.github.mdfifty50-boop/agent-guard · crashed on start
io.github.mdfifty50-boop/agent-replay · alive
io.github.mdfifty50-boop/agent-security · alive
Agentic Observability MCP io.github.mdfifty50-boop/agentic-observability · alive
io.github.mdfifty50-boop/docx-forge · alive
io.github.mdfifty50-boop/domain-expertise · alive
io.github.mdfifty50-boop/gcc-intelligence · alive
io.github.mdfifty50-boop/mcp-registry · crashed on start

Servers that mention compliance.

BlueNexus Universal MCP ai.bluenexus/universal-mcp · needs auth
Clarid Compliance ai.clarid/compliance · no DNS
Duskly ai.duskly/duskly · alive
ai.kanonik/kanonik · needs auth
ai.ssid/ssid-mcp · alive
ThinkNEO Control Plane ai.thinkneo/control-plane · no DNS
ClearPolicy app.clearpolicy/clearpolicy · needs auth
EuroComply — EU Regulatory Compliance app.eurocomply/compliance · 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

No valid answer since 2026-10-17, in every probe since then.
The process exited on start before it answered initialize. The error output is above.