Url vs PayMCP
Side-by-side comparison of two Model Context Protocol servers. Pick the right one for Claude Desktop, Claude Code, or Cursor.
Enables URL parsing and building from components, plus query string parsing, all without keys or online dependencies.
Comparison
| Feature | Url | PayMCP |
|---|---|---|
| Pricing | Free | Free |
| Installs | — | 2 |
| Rating | — | — |
| Verified | — | |
| Hosted | Hosted | — |
| Tools | — | — |
| Category | development | development |
| Author | pipeworx-io | blustAI |
| Repo | pipeworx-io/mcp-url | blustAI/paymcp |
When to pick Url
Enables URL parsing and building from components, plus query string parsing, all without keys or online dependencies.
When to pick PayMCP
Lightweight payments layer for MCP servers: turn tools into paid endpoints with a two-line decorator. [PyPI](https://pypi.org/project/paymcp/) · [npm](https://www.npmjs.com/package/paymcp) · [TS repo](https://github.com/blustAI/paymcp-ts)
Looking for something else? Browse all MCPs or check trending this week.