SiteCheck Agent Intel & Dev vs CallRail MCP
SiteCheck Agent Intel & Dev is an MCP server published by bck-stack. Marketplaces we read that list it: 1 (Official MCP Registry). CallRail MCP is an MCP server published by pghdma. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-25. 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 |  CallRail MCP | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 1.3.1 Downloads/month (PyPI): 582 Downloads/week (PyPI): 168 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 1.3.1 Downloads/month (PyPI): 582 Downloads/week (PyPI): 168 Forks (GitHub): 0 Stars (GitHub): 2 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 | SiteCheck Agent Intel & Dev | CallRail MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 2 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.fadeandco.workers.dev/mcp) | On your machine (callrail-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | Not stated | github.com/pghdma/callrail-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-23 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | no remote endpoint we check |
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
SiteCheck Agent Intel & Dev
135 pay-per-call agent tools: agent intelligence, token risk, developer and AI data tools. x402
CallRail MCP
CallRail REST API v3: 57 tools for calls, leads, trackers, tags, users, and agency reporting.
How to run each
SiteCheck Agent Intel & Dev
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
CallRail MCP As a local MCP server: PyPI package
claude mcp add --env "CALLRAIL_API_KEY=<YOUR_CALLRAIL_API_KEY>" --transport stdio callrail-mcp -- uvx callrail-mcpRequires: CALLRAIL_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of SiteCheck Agent Intel & Dev publish no settings it asks for, so we do not compare settings.
What it can do: SiteCheck Agent Intel & Dev · What it can do: CallRail MCP · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.