Upwork vs io.github.RudrenduPaul/freelancer-payment-protection
Upwork is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). io.github.RudrenduPaul/freelancer-payment-protection is an MCP server published by RudrenduPaul. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.RudrenduPaul/freelancer-payment-protection | |
|---|---|---|
| Cursor: cursor/plugins | Listed Version: 1.0.0 Forks (GitHub): 1 197 Stars (GitHub): 12 306 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.6 Downloads/month (PyPI): 122 Downloads/week (PyPI): 42 Forks (GitHub): 1 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Upwork | io.github.RudrenduPaul/freelancer-payment-protection |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 12 306 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 1 197 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.upwork.com/mcp) | On your machine (freelancer-payment-protection-cli) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/cursor/plugins | github.com/rudrendupaul/freelancer-payment-protection |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 days ago, requires a key | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Upwork
Search talent, post jobs, and manage contracts.
io.github.RudrenduPaul/freelancer-payment-protection
Wraps the fpp CLI as a single generic MCP tool for freelancer client payment-risk checks.
How to run each
Upwork
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.RudrenduPaul/freelancer-payment-protection As a local MCP server: PyPI package
claude mcp add --transport stdio freelancer-payment-protection -- uvx --from freelancer-payment-protection-cli freelancer-payment-protection-cli fpp-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Upwork has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Upwork · What it can do: io.github.RudrenduPaul/freelancer-payment-protection · Compare two other plugins
Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.