Offline Protocol (hosted) vs Toolforest
Offline Protocol (hosted) is an MCP server published by offlineprotocol.com. Marketplaces we read that list it: 1 (Official MCP Registry). Toolforest is an MCP server published by toolforest.io. 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 |   Offline Protocol (hosted) |  Toolforest |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.7 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.0 No figure published 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 | Offline Protocol (hosted) | Toolforest |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.offlineprotocol.com/mcp) | Remote server (mcp.toolforest.io/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) | github.com/offline-protocol/offline-protocol-agent-plugins | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 1 h ago | Responded 5 days ago, requires a key |
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
Offline Protocol (hosted)
Offline Protocol packages, workflows and integration guides over HTTPS. Read-only.
Toolforest
Hosted MCP server with managed OAuth for 15+ toolkits: Google Workspace, Fitbit, Oura, Kalshi, etc.
How to run each
Offline Protocol (hosted) As a remote MCP server
claude mcp add --transport http hosted https://mcp.offlineprotocol.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>" --header "x-app-id: <YOUR_X_APP_ID>"Requires: Authorization header, x-app-id header
Toolforest As a remote MCP server
claude mcp add --transport http toolforest https://mcp.toolforest.io/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
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: Offline Protocol (hosted) · What it can do: Toolforest · 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.