HTTP vs Chainweb API
HTTP is an MCP server published by Abhishekkumar2021. Marketplaces we read that list it: 1 (Official MCP Registry). Chainweb API is an MCP server published by Pact-Community-Organization. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  HTTP |  Chainweb API |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Downloads/month (npm): 184 Downloads/week (npm): 31 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.2.3 Downloads/month (npm): 215 Downloads/week (npm): 45 Forks (GitHub): 3 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 | HTTP | Chainweb API |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 0 (worse) | 3 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@abhishekmcp/http) | On your machine (@pact-community/mcp-chainweb) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 0 | 5, secrets among them: 0 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/abhishekkumar2021/mcp-suite | github.com/pact-community-organization/pact-mcp |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
HTTP
HTTP/REST client with saved collections, env secrets, and SSRF-safe host allowlisting.
Chainweb API
Chainweb HTTP API: local sim, pre-signed send, poll, table reads, SPV proofs, module deploys.
How to run each
HTTP As a local MCP server: npm package
claude mcp add --env "HTTP_ALLOW_HOSTS=<YOUR_HTTP_ALLOW_HOSTS>" --transport stdio http -- npx -y @abhishekmcp/httpRequires: HTTP_ALLOW_HOSTS
Chainweb API As a local MCP server: npm package
claude mcp add --env "PACT_COMMUNITY_CHAINWEB_MODE=<YOUR_PACT_COMMUNITY_CHAINWEB_MODE>" --env "PACT_COMMUNITY_WORKSPACE_ROOT=<YOUR_PACT_COMMUNITY_WORKSPACE_ROOT>" --transport stdio chainweb -- npx -y @pact-community/mcp-chainwebRequires: PACT_COMMUNITY_CHAINWEB_MODE, PACT_COMMUNITY_WORKSPACE_ROOT
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
Only HTTP asks for
HTTP_ALLOW_HOSTSHTTP_WRITABLE
Only Chainweb API asks for
PACT_COMMUNITY_CHAINWEB_BASE_URLPACT_COMMUNITY_CHAINWEB_MODEPACT_COMMUNITY_CHAINWEB_NETWORK_IDPACT_COMMUNITY_CHAINWEB_PROFILEPACT_COMMUNITY_WORKSPACE_ROOT
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: HTTP · What it can do: Chainweb API · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.