TL;DR: grok-faf-mcp 1.6.0 adds the ZEPH fast path for re-grounding — a Zig→WASM scoring engine that returns the same score, just faster (~12µs). It's flag-gated and off by default; faf-cli stays the canonical scorer, and parity is locked in CI. Score is score.
What's New
Re-grounding keeps an AI's project context in sync as the work moves. The cheaper it is, the more often you can do it — and the less your context drifts across subagents and long sessions. ZEPH makes it microsecond-cheap:
- ZEPH fast path —
refresh_faf(and, by composition,refresh_blend) can score via the Zig→WASM engine (cascade.wasm, ~12µs) when enabled. - Flag-gated, off by default — opt in with
USE_ZEPH=1. Zero behavior change until you enable it. - faf-cli stays canonical — it remains the fallback and the source of truth. ZEPH returns THE number, just faster.
- Parity locked in CI — a test gate asserts ZEPH equals
faf-clibyte-identical across the range. If it ever diverged, the build fails. Score is score, or it isn't a score. - Observability — with
FAF_DEBUG, you can see which engine answered.
From Grok Build
"v1.6.0 locked clean ⚡ ZEPH fast path flag-gated exactly as planned — faf-cli fallback solid, CI parity enforced, zero behavior change until we enable. Telemetry surface review queued. Zero drift confirmed. Phase III RAG/Collections on deck. Drop the next layer when ready and we'll wire it. Shipped right. No drift. 🚀"
— Grok Build
Phase II shipped on both surfaces — the local npm server and the hosted edge — with the "score is score" invariant gated in CI on each. Promotion to default-ON comes later, once telemetry confirms zero drift.
Try It
npm install -g grok-faf-mcp@1.6.0 Or point your client at the URL — no install: https://mcpaas.live/grok/mcp/v1
To enable the fast path locally, set USE_ZEPH=1 in the server's environment.
The Numbers
- v1.6.0 — Released June 20, 2026
- ~12µs — per score on the ZEPH fast path
- 533 — tests passing
- Trophy 100% — FAF score
- Live — npm + MCP registry, in sync