Status

Data source, sync freshness, and runtime health.

Use this status surface before treating Git.Top recommendations as production-grade. It exposes whether the public API is D1-backed, whether sync is fresh, and how much of the seed corpus has been indexed.

Health JSON Sync JSON Quality governance Corpus coverage
RuntimeOK

D1 binding is available.

Data sourced1

d1_query

Synchealthy / fresh

Last success 2026-09-26T15:31:15.026Z.

Derivedfresh

Alternatives rebuilt 2026-09-25T09:31:23.179Z.

Indexed1213

500/500 seed repositories synced.

Sync Progress

Healthy

Cycle progress12% · cursor 60 of 500
Remaining seed items0 repositories remain before the current cycle is complete.
Next batch wrapsNo
Next batch previewdocker/mcp-registry, upstash/mcp-server, supermemoryai/supermemory-mcp, apify/apify-mcp-server, TencentEdgeOne/edgeone-pages-mcp
Refresh tiers125 hot, 863 warm, 225 cold.
Refresh due5 hot, 0 warm, 0 cold; includes the pre-expiry lead window.
Stale by policy0 hot, 0 warm, 0 cold; oldest 0d.

Recent Runs

Latest sync attempts

cron · 2026-09-26T15:31:15.026Z8 synced, 0 failed, 0 alternatives updated, 16172ms.
cron · 2026-09-26T15:01:17.303Z8 synced, 0 failed, 0 alternatives updated, 15953ms.
cron · 2026-09-26T14:31:16.362Z8 synced, 0 failed, 0 alternatives updated, 15479ms.
cron · 2026-09-26T14:01:25.617Z8 synced, 0 failed, 0 alternatives updated, 16309ms.
cron · 2026-09-26T13:31:11.631Z8 synced, 0 failed, 0 alternatives updated, 14468ms.

Integration Guidance

When to fail closed

Require D1 for production answers.Use require_d1=true on REST knowledge endpoints when seed fallback is not acceptable.
Check source and freshness together.Prefer metadata.source=d1, sync.health=healthy, and sync.freshness=fresh before citing high-confidence recommendations.
Use quality and coverage for context.Pair this page with /quality and /coverage before broad selection tasks.