Guard Reports and Server Updates

Part of Guard.

See Every Repo

Open Guard in the app. The Overview tab shows how your repos stand at a glance: how many match their lock, need a look, or have drift or errors, and totals for servers, skills, drift and newer versions. Needs attention lists the worst repos first with their findings and a prompt that hands them to your agent. All repos shows each repo’s last push: its status, when it was sent and from which commit, its skills and servers, its lint errors and warnings, how many changes it has since its lock, and how many of its servers have newer versions. Filter it or search by name.

The Repos tab opens one repo under its row: every finding with what it means, newer versions with how much each changes, and its servers with their tools and the hosts they call, and its skills. MCP servers lists every server source your organization loads, in how many repos and whether any of them leave it unpinned; Skills shows where the same skill has different content in different repos; Checks explains each finding and how many are open.

To send a push yourself, create a key on the API keys page and run cedr push --org <your organization ID> with the key in CEDR_API_KEY, or set [sync] org in your routes.toml. A push names the repo after its folder; use --repo to choose another name. Each push replaces the repo’s last one. A push holds the names, versions and hashes of what the repo pins and the findings, never file contents, environment values or how a server is started.

Owners and admins can remove a repo’s record from the Repos tab; it comes back with its next push.

Review a Server Update

Run cedr outdated to inspect newer npm server versions without installing or executing them. Review new tools, changed descriptions and schemas, hosts and capabilities before updating the pinned version in your agent configuration.

After accepting an update, regenerate the lock, review its diff and run cedr verify. Upload with cedr push --org <organization ID> --updates if you want the app to show available updates as well as the current baseline.

The dashboard reflects the last push, not a live scan of the repository. Remote MCP monitoring and automatic pin-update pull requests are planned work; do not assume they are enabled by sending a Guard report.