Categories › Security › Code & dependency scanning
Compliance & security scan for your app: secrets, exposed files, headers, privacy, AI-disclosure.
Remote server: your requests and data go to mcp.launchtrust.co. Claude Code: claude mcp add --transport http launchtrust https://mcp.launchtrust.co/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
scan_url — Run a FREE, count-only LaunchTrust quick scan on a public web URL. It runs a quick subset of LaunchTrust's compliance and security checks (flist_jurisdictions — List the jurisdictions and categories LaunchTrust tracks (e.g. EU AI Act, GDPR, US state privacy laws, app-store policies). Public coverage get_compliance_rules — Fetch LaunchTrust's sourced, founder-reviewed compliance rule snapshots, optionally filtered to one jurisdiction code (e.g. eu-ai-act-50, gdverify_record — Independently verify the ECDSA (ES256) signature on a LaunchTrust signed scan/disclosure record against the published public key. Pass the rlist_my_apps — List the apps registered in your LaunchTrust account, with each one's latest scan status. Requires a LaunchTrust token.register_app — Register a web URL in your LaunchTrust account so it can be fully scanned and monitored. Idempotent — if the URL is already registered, retuscan_app — Run the full LaunchTrust scan on one of your registered apps and store a signed, dated evidence record. Requires a LaunchTrust token and an get_scan_history — List recent scans (summary + findings) for one of your registered apps. Requires a LaunchTrust token.get_market_report — Get the latest scan for one of your registered apps, with each finding annotated by the jurisdictions and rules applicable to that app's tarNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.