Developer · Remote MCP server
LaunchTrust
Compliance & security scan for your app: secrets, exposed files, headers, privacy, AI-disclosure.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
co.launchtrust/launchtrust- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-06-26
- Updated
- 2026-06-26
- Publisher
- co.launchtrust
- Namespace
- Namespace verified by the MCP Registry via the domain launchtrust.co · how
- Repository
- github.com/mustafasalimerek-bit/launchtrust-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.launchtrust.co/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- launchtrust 0.1.0 · protocol 2025-06-18
- Tools discovered
- 9:
scan_url,list_jurisdictions,get_compliance_rules,verify_record,list_my_apps,register_app,scan_app,get_scan_history,get_market_report - Checked on
- 2026-10-05
How to connect LaunchTrust
LaunchTrust is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.launchtrust.co/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| LathePostgres, Redis, CouchDB, NATS, your app and its sign-in on one dedicated machine, one flat price. | Remote · HTTPLive check: sign-in required |
| LatinGrounds LLMs in real Latin: Wiktionary lemmas, Morpheus inflections, citations. | Remote · HTTPLive check: ✓ handshake |
| Latitude 10 StoreDeveloper kits and design packs for AI agents, paid in USDC over x402. Free API readiness check. | Remote · HTTPLive check: ✓ handshake |
| LaunchFlagFeature flags and kill switches. Turn a shipped feature off in production without a deploy. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Lawang OnboardPermission-aware onboarding MCP server: answers about a codebase, filtered by the caller's role. | Remote & Local · HTTP, stdioLive check: sign-in required |
| LayeroDeploy and operate sites on Layero - hosting with build servers in Russia: domains, env, Data API. | Remote · HTTPLive check: ✓ handshake |
| LazywebReal product evidence: 281k+ real app screens and flows, 20k+ mobile A/B tests, growth reports. | Remote · HTTPLive check: sign-in required |
| LBrainLocal-first agent memory. Source, date, bind/abstain. Permanent name: lbrain.ai/claim.html. | Local · stdio |