Spoor

io.github.asinha07/spoorv0.2.1Monitoring & Logs

What changed across metrics, logs and traces, and where it started (VictoriaMetrics stack).

The current version, v0.2.1, was published to the official MCP registry on 2026-10-16. It is distributed as the Docker image ghcr.io/asinha07/spoor:0.2.1, filed under Monitoring & Logs by this index, and declares 6 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using Spoor in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire

Auditable install path →Watch it hold a drift →

Trust verdict · v1 advisory · method

REVIEWstatus: PARTIALfresh until 2026-11-15 22:09 UTC

screened 2026-10-16tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidence“Tool monitors changes across metrics, logs, and traces.”via static_description

Limits of this verdict

- Semantic screen only - the deterministic conformance probe has not run on this server
- Confidence is reported but not yet calibrated (v1)
- Screen reads the tool description, not the live behavior
- advisory
- registry description only no input schema
- screen model 8b

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Test a description on the public screen → It is a separate check from the verdict above, so the two can differ.

That verdict was true at screening time (snapshot 2026-10-19).

Contracts can change after screening, with no version bump. The gate pins Spoor’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Cite this record

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

Markdown

[Independent trust record for Spoor](https://mcpindex.ai/server/io-github-asinha07-spoor) - screening verdict, registry provenance, and contract drift monitoring.

HTML

<a href="https://mcpindex.ai/server/io-github-asinha07-spoor">Independent trust record for Spoor</a> - screening verdict, registry provenance, and contract drift monitoring.

Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown

[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-asinha07-spoor)](https://mcpindex.ai/server/io-github-asinha07-spoor)

HTML

<a href="https://mcpindex.ai/server/io-github-asinha07-spoor"><img src="https://mcpindex.ai/api/v1/badge/io-github-asinha07-spoor" alt="mcpindex verdict" height="20" /></a>

Environment variables

SPOOR_METRICS_URL

required

VictoriaMetrics URL as seen from the container, e.g. http://host.docker.internal:8428

SPOOR_LOGS_URL

required

VictoriaLogs URL as seen from the container, e.g. http://host.docker.internal:9428

SPOOR_TRACES_URL

required

VictoriaTraces URL as seen from the container, e.g. http://host.docker.internal:10428

SPOOR_METRICS_TOKEN

secret

Bearer token for VictoriaMetrics, if it requires one

SPOOR_LOGS_TOKEN

secret

Bearer token for VictoriaLogs, if it requires one

SPOOR_TRACES_TOKEN

secret

Bearer token for VictoriaTraces, if it requires one

MCP quality score · maturity, not trust · methodology

freshness

completeness

installability

documentation

stability

Alternatives in Monitoring & Logs

Labby

ai.dinglebear/labby

Rust MCP gateway with Code Mode, authentication, setup, logs, CLI, HTTP API, and operator web UI.

FrontierStack by Enfour, Inc.

app.frontierstack/frontierstack

Enfour, Inc. FrontierStack (www.frontierstack.app): Mac and server health, logs, restarts.

Git Insights

io.github.basitalisandhu/mcp-git-insights

Read-only git statistics for a local repository: log, blame ownership, churn, authors, large files.

Install this server

Claude Desktop (Docker)

{
  "mcpServers": {
    "spoor": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "--",
        "ghcr.io/asinha07/spoor:0.2.1"
      ],
      "env": {
        "SPOOR_METRICS_URL": "<spoor_metrics_url>",
        "SPOOR_LOGS_URL": "<spoor_logs_url>",
        "SPOOR_TRACES_URL": "<spoor_traces_url>",
        "SPOOR_METRICS_TOKEN": "<your-spoor_metrics_token>",
        "SPOOR_LOGS_TOKEN": "<your-spoor_logs_token>",
        "SPOOR_TRACES_TOKEN": "<your-spoor_traces_token>"
      }
    }
  }
}

Verdict API

curl -s mcpindex.ai/api/v1/trust/server/io-github-asinha07-spoor

Free-tier verdict as JSON: decision + dimensions + severity. Call it from your agent before it invokes a tool it just discovered.

Details

version: v0.2.1
category: Monitoring & Logs
verdict expires: 2026-11-15
quality: 90 / 100
operator: asinha07

Listing

Listed from the official MCP registry. Unclaimed by its maintainer. Maintainer? Email us →

Provenance

Each verdict is bound to a hash of the exact description it judged, so a re-crawl that changes the text produces a new record rather than silently inheriting this one. Verdict history is hash-chained and anchored to Bitcoin via OpenTimestamps (latest confirmed at block 972,115). Verify it yourself.

Links

Repository →Website →