OSP Marketing Tools vs Parsley - Buyer Intent Signals
OSP Marketing Tools is an MCP server published by open-strategy-partners. Marketplaces we read that list it: 1 (Docker MCP Catalog). Parsley - Buyer Intent Signals is an MCP server published by peterjduffy. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:34b72f4cc3d2 Forks (GitHub): 43 Pulls (Docker Hub): 44 816 Stars (Docker Hub): 2 Stars (GitHub): 274 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.2 Downloads/month (npm): 131 Downloads/week (npm): 26 Forks (GitHub): 0 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 | OSP Marketing Tools | Parsley - Buyer Intent Signals |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 274 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 44 816 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 43 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/osp_marketing_tools) | Remote server (www.parsley.id/api/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence (differs) | CC-BY-SA-4.0 | Not stated |
| Repository (differs) | github.com/open-strategy-partners/osp_marketing_tools | github.com/peterjduffy/parsley-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 503 (2 h 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
OSP Marketing Tools
A Model Context Protocol (MCP) server that empowers LLMs to use some of Open Srategy Partners' core writing and product marketing techniques.
Parsley - Buyer Intent Signals
Query buyer intent signals, MEDDIC qualifications, and lead scores from Parsley.
How to run each
OSP Marketing Tools As a local MCP server: Docker image
claude mcp add --transport stdio osp-marketing-tools -- docker run -i --rm mcp/osp_marketing_tools
Parsley - Buyer Intent Signals As a remote MCP server
claude mcp add --transport http parsley-mcp https://www.parsley.id/api/mcp --header "X-API-Key: <YOUR_X_API_KEY>"
Requires: PARSLEY_API_KEY (secret), X-API-Key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Parsley - Buyer Intent Signals has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Parsley - Buyer Intent Signals publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of OSP Marketing Tools publish no settings it asks for, so we do not compare settings.
What it can do: OSP Marketing Tools · What it can do: Parsley - Buyer Intent Signals · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.