OneTool MCP vs saagarpatel.dev Portfolio
OneTool MCP is an MCP server published by beycom. Marketplaces we read that list it: 1 (Official MCP Registry). saagarpatel.dev Portfolio is an MCP server published by saagpatel. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 |  OneTool MCP |  saagarpatel.dev Portfolio |
|---|---|---|
| Official MCP Registry | Listed Version: 2.2.2 Forks (GitHub): 7 Stars (GitHub): 24 Not marked · First seen |
Listed Version: 0.1.0 Downloads/month (npm): 128 Downloads/week (npm): 10 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 | OneTool MCP | saagarpatel.dev Portfolio |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 24 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 7 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Not stated | Remote server (mcp.saagarpatel.dev/mcp) |
| Transport (differs) | Not stated | 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/beycom/onetool-mcp | github.com/saagpatel/portfolio-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 403 (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
OneTool MCP
One MCP for devs incl Brave,Google,Tavily,Context7,AWS,Excalidraw,DB,GitHub,DevTools,Playwright
saagarpatel.dev Portfolio
Agent-native MCP server over the public saagarpatel.dev corpus. Read-only, stateless.
How to run each
OneTool MCP
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
saagarpatel.dev Portfolio As a remote MCP server
claude mcp add --transport http portfolio-mcp https://mcp.saagarpatel.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only saagarpatel.dev Portfolio 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: OneTool MCP · What it can do: saagarpatel.dev Portfolio · 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.