MCP Registry Monitor vs Parseable
MCP Registry Monitor lists no tools and Parseable lists no tools and runs locally.
| Fact | MCP Registry Monitorio.github.nirholas/mcp-notify | Parseableio.github.parseablehq/parseable-mcp-server |
|---|---|---|
| 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 | Not known | Local |
| Needs first | – | Node.js |
| Licence | Not stated | APACHE-2.0 |
| Latest version | 1.0.0 | 0.2.16 |
| Known advisories | 0 | 0 |
| Works in | No install config | 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 |
| Downloads last week | Not known | Not known |
| Install | Install MCP Registry Monitor | Install Parseable |
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 Registry Monitor with othersCompare Parseable with others