OpenZeppelin Stellar Contracts vs io.github.horizon-pulse/horizon-pulse
OpenZeppelin Stellar Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.horizon-pulse/horizon-pulse is an MCP server published by horizon-pulse. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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 |  OpenZeppelin Stellar Contracts |  io.github.horizon-pulse/horizon-pulse |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.5 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 | OpenZeppelin Stellar Contracts | io.github.horizon-pulse/horizon-pulse |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-17 |
| Where it runs (differs) | Remote server (mcp.openzeppelin.com/contracts/stellar/mcp) | Remote server (horizonpulse.dev/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/horizon-pulse/horizon-pulse |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
| Endpoint at the last check (differs) | Responded 2 days ago | Responded 8 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
OpenZeppelin Stellar Contracts
Access to OpenZeppelin Stellar Contracts.
io.github.horizon-pulse/horizon-pulse
28 agent tools via x402: crypto data, tx checks, web fetch. MCP pays Base USDC; HTTP adds 3 rails.
How to run each
OpenZeppelin Stellar Contracts As a remote MCP server
claude mcp add --transport http openzeppelin-stellar https://mcp.openzeppelin.com/contracts/stellar/mcpio.github.horizon-pulse/horizon-pulse As a remote MCP server
claude mcp add --transport http horizon-pulse https://horizonpulse.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Only OpenZeppelin Stellar Contracts has
stellar-accountstellar-fungiblestellar-governorstellar-non-fungiblestellar-stablecoinstellar-vault
Only io.github.horizon-pulse/horizon-pulse has
balancebazaar_checkchain_headdiscourse_splitextractfetchfundinggasgrocery_ingredientgrocery_normalizehttpmarket_quote
Show the remaining 16
market_searchmoney_market_ratesname_resolvepdfportfoliopulsescreenshotsearchsignalstoken_metatokenized_stocktx_guardtx_statuswatchx402_checkyield
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (io.github.horizon-pulse/horizon-pulse as of 2026-10-19). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: OpenZeppelin Stellar Contracts · What it can do: io.github.horizon-pulse/horizon-pulse · 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.