cyfyr
The diagnostic layer for the AI-native stack.
Reads your manifest. Probes every provider. Reports the seams.
Bugs hide in the seams between providers.
A modern app spans five to ten SaaS providers — host, database, auth, payments, email, observability — plus the agent layer that writes the code in the first place.
No single vendor builds cross-provider checks. Stripe doesn't know your webhook target is undeployed. Cloudflare doesn't know which Stripe events Stripe is delivering. The seam between them is invisible to both dashboards — and to every individual provider's CLI.
cyfyr doctor reads from both sides and reports the disagreement.
Read-only. Local. Yours. No telemetry, no account, no enterprise upsell. The check library is the asset — captured scar tissue from real production bugs, growing one PR at a time.
Five checks in v0.1.
Two in the moat.
Single-provider checks are commodities; every provider's own CLI can do them. Cross-provider integrity checks are what nobody else will build — because no individual provider has visibility into the seams, and no provider's incentives align with reporting them.
whoami. Reports authenticated identity. Catches: CLI not installed, expired login, wrong account selected..env, .env.local, .env.production. Catches the classic "works locally, broken in preview" — env vars added to one file but not the others.Your agent stops guessing
and starts querying.
cyfyr ships an MCP server. Wire it into Claude Code, Codex, or Cursor and every conversation gets three new tools: cyfyr_doctor_run, cyfyr_doctor_list, cyfyr_doctor_explain.
imprint.run/api/webhook returns 404 — Stripe is delivering 6 event types to a dead URL. Three ways to fix:1. Deploy a handler at /api/webhook
2. Repoint the Stripe endpoint to your actual handler
3. Disable the endpoint in the Stripe dashboard.
// ~/.claude.json (user-scope) — or .mcp.json per project { "mcpServers": { "cyfyr-doctor": { "command": "node", "args": ["/path/to/cyfyr/out/doctor/mcp.js"] } } }
One config file.
Two commands.
No package to download, no account to make, no key to generate. cyfyr runs against your existing API credentials — nothing leaves your machine.
# 1. clone & build $ git clone https://github.com/electjustinoberg/cyfyr ~/cyfyr $ cd ~/cyfyr && npm install && npm run compile # 2. declare your stack — one .cyfyr/config.json per project $ mkdir -p .cyfyr && cat > .cyfyr/config.json <<EOF { "model": { "provider": "anthropic" }, "host": { "provider": "vercel" }, "db": { "provider": "supabase" }, "payments": { "provider": "stripe" }, "email": { "provider": "resend" } } EOF # 3. diagnose $ node ~/cyfyr/out/doctor/cli.js # (or wire the MCP server above and ask your agent)