ECOSYSTEM DISTRIBUTION · PRIVATE BETA
Verify and distribute your MCP server across AI ecosystems.
Schema quality gate, JSON-RPC validation, packaging for Smithery, Cursor, Glama, Claude Desktop — with a proof badge. You approve before listing.
Private beta · No card required · No auto-approval of mutations
Machine-verifiable artifact
Sample MCP quality scorecard & manifest
Verifiable quality audit output documenting schema conformance, parameter typing, and multi-catalog packaging.
# Launchfiles MCP Quality Scorecard & Manifest
audit_id: "mcp_audit_100_pass"
protocol: "Model Context Protocol (MCP)"
compliance:
json_rpc: "2.0 verified"
json_schema: "100% parameter types declared"
security_attenuation: "zero ambient shell exec"
manifests_generated:
smithery: "smithery.yaml ready"
cursor: ".cursor-plugin/plugin.json ready"
glama: "glama.json ready"
claude_desktop: "mcp.json snippet ready"
verification_status: "VERIFIED_GRADE_A_PLUS"
human_boundary: "generates catalog manifests for your approval"
status: "HARD_GREEN_VERIFIED"
signed_by: "Launchfiles Deterministic Verification Gate"
Verified quality gates unlock instant ecosystem distribution
Listing broken or unvalidated MCP tools destroys user trust. Launchfiles probes your MCP server, verifies JSON-RPC 2.0 and JSON Schema compliance, checks security attenuation, and generates catalog manifests for your approval with verifiable quality badges.
MCP Quality Scorecard
Comprehensive 0–100 audit of schema validity, parameter typing, and security.
Smithery.ai Manifest
Production-ready smithery.yaml for 1-click cloud & stdio installation.
Cursor Plugin Package
Complete .cursor-plugin/plugin.json configuration.
Public Verification Badge
Embeddable SVG and Markdown proof badge with permanent receipt URL.
Approval required: Manifests are generated for your inspection. Launchfiles never auto-publishes to third-party catalogs without your explicit sign-off.
HOW IT WORKS (MISSION HANDOFF)
From problem to next safe action
Three steps to a verified mission handoff.
Probe & score
Audit schema, JSON-RPC, security
Package
smithery.yaml, plugin.json, glama.json, mcp.json
You approve
listing/publish only after human sign-off
Built for MCP tool authors
Clear boundaries on who this workflow serves.
Who this is for
Founders, API developers, and MCP tool authors who want their servers verified, packaged, and discovered by AI developers on Smithery.ai, Cursor, Glama, and Claude Desktop.
Who this is not for
Un-gated or autonomous publishing without review. If you want to connect existing MCP tools to your agent instead, see Use from Agent for consumer MCP setup.
Frequently asked questions
Everything you need to know about MCP server verification and ecosystem packaging.
- What is the Model Context Protocol (MCP)?
- MCP is an open standard that connects AI assistants and coding agents to external developer tools, databases, and APIs securely through standardized JSON-RPC protocols.
- How does Launchfiles secure MCP tool execution?
- Launchfiles wraps MCP tool calls inside bounded authority envelopes with strict spend ceilings and approval gates for write operations, preventing rogue tool execution and ambient shell escapes.
- Does Launchfiles automatically publish or list my server?
- No. Launchfiles generates catalog manifests and runs compliance gates for your approval. You retain full control over when and where your MCP server is published or listed.
- Which AI catalogs and developer tools are supported?
- Launchfiles packages validated manifests for Smithery.ai, Cursor plugins (.cursor-plugin/plugin.json), Glama, and Claude Desktop configuration.
ECOSYSTEM DISTRIBUTION · PRIVATE BETA
Run one bounded MCP audit with a scorecard.
Schema quality gate, JSON-RPC validation, packaging for Smithery, Cursor, Glama, Claude Desktop — with a proof badge. You approve before listing.
Private beta · No card required · No auto-approval of mutations