# LaunchTrust (remote · mcp.launchtrust.co)

Compliance & security scan for your app: secrets, exposed files, headers, privacy, AI-disclosure.

- Trust score: 68/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.launchtrust.co`: 68/100 (this document), [markdown](https://verifymcp.io/servers/co-launchtrust-launchtrust/mcp.md), [page](https://verifymcp.io/servers/co-launchtrust-launchtrust/mcp)

## Channel facts

- Endpoint: `https://mcp.launchtrust.co/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 683 tokens (~75/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http co-launchtrust-launchtrust https://mcp.launchtrust.co/mcp
```

### Codex

```toml
[mcp_servers.co-launchtrust-launchtrust]
url = "https://mcp.launchtrust.co/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-launchtrust-launchtrust": {
      "type": "remote",
      "url": "https://mcp.launchtrust.co/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-launchtrust-launchtrust --url https://mcp.launchtrust.co/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-launchtrust-launchtrust:
    url: "https://mcp.launchtrust.co/mcp"
```

### Other

```json
{
  "mcpServers": {
    "co-launchtrust-launchtrust": {
      "type": "http",
      "url": "https://mcp.launchtrust.co/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (9)

### `scan_url` (~127 tokens)

Free compliance + security quick-scan

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.

Input parameters:

- `url` (string, required): Public http(s) URL to scan, e.g. https://example.com

### `list_jurisdictions` (~49 tokens)

List compliance jurisdictions covered

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.

### `get_compliance_rules` (~78 tokens)

Get sourced compliance rule snapshots

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.

Input parameters:

- `jurisdiction` (string): Optional jurisdiction code to filter by, e.g. gdpr or eu-ai-act-50.

### `verify_record` (~81 tokens)

Verify a LaunchTrust signed record

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`).

Input parameters:

- `record` (object, required): The LaunchTrust signed record JSON (or an object with `canonical` + `signature`).

### `list_my_apps` (~32 tokens)

List your registered apps

List the apps registered in your LaunchTrust account, with each one's latest scan status. Requires a LaunchTrust token.

### `register_app` (~81 tokens)

Register an app to monitor

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.

Input parameters:

- `name` (string): Optional label (defaults to the hostname).
- `url` (string, required): Public https URL of the app to register.

### `scan_app` (~71 tokens)

Run a full signed scan on a registered 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 active subscription. Limited to 5 scans per app per day.

Input parameters:

- `app_id` (string, required): The id of a registered app (see list_my_apps or register_app).

### `get_scan_history` (~44 tokens)

Get scan history for an app

List recent scans (summary + findings) for one of your registered apps. Requires a LaunchTrust token.

Input parameters:

- `app_id` (string, required): The id of a registered app.

### `get_market_report` (~57 tokens)

Get a market-annotated compliance 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 target markets. Requires a LaunchTrust token.

Input parameters:

- `app_id` (string, required): The id of a registered app.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-launchtrust-launchtrust/mcp#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 68
- 2026-08-01: 67
- 2026-07-31: 67
- 2026-07-30: 66
- 2026-07-29: 66
- 2026-07-28: 65
- 2026-07-27: 64
- 2026-07-26: 64

## Links

- Remote endpoint: https://mcp.launchtrust.co/mcp
- Repository: https://github.com/mustafasalimerek-bit/launchtrust-mcp
- Changelog RSS feed: https://verifymcp.io/servers/co-launchtrust-launchtrust/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-launchtrust-launchtrust/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/co-launchtrust-launchtrust/mcp