# io.github.ljcl/intervals-mcp (oci · ghcr.io/ljcl/intervals-mcp:2.1.1)

Remote MCP server for intervals.icu run data and analysis

- Trust score: 20/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- oci · `ghcr.io/ljcl/intervals-mcp:2.1.1`: 20/100 (this document), [markdown](https://verifymcp.io/servers/ljcl-intervals-mcp/ghcr-io-ljcl-intervals-mcp-2-1-1.md), [page](https://verifymcp.io/servers/ljcl-intervals-mcp/ghcr-io-ljcl-intervals-mcp-2-1-1)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/ljcl/intervals-mcp:2.1.1`
- Transport: `streamable-http`

## 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-09-28.

- **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**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to ljcl/intervals-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: 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

```bash
docker pull ghcr.io/ljcl/intervals-mcp:2.1.1
```

## 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-09-28 (score 20, +10)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 10)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/ljcl-intervals-mcp/ghcr-io-ljcl-intervals-mcp-2-1-1#diagnostics

## Score history

- 2026-09-28: 20
- 2026-09-27: 10

## Common questions

### What is the io.github.ljcl/intervals-mcp server?

io.github.ljcl/intervals-mcp is listed in the public MCP registry as io.github.ljcl/intervals-mcp. Remote MCP server for intervals.icu run data and analysis. This page covers its container image (ghcr.io/ljcl/intervals-mcp:2.1.1).

### Is the io.github.ljcl/intervals-mcp server safe to use?

io.github.ljcl/intervals-mcp scores 20 out of 100 on VerifyMCP. Its build provenance is signed and verified. 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.

### Is the io.github.ljcl/intervals-mcp server still maintained?

io.github.ljcl/intervals-mcp is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.ljcl/intervals-mcp server under?

io.github.ljcl/intervals-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- GitHub Container Registry: https://ghcr.io/ljcl/intervals-mcp
- Repository: https://github.com/ljcl/intervals-mcp
- Changelog RSS feed: https://verifymcp.io/servers/ljcl-intervals-mcp/ghcr-io-ljcl-intervals-mcp-2-1-1.xml
- Changelog JSON feed: https://verifymcp.io/servers/ljcl-intervals-mcp/ghcr-io-ljcl-intervals-mcp-2-1-1.json
- HTML version of this page: https://verifymcp.io/servers/ljcl-intervals-mcp/ghcr-io-ljcl-intervals-mcp-2-1-1