io.github.justinwilliames/orbit-lifecycle-mcp

Orbit

Is the Orbit MCP server down? Yes. It has given no valid answer since 2026-10-26: not found.

Lifecycle marketing in Claude: Braze, email QA, deliverability, segmentation. Free, no key.

not found down since 2026-10-26 · probed 2026-11-14 · unchanged since 2026-11-02

download answered HTTP 404

Bundle: https://github.com/justinwilliames/orbit-for-claude/releases/download/v0.43.2/orbit-lifecycle-marketing-system-for-claude.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
Host: github.com
Website: https://yourorbit.team
Registry: deprecated, updated 2026-09-22 · registry entry

More servers

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

Contract Risk Review io.github.justingyang218/contract-risk-review-mcp · install failed
xcforge - iOS MCP Server & CLI io.github.justinthevoid/xcforge · install failed
Orbit io.github.justinwilliames/braze-lifecycle-mcp · not found
Orbit io.github.justinwilliames/orbit-for-claude · not found
JustRouting MCP Server io.github.justrouting/justrouting · install failed
Cairn io.github.juw12/cairn · alive
precedent io.github.juw12/precedent · alive
io.github.kKEo/memors · install failed

Servers that mention lifecycle.

LLMIntel Model Lifecycle ai.llmintel/model-lifecycle · alive
Assetize — IBM Maximo knowledge au.com.assetize/maximo · alive
pdfs.build build.pdfs/pdfs-build · needs auth
AGI Alpha com.agialpha/agi-alpha · not found
com.fadehost/mcp · alive
FillStub - options trading journal com.fillstub/options-trading-journal · alive
Constat MCP — FDA Device Evidence Lifecycle com.healthai/radar · rejects our protocol version
io.github.Massed-Compute/mcp · needs auth

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

No valid answer since 2026-10-26, in every probe since then.
The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.