MCP Registry · v0.50.0
Registry metadata is discovery evidence, not capability evidence
Package availability boundary: commands that use published
@ruleoak/*@0.50.0 packages apply only after those exact npm packages are publicly available. The fresh GitHub v0.50.0 source repository remains the canonical source release.RuleOak can fetch bounded public registry metadata and produce a deterministic inspection queue. It does not invoke mutating tools during registry ingestion.
npx @ruleoak/cli@0.50.0 inspect registry fetch --out .ruleoak/registry/snapshot.json --latest-only
npx @ruleoak/cli@0.50.0 inspect registry queue --snapshot .ruleoak/registry/snapshot.json --out .ruleoak/registry/queue.json
Custom registry endpoints require explicit opt-in. Plain HTTP is refused except for explicitly allowed loopback mirror/test use. Discovery never grants authority.