io.github.hakimjonas/lambe

Lambë

Is the Lambë MCP server down? It gave no valid answer in the probe of 2026-11-11: install failed. One failed probe is not an outage.

Shape-aware query language for structured data — JSON, YAML, TOML, HCL, CSV, Markdown.

install failed no valid answer since 2026-11-11 · probed 2026-11-14 · unchanged since 2026-11-11

not a zip file: [/tmp/mcpcost-stdio-kipzgz/bundle.mcpb]
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes

Bundle: https://github.com/hakimjonas/lambe/releases/download/v0.14.0/lam-mcp-linux-x64 (MCPB, for a client that installs bundles; probed in a container with the network off)
Host: github.com
Repository: https://github.com/hakimjonas/lambe.git
Registry: active, updated 2026-09-07 · registry entry

Compare this server with others.

More servers

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

Keysrs io.github.gshost1/keysrs · crashed on start
Stallhunt io.github.guillem/stallhunt · crashed on start
DWAI IDE Bridge io.github.guxiaodan333-source/dwai-ide-bridge · not probed
Platter io.github.hadriangateway/platter · alive
MPM-Coding io.github.halflifezyf2680/mpm-coding · not found
MPM-Coding io.github.halflifezyf2680/mpm-vibe-coding · not found
io.github.hanmahong5-arch/wireforge · crashed on start
Gateway Price Disclosure Check io.github.happy520ai/gateway-price-check · alive

Servers that mention lambe.

io.github.SlambertDK/shelfatlas-catalog · alive
astrodynamics-mcp io.github.astro-tools/astrodynamics-mcp · crashed on start

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-11. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.