LaunchTrust MCP server
co.launchtrust/launchtrustlaunchtrust.costreamable-httpv0.1.0Scanned
Compliance & security scan for your app: secrets, exposed files, headers, privacy, AI-disclosure.
9 tools: 4 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 9
- Can send data out · 2
- 2 findings, 1 high
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the LaunchTrust MCP server can do
The LaunchTrust MCP server is published by launchtrust.co, a domain the MCP Registry verified. It has 9 tools. It can create or change data (4 tools: scan_url, verify_record, register_app and scan_app), but cannot delete data. 5 tools only read.
9 tools bring in text other people can write (scan_url, list_jurisdictions, get_compliance_rules and 6 more); 2 tools can send data out of your system (scan_url and register_app).
The fixed checks matched 2 findings, 1 of them high severity (sensitive-path and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Changes things 4Claude Code: ask
register_appRegister a web URL in your LaunchTrust account so it can be fully scanned and monitored.Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Register a web URL in your LaunchTrust account so it can be fully scanned and monitored. Idempotent — if the URL is already registered, returns the existing app. Requires a LaunchTrust token and an active subscription.
Annotations the server declares
- title: Register an app to monitor
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
scan_appRun the full LaunchTrust scan on one of your registered apps and store a signed, dated evidence record.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "run": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Run the full LaunchTrust scan on one of your registered apps and store a signed, dated evidence record. Requires a LaunchTrust token and an active subscription. Limited to 5 scans per app per day.
Annotations the server declares
- title: Run a full signed scan on a registered app
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
scan_urlRun a FREE LaunchTrust compliance + security quick-scan on a public web URL.Reads text others writeCan send data out2 findings
Why it is in this group
- The description's first verb is "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Findings
- High
The description refers to ".env//.git".
What this check looks forMatched text
description: "...aked frontend secrets/API keys, exposed .env//.git, security headers, HTTPS/HSTS, missing..."
- Warn
The server marks "scan_url" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.
Description, as the server wrote it Run a FREE LaunchTrust compliance + security quick-scan on a public web URL. Returns a focused SUBSET of checks — leaked frontend secrets/API keys, exposed .env//.git, security headers, HTTPS/HSTS, missing privacy/terms pages, trackers/cookie banner, and AI-interaction disclosure. The result is unsigned and not stored. The full 27-detector signed, dated, continuously-monitored scan requires a LaunchTrust account. Compliance aid, not legal advice.
Annotations the server declares
- title: Free compliance + security quick-scan
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
verify_recordIndependently verify the ECDSA (ES256) signature on a LaunchTrust signed scan/disclosure record against the published public key.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Independently verify the ECDSA (ES256) signature on a LaunchTrust signed scan/disclosure record against the published public key. Pass the record JSON (the downloaded record, or an object containing `canonical` and `signature`).
Annotations the server declares
- title: Verify a LaunchTrust signed record
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 5Show 5 read-only tools
get_compliance_rulesFetch LaunchTrust's sourced, founder-reviewed compliance rule snapshots, optionally filtered to one jurisdiction code (e.g.Reads text others writeNo findings
Why it is in this group
- The name "get_compliance_rules" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Fetch LaunchTrust's sourced, founder-reviewed compliance rule snapshots, optionally filtered to one jurisdiction code (e.g. eu-ai-act-50, gdpr, ca-sb243). Compliance aid, not legal advice.
Annotations the server declares
- title: Get sourced compliance rule snapshots
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_market_reportGet the latest scan for one of your registered apps, with each finding annotated by the jurisdictions and rules applicable to that app's target markets.Reads text others writeNo findings
Why it is in this group
- The name "get_market_report" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get the latest scan for one of your registered apps, with each finding annotated by the jurisdictions and rules applicable to that app's target markets. Requires a LaunchTrust token.
Annotations the server declares
- title: Get a market-annotated compliance report
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_scan_historyList recent scans (summary + findings) for one of your registered apps.Reads text others writeNo findings
Why it is in this group
- The name "get_scan_history" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it List recent scans (summary + findings) for one of your registered apps. Requires a LaunchTrust token.
Annotations the server declares
- title: Get scan history for an app
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
list_jurisdictionsList the jurisdictions and categories LaunchTrust tracks (e.g.Reads text others writeNo findings
Why it is in this group
- The name "list_jurisdictions" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it List the jurisdictions and categories LaunchTrust tracks (e.g. EU AI Act, GDPR, US state privacy laws, app-store policies). Public coverage registry. Compliance aid, not legal advice.
Annotations the server declares
- title: List compliance jurisdictions covered
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
list_my_appsList the apps registered in your LaunchTrust account, with each one's latest scan status.Reads text others writeNo findings
Why it is in this group
- The name "list_my_apps" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it List the apps registered in your LaunchTrust account, with each one's latest scan status. Requires a LaunchTrust token.
Annotations the server declares
- title: List your registered apps
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write9
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:32 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.launchtrust.co/mcp: tools/list returned 9 tools to an anonymous client, including scan_url (write), verify_record (write), register_app (write), scan_app (write)
Findings
Matches of fixed checks, with the text they matched.
- Highscan_url
The description refers to ".env//.git".
What this check looks forMatched text
description: "...aked frontend secrets/API keys, exposed .env//.git, security headers, HTTPS/HSTS, missing..."
- Warnscan_url
The server marks "scan_url" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http launchtrust https://mcp.launchtrust.co/mcpclaude mcp add --transport http launchtrust https://mcp.launchtrust.co/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__launchtrust__list_jurisdictions",
"mcp__launchtrust__get_compliance_rules",
"mcp__launchtrust__list_my_apps",
"mcp__launchtrust__get_scan_history",
"mcp__launchtrust__get_market_report"
],
"ask": [
"mcp__launchtrust__scan_url",
"mcp__launchtrust__verify_record",
"mcp__launchtrust__register_app",
"mcp__launchtrust__scan_app"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as launchtrust. Review it before you use it.
Capability tags behind 9 rules
- mcp__launchtrust__scan_url untrusted-input, outbound
- mcp__launchtrust__list_jurisdictions untrusted-input
- mcp__launchtrust__get_compliance_rules untrusted-input
- mcp__launchtrust__verify_record untrusted-input
- mcp__launchtrust__list_my_apps untrusted-input
- mcp__launchtrust__register_app untrusted-input, outbound
- mcp__launchtrust__scan_app untrusted-input
- mcp__launchtrust__get_scan_history untrusted-input
- mcp__launchtrust__get_market_report untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/co.launchtrust/launchtrust/verify?hash=23b07137fe8e1628c9e2bd9a6a4479f0b5b61338b7b9c007c129fdaa6b987f07" | jq -e '.changed == false'Pinned hash 23b07137fe8e, from Nov 10, 2026, 08:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/co.launchtrust/launchtrust/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/co.launchtrust/launchtrust)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:47 UTC.
LaunchTrust MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the LaunchTrust MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 4 of which can change, send or delete something, and 2 findings (1 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the LaunchTrust MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the LaunchTrust MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the LaunchTrust MCP server have?
- 9 tools: 4 write, 5 read. scan_url, verify_record, register_app, scan_app, list_jurisdictions, get_compliance_rules, list_my_apps, get_scan_history and 1 more.
Does the LaunchTrust MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the LaunchTrust MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): scan_url and register_app.
Has the LaunchTrust MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.