# Rock Regeneration Gigs (oci · ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0)

Search upcoming gigs from the Rock Regeneration gig guide (southern England).

- Trust score: 52/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- oci · `ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0`: 52/100 (this document), [markdown](https://verifymcp.io/servers/cuotos-rock-regeneration-gigs-mcp/ghcr-io-cuotos-rock-regeneration-gigs-mcp-2-0-0.md), [page](https://verifymcp.io/servers/cuotos-rock-regeneration-gigs-mcp/ghcr-io-cuotos-rock-regeneration-gigs-mcp-2-0-0)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0`
- 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-10-18.

- **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 artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 32/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 25 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 86/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 185 tokens (~185/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 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 Rock Regeneration Gigs MCP server?

Rock Regeneration Gigs runs locally as a container image, launched with docker run --rm -i ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0. 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 cuotos-rock-regeneration-gigs-mcp -- docker run --rm -i ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0
```

### Cursor

```json
{
  "mcpServers": {
    "cuotos-rock-regeneration-gigs-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cuotos-rock-regeneration-gigs-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cuotos-rock-regeneration-gigs-mcp -- docker run --rm -i ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cuotos-rock-regeneration-gigs-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cuotos-rock-regeneration-gigs-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "cuotos-rock-regeneration-gigs-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cuotos-rock-regeneration-gigs-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0"
      ]
    }
  }
}
```

## 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-10-17 (score 52, +1)

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

### 2026-10-15 (score 51, +1)

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

### 2026-10-13 (score 50, +1)

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

### 2026-10-12 (score 49, +1)

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

### 2026-10-10 (score 48, +1)

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

### 2026-10-07 (score 47, +1)

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

### 2026-10-05 (score 46, +1)

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

### 2026-10-02 (score 45, +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.

## MCP tools (1)

### `search_gigs` (~185 tokens)

Search for upcoming gigs and live music events from the Rock Regeneration gig guide, covering venues across southern England (Hampshire, Dorset, Wiltshire, Isle of Wight, etc). Returns structured event data. All filters are optional — omit to return everything.

Input parameters:

- `artist` (string): Filter by artist or band name — partial, case-insensitive match.
- `from_date` (string): Only return gigs on or after this date. Format: YYYY-MM-DD.
- `location` (string): Filter by town or city. Automatically expands to include nearby towns in the same area (e.g. 'Southampton' also returns Eastleigh, Winchester, Hedge End, etc.).
- `to_date` (string): Only return gigs on or before this date. Format: YYYY-MM-DD.
- `venue` (string): Filter by venue name — partial, case-insensitive match.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cuotos-rock-regeneration-gigs-mcp/ghcr-io-cuotos-rock-regeneration-gigs-mcp-2-0-0#diagnostics

## Score history

- 2026-10-18: 52
- 2026-10-17: 52
- 2026-10-16: 51
- 2026-10-15: 51
- 2026-10-14: 50
- 2026-10-13: 50
- 2026-10-12: 49
- 2026-10-10: 48
- 2026-10-07: 47
- 2026-10-05: 46
- 2026-10-04: 45
- 2026-10-03: 45
- 2026-10-02: 45
- 2026-10-01: 44
- 2026-09-30: 44
- 2026-09-29: 43
- 2026-09-28: 43
- 2026-09-27: 42
- 2026-09-26: 42
- 2026-09-25: 41
- 2026-09-24: 40
- 2026-09-23: 40
- 2026-09-22: 40

## Common questions

### What is the Rock Regeneration Gigs MCP server?

Rock Regeneration Gigs is an MCP server listed in the public MCP registry as io.github.cuotos/rock-regeneration-gigs-mcp. Search upcoming gigs from the Rock Regeneration gig guide (southern England). This page covers its container image (ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0).

### Is the Rock Regeneration Gigs MCP server safe to use?

Rock Regeneration Gigs scores 52 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 Rock Regeneration Gigs MCP server expose?

Rock Regeneration Gigs exposes 1 tool: search_gigs. Their descriptions and schemas cost roughly 185 tokens of context every time the server is loaded.

### Is the Rock Regeneration Gigs MCP server still maintained?

Rock Regeneration Gigs is still listed as active in the MCP registry. We last reached this channel on 18 October 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/cuotos/rock-regeneration-gigs-mcp
- Repository: https://github.com/cuotos/rock-regeneration-gigs-mcp
- Changelog RSS feed: https://verifymcp.io/servers/cuotos-rock-regeneration-gigs-mcp/ghcr-io-cuotos-rock-regeneration-gigs-mcp-2-0-0.xml
- Changelog JSON feed: https://verifymcp.io/servers/cuotos-rock-regeneration-gigs-mcp/ghcr-io-cuotos-rock-regeneration-gigs-mcp-2-0-0.json
- HTML version of this page: https://verifymcp.io/servers/cuotos-rock-regeneration-gigs-mcp/ghcr-io-cuotos-rock-regeneration-gigs-mcp-2-0-0