Your endpoint
Keep your infrastructure. You manage deployment, uptime and storage.
Why MCPRush
Discover. Connect. Publish.One MCP marketplace.
Find MCP servers and agent skills, review available security findings, and connect the tools you need. Publish your own with hosting, paid access and product management in one place.
Building tools? Explore publishing
PublishConnect or downloadManage
MCP servers and agent skills
From project to customer
Your product
MCP server or agent skill
MCPRush
Listing · Access · Payments
Your customers
Connect an MCP · Download a skill
Hosting options for MCP. File delivery for skills.
Compare what you can actually do.
Compare publishing, hosting, access and fees. Select the platforms you’re considering.
Registry & gateway
Marketplace platform
Registry & gateway
| Criterion | MCPRushMCP marketplace | SmitheryRegistry & gateway | ApifyMarketplace platform |
|---|---|---|---|
| Paid MCP access | Available: Publisher-set subscriptionsMonthly plans with a call allowance and an optional rate limit, $5–$999. There is no per-call billing. | Not documentedPublisher billing not documentedSmithery's own pricing and docs describe only what the consuming account pays Smithery per RPC; no mechanism for a publisher to charge end users (subscription, per-call or per-event) appears in any page read. | Available: Pay-per-event chargingA publisher deploys the MCP server as an Actor and charges money per run, per API call, per tool call, per resource read or per custom event by adding Actor.charge() to the code; a flat monthly Rental model also exists but is being sunset. |
| Sell agent skills | Available: Free or one-time purchaseSkill files are delivered to the customer; a skill never passes through the gateway. | Not documentedSkills registry, no pricingSmithery runs a public skills registry of GitHub-backed, installable skills with install counts and a quality score, but no page read exposes a price, purchase or payout field for skills. | LimitedSkills free, open sourceApify ships Agent Skills and a community repo for third-party skills, but the skills themselves are open-source files installed via the skills.sh CLI — the documented way to earn money is the paid Actor the skill calls, not the skill file. |
| Hosting choice | Available: MCPRush or your endpointManaged hosting builds from a public GitHub repo, npm, PyPI or a container image, within account limits. An endpoint you run stays yours. | Available: Hosted or your URLA release can be hosted on Smithery (JS module upload), external (your own public HTTPS endpoint, proxied by the Gateway), or a stdio MCPB bundle, and the registry exposes whether a server is Smithery-hosted. | Available: Apify hosts; proxy allowedApify runs the server for you via Actor Standby with auto-scaling and no infrastructure to operate, and an existing or third-party remote MCP server can be wrapped and re-exposed behind the Apify endpoint instead of being rewritten; compute is billed in compute units at $0.2/CU (Free and Starter), $0.16/CU (Scale) and $0.13/CU (Business). |
| Version control | Available: Promote or roll backA release is cut, promoted when you are ready and rolled back to a previous one; a customer can pin a version in the gateway address, and a release that widens the tool surface waits for each install to accept it. | LimitedRelease history, no pinningSmithery keeps a per-server release history that a publisher can list and inspect (status, git commit, branch, build logs, timestamps), but the pages read document no version number on the public server record, no. | Available: Versioned builds, pin, rollbackMCP servers are Actors, so they inherit Apify's versioning: MAJOR.MINOR semantic versions (up to 10 per Actor) with auto-numbered builds and tags such as latest or beta, customers can pin an exact build tag or. |
| Access and usage controls | Available: Gateway checksCalls routed through MCPRush are checked for the customer’s key, the install, the plan allowance and the rate limit before they are forwarded. | Available: Gateway + scoped tokensAll calls route through Smithery's Connect gateway, where scoped service tokens constrain which namespaces, resources and operations a caller may reach, and each plan carries a monthly RPC allowance with custom rate limits on the enterprise tier. | Available: Token gateway, spend capsCalls go through Apify's own MCP endpoint at mcp.apify.com, which requires an Apify API token or OAuth and is rate-limited to 30 requests per second per user, while a per-run maximum total charge stops further charging and aborts the run, and each plan caps concurrent runs (5 on Free up to 256 on Business). |
| Release security reports | Available: Available-source scanningA report belongs to one release and one source. Servers on npm, PyPI or a public GitHub repo can be scanned; some releases have no completed scan. | Not documentedQuality score, not securitySmithery scans a published server, but the docs describe that scan as metadata extraction, and the per-server badge is labelled a quality score based on best practices and reliability; no security scan, audit or vulnerability result per release or source appears on any page read. | Not documentedPlatform SOC 2 onlyThe pages reviewed document platform-level assurance (SOC 2 Type II, a Trust Center, a security whitepaper and a vulnerability disclosure policy) but do not describe any published per-release or per-source security scan or audit result for individual Actors or MCP servers in the Store. |
| Publisher platform fee | Available: 12% of net salesNet sales are what is left after refunds and chargebacks. Payment processing fees are separate. | Not applicableListing free, no rev-shareSmithery does not sell access on a publisher's behalf, so there is no revenue share or payout to state; the platform fee for listing is explicitly zero, and the only charge on the platform is the consumer's own RPC bill. | Available: 80% to the developerThe developer earns 80% of revenue minus platform usage costs (Apify keeps a 20% commission, and the usage cost can optionally be passed to the user instead), publishing itself has no upfront fee, payout invoices are generated on the 11th of each month with a 3-day review window, and payout minimums are $20 for PayPal and Wise or $100 for other methods. |
| Public catalogue | Available: Public, no sign-inListing pages, with their release and scan details, are readable without an account. | Available: Public, browsableA public, filterable catalogue of MCP servers and a separate skills registry are browsable on the site and queryable through a search API with full-text and semantic search. | Available: Apify Store, MCP categoryApify Store is a public, browsable marketplace of 72,000+ Actors with a dedicated MCP_SERVERS category, and the catalogue is also queryable through an unauthenticated public store API. |
MCPRushSmithery
Paid MCP access
Available: Publisher-set subscriptions
Not documentedPublisher billing not documented
Details for Paid MCP access
MCPRush
Monthly plans with a call allowance and an optional rate limit, $5–$999. There is no per-call billing.
Smithery
Smithery's own pricing and docs describe only what the consuming account pays Smithery per RPC; no mechanism for a publisher to charge end users (subscription, per-call or per-event) appears in any page read.
Sell agent skills
Available: Free or one-time purchase
Not documentedSkills registry, no pricing
Details for Sell agent skills
MCPRush
Skill files are delivered to the customer; a skill never passes through the gateway.
Smithery
Smithery runs a public skills registry of GitHub-backed, installable skills with install counts and a quality score, but no page read exposes a price, purchase or payout field for skills.
Hosting choice
Available: MCPRush or your endpoint
Available: Hosted or your URL
Details for Hosting choice
MCPRush
Managed hosting builds from a public GitHub repo, npm, PyPI or a container image, within account limits. An endpoint you run stays yours.
Smithery
A release can be hosted on Smithery (JS module upload), external (your own public HTTPS endpoint, proxied by the Gateway), or a stdio MCPB bundle, and the registry exposes whether a server is Smithery-hosted.
Version control
Available: Promote or roll back
LimitedRelease history, no pinning
Details for Version control
MCPRush
A release is cut, promoted when you are ready and rolled back to a previous one; a customer can pin a version in the gateway address, and a release that widens the tool surface waits for each install to accept it.
Smithery
Smithery keeps a per-server release history that a publisher can list and inspect (status, git commit, branch, build logs, timestamps), but the pages read document no version number on the public server record, no.
Access and usage controls
Available: Gateway checks
Available: Gateway + scoped tokens
Details for Access and usage controls
MCPRush
Calls routed through MCPRush are checked for the customer’s key, the install, the plan allowance and the rate limit before they are forwarded.
Smithery
All calls route through Smithery's Connect gateway, where scoped service tokens constrain which namespaces, resources and operations a caller may reach, and each plan carries a monthly RPC allowance with custom rate limits on the enterprise tier.
Release security reports
Available: Available-source scanning
Not documentedQuality score, not security
Details for Release security reports
MCPRush
A report belongs to one release and one source. Servers on npm, PyPI or a public GitHub repo can be scanned; some releases have no completed scan.
Smithery
Smithery scans a published server, but the docs describe that scan as metadata extraction, and the per-server badge is labelled a quality score based on best practices and reliability; no security scan, audit or vulnerability result per release or source appears on any page read.
Publisher platform fee
Available: 12% of net sales
Not applicableListing free, no rev-share
Details for Publisher platform fee
MCPRush
Net sales are what is left after refunds and chargebacks. Payment processing fees are separate.
Smithery
Smithery does not sell access on a publisher's behalf, so there is no revenue share or payout to state; the platform fee for listing is explicitly zero, and the only charge on the platform is the consumer's own RPC bill.
Public catalogue
Available: Public, no sign-in
Available: Public, browsable
Details for Public catalogue
MCPRush
Listing pages, with their release and scan details, are readable without an account.
Smithery
A public, filterable catalogue of MCP servers and a separate skills registry are browsable on the site and queryable through a search API with full-text and semantic search.
Read from each platform’s own public pages on 22 September 2026. Features and terms can change.
See the findings before you connect.
Review the available security result with the source, release and scan date. Public rules help explain how the result was produced.
MCP Trust Checker is the engine behind the reports.
MCP scan report
Example
- Release
- v1.2.0
- Coverage
- available source
Capability declared read access; write capability detected
Review the capability and the access your use case needs.
A scan describes what was checked. It is not a guarantee of safety.
Your hosting. Or ours. Your product.
Keep your existing MCP endpoint or deploy a supported server on MCPRush. Customer access and applicable usage limits are handled through the gateway.
MCPRush hosting
Deploy a supported server and manage hosted releases from your publisher account.
AI client
Your customer’s tool
MCPRush gateway
Access check
Usage limits
MCP endpoint
Hosted by you or MCPRush
The call is checked and forwarded to the MCP endpoint.
Applies to gateway-connected MCP servers. Managed hosting is subject to account availability and limits.
Supported free MCP servers can also run locally. Calls outside the gateway aren’t measured by MCPRush.
Choose your product. Set your price.
Offer MCP subscriptions or sell agent skills. Manage your listing, access options and earnings from your publisher account.
- MCP serverFree access or monthly subscriptions
- Agent skillFree downloads or one-time purchases
88%
Before payment processing fees
MCPRush’s platform fee is 12% of net sales. Net sales account for refunds and chargebacks. Payment processing fees are separate.
Before you choose.
Are paid tools included in my account plan?
Paid tools have their own prices. Your account plan covers account features and usage limits. Check each listing for its access options.
Can I keep my existing MCP hosting?
Yes. Connect a supported endpoint you already host. MCPRush handles access through its gateway while you operate the server.
Does every tool have a security grade?
No. Availability depends on the source and scan status. Review the coverage and release details. Agent skills do not automatically receive an MCP server grade.
How is the platform comparison maintained?
The comparison links to public documentation and records when each source was checked. “Not documented” means the reviewed sources did not establish the feature. It does not mean the feature is unavailable.