Argosvix

com.argosvixPublished by argosvix.comv1.1.2Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlySecurity & MonitoringData & Analytics

Overview

AI-generated overview

Argosvix is an observability MCP server that lets an assistant query LLM cost, error, and latency data and operate alerts and evals.

What you can do
Argosvix exposes an observability backend to an assistant over stdio. According to the registry description, it can query LLM cost, error, and latency data and operate alerts and evals. Two public data tools, get_synth_daily and get_daily_readthrough, are available without an API key, while account tools require one.
When to use it
Useful when you want an assistant to inspect LLM usage, spend, error rates, or latency, or to work with alerts and evaluations from a chat client such as Claude or Cursor. It is aimed at teams already using the Argosvix observability platform.
Requirements
Runs as a local stdio process on the user's machine, installed from the npm package @argosvix/mcp-server, so Node.js is needed. An Argosvix API key (ARGOSVIX_API_KEY, prefixed argk_) issued from the dashboard is required for account tools; without it only the two public data tools work. Desktop only.
Before you install
The server asks for an API key, ARGOSVIX_API_KEY, which grants access to account-level observability data; treat it as a secret and avoid exposing it in logs or shared configuration. Account tools may change alerts or evaluations, so review what an assistant is allowed to modify. The server sends queries to the Argosvix service.

Installation

In SourceWeft

  1. Open Argosvix in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.