io.github.KryptosAI/mcp-observatory vs io.github.stasxr/palanit-core
io.github.KryptosAI/mcp-observatory is an MCP server published by KryptosAI. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.stasxr/palanit-core is an MCP server published by stasxr. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |  io.github.KryptosAI/mcp-observatory |  io.github.stasxr/palanit-core |
|---|---|---|
| Official MCP Registry | Listed Version: 1.36.1 Downloads/month (npm): 3 473 Downloads/week (npm): 630 Forks (GitHub): 15 Stars (GitHub): 135 Not marked · First seen |
Listed Version: 0.1.3 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 | io.github.KryptosAI/mcp-observatory | io.github.stasxr/palanit-core |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 135 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 15 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-21 |
| Where it runs (differs) | On your machine (@kryptosai/mcp-observatory) | On your machine (palanit-core) |
| Transport | stdio | stdio |
| 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/kryptosai/mcp-observatory | github.com/stasxr/palanit-core |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-11 | 2026-10-17 |
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
io.github.KryptosAI/mcp-observatory
MCP security scanner. CI-native testing, attack simulation, health scoring, and SARIF.
io.github.stasxr/palanit-core
Scan MCP servers and agent tool manifests for poisoning, exfiltration, secrets and supply-chain risk
How to run each
io.github.KryptosAI/mcp-observatory As a local MCP server: npm package
claude mcp add --transport stdio mcp-observatory -- npx -y @kryptosai/mcp-observatoryio.github.stasxr/palanit-core As a local MCP server: PyPI package
claude mcp add --transport stdio palanit-core -- uvx palanit-coreCommands built only from what the marketplaces declare; the full set for every client is on each card.
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: io.github.KryptosAI/mcp-observatory · What it can do: io.github.stasxr/palanit-core · 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.