Skip to content

Browsing and reading a report card

The registry's job is to let you judge a QuickAgent before it touches your machine.

Browse

Browse (/search) searches names, summaries, and READMEs. Filters narrow the results by run mode, declared capability, license (faceted from what has actually been published), verified organizations, and sort order (best match, most installed, newest). Every result carries its run-mode badges — autonomous, interactive, or both. Each badge carries what its mode means as hover text, and so does every option in the mode filter.

Click anywhere on a result row to open its detail pane beside the list: the latest version, the scan verdict, declared capabilities, license, and the install command, without leaving the list. Its last line sends you to the report before you install. Click the namespace/name identifier itself to go to the full page. The pane's state lives in the URL, so a filtered view with a selection can be shared as a link.

The QuickAgent page

What the page shows:

  • Run modes — the badges beside the name say how the release runs: from its files to a result (autonomous), as a conversation (interactive), or either. The package format explains what each means.
  • Declared capabilities — what the manifest claims to need: network egress, filesystem access, exec, secret names, data categories, MCP servers. These are the author's declaration and the basis for scanning and policy; the registry cannot enforce them at run time. Your runtime should.
  • MCP servers & tools — exactly which tools the runner will grant for this contract, and each MCP server the release declares, with its exact package version and the tools it is limited to. Each server carries the registry's last vulnerability check of that version: "no known advisories as of …", or the advisories it carries.
  • Dependency alerts — when a published version declares an MCP server version that has since gained a high or critical advisory, the page says so above the advisories, with the advisory ids and the fixed versions. The author sees the same alert as a banner after signing in and on the dashboard, and can switch the banner off in settings.
  • Security report — "scanned, N findings, signed", never "safe". The card carries the scan date, and the ruleset version, adjudication model and scan status where the report records them, so you can judge how fresh the check is. The full report lists every finding, and reviewer dismissals stay visible with their rationale.
  • Install — the command per target, and the git clone URL (HTTPS, and SSH when the instance advertises it).
  • Code & README — a file browser over the release archive, which is the exact content an install receives, with the README under it. Invisible characters — zero-width, bidirectional and tag characters — render as visible placeholders in the README and in the file view, as they do on the review page.
  • Provenance — the archive digest, where the release came from, and the agentry verify command. It re-downloads the release, recomputes the digest and checks the signature against the registry's signing keys, pinned on first use. The key id is on the version page, beside the full report.
  • Releases and advisories — the twelve newest versions with their status (published, yanked, quarantined, blocked), and every advisory the registry has raised against this QuickAgent. The registry's /advisories page is the global feed, newest first, each advisory with a permalink.

Stars and install counts are popularity signals, not safety signals, and the page says so where it shows them.