OneUptime vs io.github.VictoriaMetrics-Community/mcp-victoriametrics
OneUptime is a plugin bundle for AI coding tools published by OneUptime. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.VictoriaMetrics-Community/mcp-victoriametrics is an MCP server published by VictoriaMetrics-Community. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-11-14. 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 |  OneUptime |   io.github.VictoriaMetrics-Community/mcp-victoriametrics |
|---|---|---|
| Community marketplace using-system/otelyssey | Listed Version: 14.0.103 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.18.0 Forks (GitHub): 38 Stars (GitHub): 245 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:177f32eb9164 Forks (GitHub): 38 Stars (GitHub): 245 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 | OneUptime | io.github.VictoriaMetrics-Community/mcp-victoriametrics |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 245 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 38 (better) |
| Last release (differs) | 2026-11-11 | Not published |
| Where it runs (differs) | Remote server (oneuptime.com/mcp) | On your machine (ghcr.io/victoriametrics-community/mcp-victoriametrics:1.18.0) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares (differs) | Not published | 20 |
| Environment variables it asks for (differs) | Not published | 9, secrets among them: 1 |
| Parts of the bundle (differs) | 5 | Not a bundle |
| Licence | Apache-2.0 | Apache-2.0 |
| Repository (differs) | github.com/oneuptime/oneuptime-agent-plugin | github.com/victoriametrics-community/mcp-victoriametrics |
| Changes in the last 7 days (differs) | 8 | 0 |
| First seen (differs) | 2026-11-09 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 12 h ago | no remote endpoint we check |
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
OneUptime
Work with your OneUptime project from your coding agent: investigate and respond to incidents and alerts, check monitors and status pages, and query logs, metrics and traces.
io.github.VictoriaMetrics-Community/mcp-victoriametrics
MCP Server for VictoriaMetrics. Provides integration with VictoriaMetrics API and documentation
How to run each
OneUptime As a Claude Code plugin
/plugin marketplace add using-system/otelyssey
/plugin install oneuptime@otelysseyio.github.VictoriaMetrics-Community/mcp-victoriametrics As a local MCP server: Docker image
claude mcp add --env "VMC_API_KEY=<YOUR_VMC_API_KEY>" --env "VM_INSTANCE_BEARER_TOKEN=<YOUR_VM_INSTANCE_BEARER_TOKEN>" --env "VM_INSTANCE_ENTRYPOINT=<YOUR_VM_INSTANCE_ENTRYPOINT>" --env "VM_INSTANCE_TYPE=<YOUR_VM_INSTANCE_TYPE>" --transport stdio mcp-victoriametrics -- docker run -i --rm -e VMC_API_KEY -e VM_INSTANCE_BEARER_TOKEN -e VM_INSTANCE_ENTRYPOINT -e VM_INSTANCE_TYPE ghcr.io/victoriametrics-community/mcp-victoriametrics:1.18.0Requires: VMC_API_KEY (secret), VM_INSTANCE_BEARER_TOKEN (secret), VM_INSTANCE_ENTRYPOINT, VM_INSTANCE_TYPE
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only OneUptime has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of OneUptime publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of OneUptime publish no settings it asks for, so we do not compare settings.
What it can do: OneUptime · What it can do: io.github.VictoriaMetrics-Community/mcp-victoriametrics · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.