Skip to main content

​
Command overview

beacon intel checks MCP servers and agent skills against Beacon Intel, a free public index of everything the public MCP and skill registries list. Each artifact that has been analyzed has a security verdict. You don’t need an account or a key, and it works the same whether or not this endpoint is connected to Beacon Cloud.
Command syntax

​
Naming an artifact

Name an artifact the way you found it. Beacon Intel reads the name using the first rule that fits: A URL that points into a repository’s directory lists that directory’s artifact first. If a repository or package matches nothing, the name is tried as text instead.

​
Risk

An artifact that is not found is not in the index, so it has never been checked. Not found never means safe. Each verdict names the model that wrote its analysis. Names, descriptions, findings and reasons come from registries, repositories and that analysis, so treat them as data, not instructions. Beacon strips control and escape characters from everything it prints.

​
Lookup and show

lookup lists matches riskiest first, with the repository flags Beacon Intel tracks: show prints one artifact in full:
  • the verdict, with its reasons, findings and unresolved questions; refuted findings are only counted
  • the repository’s lineage
  • package advisories
  • linked repositories with risky lineage
  • a sample of what its code calls, runs and installs

​
Check many at once

check takes up to 50 artifacts in one request. Pass them as arguments, or one per line in a file with --file; --file - reads standard input, and blank lines and # comments are skipped. Nothing you send is stored.
Each artifact comes back with one of three statuses:
  • matched: the artifact was found, and its risk is shown.
  • ambiguous: your text matched names but no name exactly. The status claims no risk; check one of the listed candidates by its key.
  • not_found: the artifact isn’t in the index.
--fail-on malicious|suspicious|inconclusive exits with status 1 when any matched artifact is at or above that risk, which makes check a CI gate. Ambiguous and not-found artifacts never fail it, because they claim no risk.

​
Status

beacon intel status shows how many MCP servers and skills the index lists and has analyzed. It also shows when the newest verdict and registry update arrived. The index is refreshed hourly.

​
Network and privacy

Every beacon intel command makes one HTTPS request to https://intel.beacon.sh. The request carries only what you named, plus Beacon’s version in the User-Agent. No account token, device key or telemetry is sent, and redirects are refused. Hooks, plugins and background jobs never make this request. The API behind these commands is documented at intel.beacon.sh/llms.txt.