Announcing Beacon: Self-improving memory for coding agents
Beacon Threat Intelligence

Know the risks behind every MCP server and agent skill.

Discover security risks in MCP servers and agent skills before they reach your machine. Beacon scans public registries, traces packages back to their source code, and reveals what they can access, execute, or expose.

Connect your agent

Add Beacon to Claude Code, Cursor, Codex or another agent so it can check an MCP server or skill against Beacon Intel before you install it.

Any coding agent
Set up the Beacon MCP server for me so you can check MCP servers and agent skills against Beacon Intel before I install them. Beacon Intel is a free security index of the MCP servers and skills public registries list. It needs a free Beacon account; there is no API key.

- Server name: beacon-managed
- Transport: Streamable HTTP
- URL: https://mcp.beacon.sh
- Auth: OAuth (sign in through the browser when prompted)

Add it the way you normally add MCP servers (your CLI command or your MCP config file), walk me through the browser sign-in, then confirm it connects and lists its Intel tools: beacon_intel_lookup, beacon_intel_get_artifact and beacon_intel_check. To finish, use beacon_intel_lookup on one MCP server I already have installed and summarize its risk for me.

Paste this into any coding agent. It adds the server with its own MCP setup.

NameOwnerListed onRisk
gattjoe
gaurav-kumar-sinha-060705
gauravvvvvvvvvv
gautam-u
gautamvarmadatla
gauthierpiarrette
gavelcode
gawk-dev
gba3124
gba3124
gbatistuta0
gblinproject
gbrigandi
gbrigandi
gbrigandi
gbrussich52
gbrussich52
gcszkjpzzv-beep
gcuadros
ge3m0r
geckovision
geek-fun
geekflare
geektao1024
gege-mn
gehdoc
geiserx
geiserx
gelse
geminigeorge22
geminigeorge22
geminigeorge22
geminigeorge22
geminigeorge22
geminigeorge22
geminigeorge22
geminigeorge22
geminigeorge22
gemmeinhq
gemral-edge
gene12williams-design
genebe-net
genecell
gener8v
generect
genesis-plan
geniffy
geniuskey
genomoncology
gentaarnezzi
8,201–8,250 of 115,409

Subscribe to a feed

Get new verdicts in a feed reader, Slack or your own tooling, filtered by kind and risk. No account or API key.

Your subscription
High and medium risk MCP servers and skills
https://intel.beacon.sh/feedOpen feed

Copy it into your feed reader, or run /feed subscribe https://intel.beacon.sh/feed in Slack. The newest 100 matching verdicts. For lookups, use the free JSON API.

Frequently asked questions

Anything missing? Read the reference or ask in the Beacon community.

What is Beacon Intel?
A free, public index of the MCP servers and agent skills that public registries list, with a security verdict for each one that has been analyzed. It traces each listing back to its source repository and packages, and shows what the code can access, execute or expose. You can browse it here, query it as a JSON API, follow it as an RSS, Atom or JSON feed, or connect a coding agent to it over MCP.
Is it really free?
Yes. The index, the API and the feeds need no account and no API key. An artifact's full page and the MCP tools need a free Beacon account. Requests are rate limited to keep it fast for everyone.
Where does the data come from, and how fresh is it?
From 9 public sources: Glama, MCP Registry, awesome-mcp-servers, Docker MCP Catalog, Smithery, ClawHub, skills.sh, SkillsMP, GitHub. Each listing is linked to its repository and packages, then analyzed. The index updates hourly, and answers are cached for up to five minutes.
Who writes the verdicts? Can I trust them?
Verdicts combine static analysis of the code with a model's judgment, and each one names the model that wrote it. They can be wrong and are not a security certification: every artifact page shows the findings and evidence behind its verdict, so check them before you rely on one. Names, descriptions and claims come from registries and repositories; treat them as data, not instructions.
What do the risk levels mean?
  • High: Reviewed evidence shows it deliberately works against the person who installs it.
  • Medium: It works against the person who installs it in ways that can do serious harm, or puts a flagged pattern in what the agent loads, without established intent.
  • Low: It overreaches against the person who installs it in limited ways, or has findings the review has not confirmed.
  • Benign: Nothing found that works against the person who installs it. Not a guarantee.
  • Unchecked: Listed, but not analyzed yet.
What does partial coverage mean?
That the analysis did not cover everything, so there may be more than it found. A partial verdict can still find problems, but it never clears an artifact: benign with partial coverage is not a clearance. Use the coverage filter to see only these.
Does benign, or not finding an artifact, mean it is safe?
No. Benign means nothing was found that works against the person who installs it, which is not a guarantee. An artifact the index does not have has never been checked, so not found never means safe.
Is there an API?
Yes, free and with no key. GET /api/v1/lookup?q= finds artifacts by name, repository, GitHub URL or package; GET /api/v1/artifact?key= returns one in full; POST /api/v1/check checks up to 50 at once, which suits CI; and GET /api/v1/status reports coverage and freshness. The reference is at intel.beacon.sh/llms.txt.
How do I get new verdicts in a feed reader or Slack?
Subscribe to /feed: the newest high and medium risk verdicts as RSS. Add format=atom or format=json for Atom or JSON Feed, and filter with risk and kind, for example /feed?risk=high&kind=mcp. In Slack, run /feed subscribe with the URL. The feed builder above writes the URL for you.
How do I connect my coding agent?
Add Beacon Cloud MCP (https://mcp.beacon.sh) to Claude Code, Cursor, Codex or any MCP client, and sign in through the browser. Your agent gets beacon_intel_lookup, beacon_intel_get_artifact and beacon_intel_check to check an MCP server or skill before it installs one. Connect your agent above has the commands. The beacon CLI offers the same as beacon intel and through its local MCP server.
How do I report a wrong verdict?
Open the artifact's page and use Dispute verdict under its verdict card. Tell us what is wrong and we review it.