CheckMyLaunch MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHECKMYLAUNCH_API_KEY | Yes | Your CheckMyLaunch API key from your account page. | |
| CHECKMYLAUNCH_API_URL | No | Override the API base URL (defaults to https://www.checkmylaunch.com) | https://www.checkmylaunch.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_repoA | Run a CheckMyLaunch readiness scan on a public GitHub repository. Finds exposed secrets, security risks, deployment problems and launch blockers, and returns a readiness score plus a findings list. Use this after making changes to a project to check it is safe to ship. Only works on public repos reachable at github.com// — private repos need the signed-in flow at checkmylaunch.com. |
| scan_urlA | Run a CheckMyLaunch readiness scan on a live website URL. Checks security headers, cookie flags, TLS, exposed sensitive paths, mixed content, broken links and metadata, and returns a readiness score plus a findings list. Use this to check a deployed site before announcing a launch. |
| get_repair_promptA | Get a ready-to-use repair prompt for one finding from a previous scan_repo or scan_url result. The returned prompt is safe to run as-is in a coding tool: it names the exact fix, forbids unrelated changes, and never deploys or rotates secrets automatically. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: scan_repo scans a repository, scan_url scans a live URL, and get_repair_prompt provides repair instructions. No overlap.
All tools follow a consistent verb_noun snake_case pattern: scan_repo, scan_url, get_repair_prompt. Highly predictable.
Three tools is a reasonable minimal set for a security scanning server. While it could be expanded, the count is appropriate for the core functionality.
The set covers scanning code (repo) and live sites (URL), plus remediation (repair prompt). A minor gap is lack of result listing or management, but core workflows are covered.