Launcher MCP server
io.github.oneprofile-dev/mcp-launcher·v2.1.1·1 starsSingle MCP hub: discover, add, audit, and govern MCP servers across every AI client.
1 stars36 downloads/wk
Reviews
Write oneNobody has reviewed Launcher yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Launcher tools (5)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
add_to_stackAdd an MCP server to your Launcher stack so its tools become available through Launcher in every AI client. The server's tools appear as `<slug>__<tool>` after the AI client is restarted.
get_server_detailsGet full details about a specific MCP server including install instructions
install_serverGet the manual install configuration snippet for an MCP server (use add_to_stack instead if you want it managed by Launcher)
list_categoriesList all available MCP server categories
search_serversSearch the CuratedMCP catalog for MCP servers by keyword, category, or use case
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- Code scan68 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 59 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Launcher compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- Tools
- 5
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 1
- more than 65% of 28,688 servers
- Downloads a week
- 36
- more than 26% of 12,191 servers with a package
What its tools let an agent do: 3 read · 1 create · 1 run or deploy
Install Launcher in Claude Code, Cursor or VS Code
Runs npx -y curatedmcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mcp-launcher -- npx -y curatedmcp
What the publisher says
From the Launcher repository's README, as published. We do not edit it. Read it on GitHub
curatedmcp
The CuratedMCP Agent. One CLI to discover, run, audit, and govern every MCP server your AI tools (Claude, Cursor, Windsurf, Copilot, Gemini) use.
# 10-second risk scan of your machine — no signup
npx curatedmcp auditPlug it in once. Add servers anytime. Audit and govern them from one place.
What you get
1. Audit (the wedge — start here)
npx curatedmcp auditScans every MCP config file on your machine (Claude Desktop, Cursor, Windsurf, Claude Code, …), classifies each server against the CuratedMCP catalog, and flags:
- 🔴 HIGH — unverified or known-risky servers with credentials
- 🟡 MEDIUM — verified servers running outside catalog defaults
- 🟢 VERIFIED — known-good catalog servers
No signup, no cloud, no data leaves your machine. Logged in? Add --sync to push the result to your dashboard.
2. Run as the MCP Hub
If you use MCP servers across multiple AI clients, you've felt this pain: configure GitHub MCP in Claude Desktop, then re-do it in Cursor, then in Windsurf. New agent ships? Re-paste every config.
The agent fixes that. It's one MCP entry that fans out to every server you've added, in every AI client.
Claude Cursor Windsurf Copilot Gemini
\ \ | / /
┌──────────────────────────┐
│ curatedmcp │ ← one config in each agent
│ (the MCP hub) │
└────┬──────┬──────┬───────┘
│ │ │
GitHub Postgres Stripe ← `add`'d once, available everywhereAdd it to your AI client
{
"mcpServers": {
"curatedmcp": {
"command": "npx",
"args": ["-y", "curatedmcp"]
}
}
}Add servers to your stack
npx curatedmcp add github # prompts for GITHUB_TOKEN
npx curatedmcp add postgres --env DATABASE_URL=postgres://...
npx curatedmcp listRestart your AI client
Tools appear with a __ prefix:
- githubcreateissue
- postgres__query
- filesystemreadfile
3. Guard (local action firewall)
npx curatedmcp guard -- npx -y @modelcontextprotocol/server-githubShortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Launcher: common questions
- Is Launcher MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Launcher safety report
- How do I install Launcher?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Launcher need an API key?
- No secret keys are declared. It reads 1 setting from the environment.
- Is Launcher maintained?
- The last commit was 98 days ago (2026-07-29). The latest release is v2.1.1.
- How does Launcher compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.