HighLevel vs Execute b2b-contract-renewal-mcp
HighLevel is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). Execute b2b-contract-renewal-mcp is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 |  HighLevel | |
|---|---|---|
| Cursor: cursor/plugins | Listed Version: 1.1.0 Forks (GitHub): 1 268 Stars (GitHub): 12 913 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.0.0 No figure published 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 | HighLevel | Execute b2b-contract-renewal-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 12 913 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 268 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (services.leadconnectorhq.com/mcp/cursor/v2) | Remote server (api.m2mcent.com/b2b-contract-renewal-mcp/sse) |
| Transport (differs) | Streamable HTTP | SSE |
| 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 | Not stated |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | Answered with HTTP 402 (4 days ago) |
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
HighLevel
Work with contacts, conversations, opportunities, calendars, and payments.
Execute b2b-contract-renewal-mcp
Premium agentic endpoint for b2b-contract-renewal-mcp.
How to run each
HighLevel
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Execute b2b-contract-renewal-mcp As a remote MCP server
claude mcp add --transport sse b2b-contract-renewal-mcp https://api.m2mcent.com/b2b-contract-renewal-mcp/sse --header "Payment-Signature: <YOUR_PAYMENT_SIGNATURE>"Requires: Payment-Signature header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Execute b2b-contract-renewal-mcp 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: HighLevel · What it can do: Execute b2b-contract-renewal-mcp · 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.