# Spoor (oci · ghcr.io/asinha07/spoor)

What changed across metrics, logs and traces, and where it started (Grafana, Victoria, New Relic).

- Trust score: 45/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- oci · `ghcr.io/asinha07/spoor`: 45/100 (this document), [markdown](https://verifymcp.io/servers/asinha07-spoor/ghcr-io-asinha07-spoor.md), [page](https://verifymcp.io/servers/asinha07-spoor/ghcr-io-asinha07-spoor)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/asinha07/spoor`
- Version: `0.3.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.
- **Provenance & Transparency**: 35/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 12 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 965 tokens (~241/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Spoor MCP server?

Spoor runs locally as a container image, launched with docker run --rm -i -e SPOOR_METRICS_TYPE -e SPOOR_LOGS_TYPE -e SPOOR_TRACES_TYPE -e SPOOR_METRICS_URL -e SPOOR_LOGS_URL -e SPOOR_TRACES_URL -e SPOOR_METRICS_TOKEN -e SPOOR_LOGS_TOKEN -e SPOOR_TRACES_TOKEN -e NEW_RELIC_ACCOUNT_ID -e NEW_RELIC_API_KEY ghcr.io/asinha07/spoor:0.3.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add asinha07-spoor -- docker run --rm -i -e SPOOR_METRICS_TYPE -e SPOOR_LOGS_TYPE -e SPOOR_TRACES_TYPE -e SPOOR_METRICS_URL -e SPOOR_LOGS_URL -e SPOOR_TRACES_URL -e SPOOR_METRICS_TOKEN -e SPOOR_LOGS_TOKEN -e SPOOR_TRACES_TOKEN -e NEW_RELIC_ACCOUNT_ID -e NEW_RELIC_API_KEY ghcr.io/asinha07/spoor:0.3.1
```

This image reads SPOOR_METRICS_TYPE, SPOOR_LOGS_TYPE, SPOOR_TRACES_TYPE, SPOOR_METRICS_URL, SPOOR_LOGS_URL, SPOOR_TRACES_URL, SPOOR_METRICS_TOKEN, SPOOR_LOGS_TOKEN, SPOOR_TRACES_TOKEN, NEW_RELIC_ACCOUNT_ID and NEW_RELIC_API_KEY. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Cursor

```json
{
  "mcpServers": {
    "asinha07-spoor": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "SPOOR_METRICS_TYPE",
        "-e",
        "SPOOR_LOGS_TYPE",
        "-e",
        "SPOOR_TRACES_TYPE",
        "-e",
        "SPOOR_METRICS_URL",
        "-e",
        "SPOOR_LOGS_URL",
        "-e",
        "SPOOR_TRACES_URL",
        "-e",
        "SPOOR_METRICS_TOKEN",
        "-e",
        "SPOOR_LOGS_TOKEN",
        "-e",
        "SPOOR_TRACES_TOKEN",
        "-e",
        "NEW_RELIC_ACCOUNT_ID",
        "-e",
        "NEW_RELIC_API_KEY",
        "ghcr.io/asinha07/spoor:0.3.1"
      ]
    }
  }
}
```

This image reads SPOOR_METRICS_TYPE, SPOOR_LOGS_TYPE, SPOOR_TRACES_TYPE, SPOOR_METRICS_URL, SPOOR_LOGS_URL, SPOOR_TRACES_URL, SPOOR_METRICS_TOKEN, SPOOR_LOGS_TOKEN, SPOOR_TRACES_TOKEN, NEW_RELIC_ACCOUNT_ID and NEW_RELIC_API_KEY. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### VS Code

```json
{
  "servers": {
    "asinha07-spoor": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "SPOOR_METRICS_TYPE",
        "-e",
        "SPOOR_LOGS_TYPE",
        "-e",
        "SPOOR_TRACES_TYPE",
        "-e",
        "SPOOR_METRICS_URL",
        "-e",
        "SPOOR_LOGS_URL",
        "-e",
        "SPOOR_TRACES_URL",
        "-e",
        "SPOOR_METRICS_TOKEN",
        "-e",
        "SPOOR_LOGS_TOKEN",
        "-e",
        "SPOOR_TRACES_TOKEN",
        "-e",
        "NEW_RELIC_ACCOUNT_ID",
        "-e",
        "NEW_RELIC_API_KEY",
        "ghcr.io/asinha07/spoor:0.3.1"
      ]
    }
  }
}
```

This image reads SPOOR_METRICS_TYPE, SPOOR_LOGS_TYPE, SPOOR_TRACES_TYPE, SPOOR_METRICS_URL, SPOOR_LOGS_URL, SPOOR_TRACES_URL, SPOOR_METRICS_TOKEN, SPOOR_LOGS_TOKEN, SPOOR_TRACES_TOKEN, NEW_RELIC_ACCOUNT_ID and NEW_RELIC_API_KEY. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Codex

```bash
codex mcp add asinha07-spoor -- docker run --rm -i -e SPOOR_METRICS_TYPE -e SPOOR_LOGS_TYPE -e SPOOR_TRACES_TYPE -e SPOOR_METRICS_URL -e SPOOR_LOGS_URL -e SPOOR_TRACES_URL -e SPOOR_METRICS_TOKEN -e SPOOR_LOGS_TOKEN -e SPOOR_TRACES_TOKEN -e NEW_RELIC_ACCOUNT_ID -e NEW_RELIC_API_KEY ghcr.io/asinha07/spoor:0.3.1
```

This image reads SPOOR_METRICS_TYPE, SPOOR_LOGS_TYPE, SPOOR_TRACES_TYPE, SPOOR_METRICS_URL, SPOOR_LOGS_URL, SPOOR_TRACES_URL, SPOOR_METRICS_TOKEN, SPOOR_LOGS_TOKEN, SPOOR_TRACES_TOKEN, NEW_RELIC_ACCOUNT_ID and NEW_RELIC_API_KEY. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "asinha07-spoor": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "SPOOR_METRICS_TYPE",
        "-e",
        "SPOOR_LOGS_TYPE",
        "-e",
        "SPOOR_TRACES_TYPE",
        "-e",
        "SPOOR_METRICS_URL",
        "-e",
        "SPOOR_LOGS_URL",
        "-e",
        "SPOOR_TRACES_URL",
        "-e",
        "SPOOR_METRICS_TOKEN",
        "-e",
        "SPOOR_LOGS_TOKEN",
        "-e",
        "SPOOR_TRACES_TOKEN",
        "-e",
        "NEW_RELIC_ACCOUNT_ID",
        "-e",
        "NEW_RELIC_API_KEY",
        "ghcr.io/asinha07/spoor:0.3.1"
      ],
      "enabled": true
    }
  }
}
```

This image reads SPOOR_METRICS_TYPE, SPOOR_LOGS_TYPE, SPOOR_TRACES_TYPE, SPOOR_METRICS_URL, SPOOR_LOGS_URL, SPOOR_TRACES_URL, SPOOR_METRICS_TOKEN, SPOOR_LOGS_TOKEN, SPOOR_TRACES_TOKEN, NEW_RELIC_ACCOUNT_ID and NEW_RELIC_API_KEY. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Hermes

```yaml
mcp_servers:
  asinha07-spoor:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "SPOOR_METRICS_TYPE", "-e", "SPOOR_LOGS_TYPE", "-e", "SPOOR_TRACES_TYPE", "-e", "SPOOR_METRICS_URL", "-e", "SPOOR_LOGS_URL", "-e", "SPOOR_TRACES_URL", "-e", "SPOOR_METRICS_TOKEN", "-e", "SPOOR_LOGS_TOKEN", "-e", "SPOOR_TRACES_TOKEN", "-e", "NEW_RELIC_ACCOUNT_ID", "-e", "NEW_RELIC_API_KEY", "ghcr.io/asinha07/spoor:0.3.1"]
```

This image reads SPOOR_METRICS_TYPE, SPOOR_LOGS_TYPE, SPOOR_TRACES_TYPE, SPOOR_METRICS_URL, SPOOR_LOGS_URL, SPOOR_TRACES_URL, SPOOR_METRICS_TOKEN, SPOOR_LOGS_TOKEN, SPOOR_TRACES_TOKEN, NEW_RELIC_ACCOUNT_ID and NEW_RELIC_API_KEY. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Netclaw

```json
{
  "McpServers": {
    "asinha07-spoor": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "SPOOR_METRICS_TYPE",
        "-e",
        "SPOOR_LOGS_TYPE",
        "-e",
        "SPOOR_TRACES_TYPE",
        "-e",
        "SPOOR_METRICS_URL",
        "-e",
        "SPOOR_LOGS_URL",
        "-e",
        "SPOOR_TRACES_URL",
        "-e",
        "SPOOR_METRICS_TOKEN",
        "-e",
        "SPOOR_LOGS_TOKEN",
        "-e",
        "SPOOR_TRACES_TOKEN",
        "-e",
        "NEW_RELIC_ACCOUNT_ID",
        "-e",
        "NEW_RELIC_API_KEY",
        "ghcr.io/asinha07/spoor:0.3.1"
      ]
    }
  }
}
```

This image reads SPOOR_METRICS_TYPE, SPOOR_LOGS_TYPE, SPOOR_TRACES_TYPE, SPOOR_METRICS_URL, SPOOR_LOGS_URL, SPOOR_TRACES_URL, SPOOR_METRICS_TOKEN, SPOOR_LOGS_TOKEN, SPOOR_TRACES_TOKEN, NEW_RELIC_ACCOUNT_ID and NEW_RELIC_API_KEY. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Other

```json
{
  "mcpServers": {
    "asinha07-spoor": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "SPOOR_METRICS_TYPE",
        "-e",
        "SPOOR_LOGS_TYPE",
        "-e",
        "SPOOR_TRACES_TYPE",
        "-e",
        "SPOOR_METRICS_URL",
        "-e",
        "SPOOR_LOGS_URL",
        "-e",
        "SPOOR_TRACES_URL",
        "-e",
        "SPOOR_METRICS_TOKEN",
        "-e",
        "SPOOR_LOGS_TOKEN",
        "-e",
        "SPOOR_TRACES_TOKEN",
        "-e",
        "NEW_RELIC_ACCOUNT_ID",
        "-e",
        "NEW_RELIC_API_KEY",
        "ghcr.io/asinha07/spoor:0.3.1"
      ]
    }
  }
}
```

This image reads SPOOR_METRICS_TYPE, SPOOR_LOGS_TYPE, SPOOR_TRACES_TYPE, SPOOR_METRICS_URL, SPOOR_LOGS_URL, SPOOR_TRACES_URL, SPOOR_METRICS_TOKEN, SPOOR_LOGS_TOKEN, SPOOR_TRACES_TOKEN, NEW_RELIC_ACCOUNT_ID and NEW_RELIC_API_KEY. Set them in your client's env block for this server; docker run -e passes each one through to the container.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 45, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 44, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 43, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 42, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 41, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 40, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 39, 0)

- [functional] Package version: 0.2.1 → 0.3.1

### 2026-10-22 (score 39, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `list_services` (~64 tokens)

List services

Services seen in the window and which signals (metrics, logs, traces) have data for each.

Input parameters:

- `since` (string): Window start: RFC 3339 time or a duration ago. Default 30m.
- `until` (string): Window end. Default now.

### `new_errors` (~202 tokens)

New errors

Error logs compared with a baseline: errors that are new or spiking (messages that differ only by IDs count as one error), services whose error volume rose beyond their traffic, each with counts, first-seen time and one redacted example line, plus services whose errors are steady.

Input parameters:

- `baseline` (string): What to compare against: previous (the windows just before; default), 1d or 7d (same window that many days earlier).
- `budget_tokens` (integer): Upper bound on the response size in tokens, 200 to 4000. Default 800.
- `service` (string): Service name. Omit to scan every service seen in the window.
- `since` (string): Window start: RFC 3339 time or a duration ago such as 30m or 2h. Default 30m.
- `until` (string): Window end: RFC 3339 time or a duration ago. Default now.

### `trace_diff` (~190 tokens)

Trace diff

Span names that got slower or started failing compared with a baseline: p95 and error rate before/after, each span's share of the added latency, and an example trace ID.

Input parameters:

- `baseline` (string): What to compare against: previous (default), 1d or 7d.
- `budget_tokens` (integer): Upper bound on the response size in tokens, 200 to 4000. Default 800.
- `operation` (string): Limit to one span name, e.g. 'POST /checkout'.
- `service` (string): Service name. Omit to scan every service seen in the window.
- `since` (string): Window start: RFC 3339 time or a duration ago such as 30m or 2h. Default 30m.
- `until` (string): Window end: RFC 3339 time or a duration ago. Default now.

### `what_changed` (~199 tokens)

What changed

Ranked list of what changed in a service (or all services) across metrics, logs and traces, compared with a baseline. Returns a one-paragraph summary, findings with before/after values, onset times and evidence links, and per-signal coverage. Start here.

Input parameters:

- `baseline` (string): What to compare against: previous (the windows just before; default), 1d or 7d (same window that many days earlier).
- `budget_tokens` (integer): Upper bound on the response size in tokens, 200 to 4000. Default 800.
- `service` (string): Service name. Omit to scan every service seen in the window.
- `since` (string): Window start: RFC 3339 time or a duration ago such as 30m or 2h. Default 30m.
- `until` (string): Window end: RFC 3339 time or a duration ago. Default now.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/asinha07-spoor/ghcr-io-asinha07-spoor#diagnostics

## Score history

- 2026-11-05: 45
- 2026-11-04: 45
- 2026-11-03: 44
- 2026-11-02: 44
- 2026-11-01: 43
- 2026-10-31: 43
- 2026-10-30: 43
- 2026-10-29: 42
- 2026-10-28: 42
- 2026-10-27: 41
- 2026-10-26: 41
- 2026-10-25: 40
- 2026-10-24: 40
- 2026-10-23: 39
- 2026-10-22: 39
- 2026-10-21: 38
- 2026-10-20: 38
- 2026-10-19: 37
- 2026-10-18: 37
- 2026-10-17: 36
- 2026-10-16: 36

## Common questions

### What is the Spoor MCP server?

Spoor is an MCP server listed in the public MCP registry as io.github.asinha07/spoor. What changed across metrics, logs and traces, and where it started (Grafana, Victoria, New Relic). This page covers its container image (ghcr.io/asinha07/spoor).

### Is the Spoor MCP server safe to use?

Spoor scores 45 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Spoor MCP server expose?

Spoor exposes 4 tools: list_services, new_errors, trace_diff, what_changed. Their descriptions and schemas cost roughly 655 tokens of context every time the server is loaded.

### Is the Spoor MCP server still maintained?

Spoor is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- GitHub Container Registry: https://ghcr.io/asinha07/spoor
- Repository: https://github.com/asinha07/spoor
- Website: https://telespoor.com/
- Changelog RSS feed: https://verifymcp.io/servers/asinha07-spoor/ghcr-io-asinha07-spoor.xml
- Changelog JSON feed: https://verifymcp.io/servers/asinha07-spoor/ghcr-io-asinha07-spoor.json
- HTML version of this page: https://verifymcp.io/servers/asinha07-spoor/ghcr-io-asinha07-spoor