Agent/MCP Audit Sprint

Public MCP scan radar

MCP Security Radar

A no-execution snapshot of popular public MCP repos across browser automation, DevTools, GitHub, database, cloud, Notion, Atlassian, and browser-control surfaces. Scores are heuristic triage signals, not confirmed vulnerabilities or certifications.

Sample8 public repos
MethodUp to 90 selected text files per repo
SafetyNo dependency install or target code execution
HandoffUSD $1,000 human audit for one repo or slice

How to read this

Use the score to prioritize review, not to claim a bug

The scanner fetched public GitHub metadata plus a limited set of raw text files from each repo on June 20, 2026 Asia/Shanghai time. It looked for MCP surfaces, remote transports, write actions, credentials, auth gates, redaction, tests, and CI.

A low score means the selected files produced more review signals. It may also miss tests or controls that live outside the fetched slice, so paid work still starts with scope confirmation and fresh validation.

Browser automation surfaces need special review for clicks, sessions, page content, and downloads.
Cloud, database, GitHub, Notion, and Atlassian tools need write-mode and credential boundary tests.
Each card links to a shareable browser scan so maintainers can reproduce or rerun a public triage pass.

Radar snapshot

Popular public MCP repos with review signals

Convert a signal

When to use the paid audit

  1. You have remote transport, hosted MCP, browser-control, cloud, database, or account-writing tools.
  2. The free scan points to write actions, credential paths, missing redaction evidence, or weak test visibility.
  3. You need human validation, source-specific evidence, a ranked fix plan, and launch notes.
  4. Payment starts only after written scope acceptance; the fixed quote is USD $1,000.