Publishing an MCP plugin

The Rigyx MCP marketplace lets you ship a Model Context Protocol plugin to every Rigyx business. Free or paid. 15% take on free publishers, 30% on premium — you keep the rest. Payouts via Stripe Connect.

The 5-step workflow

1. 1

   Build your MCP server

   Rigyx runs standard MCP servers built with any official SDK (TypeScript, Python, Go, Rust). Expose tools + resources + prompts via the protocol. If your server is stateful, design for short-lived connections (Rigyx pools and re-uses connections across invocations).

   Your server should be reachable at an HTTPS URL. For development, Rigyx accepts http://localhost origins.

2. 2

   Author the signed manifest

   Every published plugin ships with an Ed25519-signed JSON manifest that describes its tools, required permissions, pricing, and contact info. Example:

   {
     "slug": "linkedin-outbound",
     "display_name": "LinkedIn Outbound",
     "version": "1.0.0",
     "server_url": "https://mcp.example.com/linkedin",
     "publisher": {
       "name": "Acme Integrations",
       "contact_email": "[email protected]",
       "public_key": "<ed25519_pubkey_base64>"
     },
     "permissions": ["read:leads", "write:messages"],
     "price": { "model": "subscription", "monthly_cents": 900, "currency": "usd" },
     "tools": [
       { "name": "send_dm", "description": "Send a LinkedIn DM to a connection" }
     ]
   }

   Sign the manifest with your Ed25519 private key and publish the signature alongside it. Rigyx verifies on submit and on every install.

3. 3

   Verify your publisher identity

   Before your first submission, verify you control the publisher contact_email AND the domain of the server_url:

   • Email OTP — we send a 6-digit code to your contact_email
   • Domain — either a DNS TXT record at _mcp-publisher.yourdomain whose value is your verification token, or a file at https://yourdomain/.well-known/mcp-publisher.json that contains {"token": "<your token>"}

   Both checks run in the dashboard at /dashboard/integrations/publisher, which also shows your token. A verified publisher gets a Verified badge on every listing.

4. 4

   Submit to the review queue

   Upload the manifest + signature at /dashboard/integrations/submit. Our security scanner runs automatically and checks:

   • Signature verifies against the registered public key
   • Declared permissions match the tools the server actually exposes
   • No injected prompt text in tool descriptions ("ignore previous instructions" = auto-reject)
   • Server URL not a loopback / private network in production
   • Pricing consistent with the Rigyx marketplace take rate

   Auto-pass scanner issues move your submission to human review. Our SLA is ~48 hours. Rejections include specific reasons and a link to fix + resubmit.

5. 5

   Connect Stripe & earn

   For paid plugins, complete Stripe Connect onboarding at /dashboard/integrations/publisher. You keep 70–85% of every subscription; Rigyx takes 15% (free-tier publishers) or 30% (premium publishers).

   Every transfer to your Stripe account is listed in the payout history on the same page.

Permission catalog

Plugins request specific permissions. Customers see the list before install and can revoke at any time.

FAQ