TrustFetch vs Wick
TrustFetch is an MCP server published by Vohlsyr. Marketplaces we read that list it: 1 (Official MCP Registry). Wick is an MCP server published by myleshorton. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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 |  TrustFetch |  Wick |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.1.0 Downloads/month (npm): 196 Downloads/week (npm): 45 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 | TrustFetch | Wick |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 9 |
| Forks (GitHub) (differs) | No figure on GitHub | 3 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (trustfetch.duckdns.org/mcp) | On your machine (wick-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| 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/myleshorton/wick |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 421 (3 days ago) | 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
TrustFetch
Prompt-injection scanning and safe webpage fetching for AI agents reading untrusted content.
Wick
Browser-grade web access for AI agents. Fetches any webpage, returns clean markdown.
How to run each
TrustFetch As a remote MCP server
claude mcp add --transport http trustfetch https://trustfetch.duckdns.org/mcp/Wick As a local MCP server: npm package
claude mcp add --transport stdio wick -- npx -y wick-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only TrustFetch has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: TrustFetch · What it can do: Wick · 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.