com.callingly/callingly vs SiteCheck
com.callingly/callingly is an MCP server published by callingly.com. Marketplaces we read that list it: 1 (Official MCP Registry). SiteCheck is an MCP server published by bck-stack. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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 |  SiteCheck | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 1.4.0 Forks (GitHub): 0 Stars (GitHub): 1 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 | com.callingly/callingly | SiteCheck |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 1 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | Remote server (api.callingly.com/mcp) | Remote server (api.sitecheck-api.workers.dev/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/bck-stack/sitecheck-x402 |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | 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
com.callingly/callingly
Lets AI agents get leads on the phone: call, send SMS, and schedule callbacks for sales teams.
SiteCheck
86 pay-per-call agent tools: web, SEO, OCR, SEC, KYB, chain reads, DeFi, weather, dev data. Via x402
How to run each
com.callingly/callingly As a remote MCP server
claude mcp add --transport http callingly https://api.callingly.com/mcpSiteCheck As a remote MCP server
claude mcp add --transport http sitecheck https://api.sitecheck-api.workers.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only SiteCheck has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of com.callingly/callingly nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: com.callingly/callingly · What it can do: SiteCheck · Compare two other plugins
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.