mcp-server-fetch vs MCP Registry Monitor
mcp-server-fetch lists no tools and runs locally and MCP Registry Monitor lists no tools.
| Fact | mcp-server-fetchio.github.modelcontextprotocol/servers-fetch | MCP Registry Monitorio.github.nirholas/mcp-notify |
|---|---|---|
| Score | Not checked yet | Not checked yet |
| Status | Not checked yet | Not checked yet |
| Tools | 0 | 0 |
| Can write data | No tools listed | No tools listed |
| Runs | Local | Not known |
| Needs first | uv | – |
| Licence | MIT | Not stated |
| Latest version | 2026.10.19 | 1.0.0 |
| Known advisories | 0 | 0 |
| Works in | Claude Desktop, Claude Code, Cursor, VS Code, Devin Desktop, Zed, Cline, Continue, Goose, LM Studio, Gemini CLI, Codex, mcp-client-cli, oterm, TUUI, BoltAI, Agenvoy, Amp, AnythingLLM, Augment Code, Bob Shell, ECA, Kiro, Kiro CLI | No install config |
| Downloads last week | Not known | Not known |
| Install | Install mcp-server-fetch | Install MCP Registry Monitor |
Scores and status come with our own checks, which have not run on these servers yet. The rest is from the publishers' registry entries, package registries and advisory databases.
Compare mcp-server-fetch with othersCompare MCP Registry Monitor with others