Ext Ops Panel
Open dashboard
Comparison

com.argosvix/server vs io.github.agentmark-ai/mcp-server

com.argosvix/server is an MCP server published by argosvix.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.agentmark-ai/mcp-server is an MCP server published by agentmark-ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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

Where each is published
Marketplacecom.argosvix/serverio.github.agentmark-ai/mcp-server
Official MCP Registry Listed
Version: 1.1.2
Downloads/month (npm): 554
Downloads/week (npm): 132
Not marked · First seen
Listed
Version: 0.4.2
Downloads/month (npm): 220
Downloads/week (npm): 34
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

com.argosvix/server vs io.github.agentmark-ai/mcp-server
Factcom.argosvix/serverio.github.agentmark-ai/mcp-server
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@argosvix/mcp-server)On your machine (@agentmark-ai/mcp-server)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/agentmark-ai/agentmark
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

com.argosvix/server

In its own words, on Official MCP Registry:

Observability MCP server: query LLM cost/errors/latency & operate alerts/evals from Claude/Cursor

io.github.agentmark-ai/mcp-server

In its own words, on Official MCP Registry:

Inspect AgentMark traces and drive AgentMark Cloud: apps, experiments, metrics, deployments.

How to run each

com.argosvix/server As a local MCP server: npm package

Claude Code
claude mcp add --env "ARGOSVIX_API_KEY=<YOUR_ARGOSVIX_API_KEY>" --transport stdio com-argosvix-server -- npx -y @argosvix/mcp-server

Requires: ARGOSVIX_API_KEY (secret)

io.github.agentmark-ai/mcp-server As a local MCP server: npm package

Claude Code
claude mcp add --env "AGENTMARK_API_KEY=<YOUR_AGENTMARK_API_KEY>" --transport stdio io-github-agentmark-ai-mcp-server -- npx -y @agentmark-ai/mcp-server

Requires: AGENTMARK_API_KEY (secret)

Commands 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

Only com.argosvix/server asks for

  • ARGOSVIX_API_KEY (secret)

Only io.github.agentmark-ai/mcp-server asks for

  • AGENTMARK_API_KEY (secret)
  • AGENTMARK_API_URL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: com.argosvix/server · What it can do: io.github.agentmark-ai/mcp-server · 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.

Where the data comes from: how the catalog is built