io.github.iusserhat/horkos

Horkos

Is the Horkos 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.

Escrow for AI agent purchases on NEAR testnet: pay only when a TEE verifies the delivery.

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

MCP error -32000: Connection closed
    at file:///work/node_modules/horkos-mcp/dist/horkos-mcp.mjs:321:1
    at ModuleJob.run (node:internal/modules/esm/module

Run it: npx -y horkos-mcp@0.1.0 (stdio, probed in a container with the network off)
Host: npmjs.com
Repository: https://github.com/iusserhat/horkos
Website: https://horkos-escrow.netlify.app
Registry: active, updated 2026-11-14 · registry entry

Compare this server with others.

More servers

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

OPNsense MCP Server io.github.itunified-io/opnsense · no executable
PostgreSQL MCP Server io.github.itunified-io/postgres · alive
Tailscale MCP Server io.github.itunified-io/tailscale · alive
Grafana MCP io.github.itzhouq/grafana-mcp · crashed on start
io.github.ivangr1/walletap · alive
WSG Check io.github.ivanoats/wsg-check · alive
IWE (iwe.md) io.github.iwe-org/iwe · alive
codebase-synapse io.github.iwiels/codebase-synapse · alive

Servers that mention horkos or purchases or delivery.

IRL Gateway io.github.horkos-labs/irl-gateway · crashed on start
FairMind Project Context ai.fairmind/project-context · needs auth
Picsha AI ai.picsha/picsha · needs auth
Pocket Drives ai.pocketdrives/pocket-drives · alive
Routing24 ai.routing24/mcp · needs auth
ai.robomart/robomart · alive
ai.uxbert/cms · needs auth
ai.waiter24/mcp · not found

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.