io.github.VictoriaMetrics-Community/mcp-victoriametrics vs network.clockchain/time
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). network.clockchain/time is an MCP server published by clockchain.network. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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.VictoriaMetrics-Community/mcp-victoriametrics |  network.clockchain/time |
|---|---|---|
| Official MCP Registry | Listed Version: 1.18.0 Forks (GitHub): 37 Stars (GitHub): 242 Not marked · First seen |
Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:177f32eb9164 Forks (GitHub): 37 Stars (GitHub): 242 Not marked · First seen |
Not listed |
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.VictoriaMetrics-Community/mcp-victoriametrics | network.clockchain/time |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 242 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 37 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (ghcr.io/victoriametrics-community/mcp-victoriametrics:1.18.0) | Remote server (clockchain-time-rp6evdzqkq-uc.a.run.app/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 20 | Not published |
| Environment variables it asks for (differs) | 9, secrets among them: 1 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/victoriametrics-community/mcp-victoriametrics | github.com/thetangstr/clockchain-developer-tools |
| 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 | Status out of date: last check 2 days ago returned HTTP 500 |
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.VictoriaMetrics-Community/mcp-victoriametrics
MCP Server for VictoriaMetrics. Provides integration with VictoriaMetrics API and documentation
network.clockchain/time
Clockchain®: neutral verified network time for AI agents (get_time). Testnet.
How to run each
io.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
network.clockchain/time As a remote MCP server
claude mcp add --transport http time https://clockchain-time-rp6evdzqkq-uc.a.run.app/mcp --header "x-api-key: <YOUR_X_API_KEY>"Requires: x-api-key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only network.clockchain/time has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of network.clockchain/time publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of network.clockchain/time publish no settings it asks for, so we do not compare settings.
What it can do: io.github.VictoriaMetrics-Community/mcp-victoriametrics · What it can do: network.clockchain/time · Compare two other plugins
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.