Spoor
OCI · GHCR.IO/ASINHA07/SPOOR
What changed across metrics, logs and traces, and where it started (Grafana, Victoria, New Relic).
Available components
Last scanned (3 hours ago)
Scores higher than 64% of OCI servers
Category Monitoring and Observability
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. How we score → Why this is hard to score →
Supply Chain Security0
- 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.Unverified
- 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.Unverified
- Install-script risk not yet assessed.Unverified
- 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.Unverified
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 12 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 23 Oct 26 0
- Package version: 0.2.1 → 0.3.1 functional
- 22 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed oci/ghcr.io/asinha07/spoor@0.3.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_services List services ~64
Services seen in the window and which signals (metrics, logs, traces) have data for each.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | – | Window start: RFC 3339 time or a duration ago. Default 30m. |
| until | string | – | Window end. Default now. |
No output schema declared.
No examples provided.
new_errors New errors ~202
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
trace_diff Trace diff ~190
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
what_changed What changed ~199
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
oci · ghcr.io/asinha07/spoor
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.
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.