Skip to main content
ClaudeWave
cuotos avatar
cuotos

rock-regeneration-gigs-mcp

Ver en GitHub
MCP ServersRegistry oficial0 estrellas0 forksGoActualizado today
ClaudeWave Trust Score
52/100
· OK
Passed
  • Actively maintained (<30d)
  • Documented (README)
Flags
  • !No standard license detected
  • !No description
Last scanned: 9/23/2026
Install in Claude Code / Claude Desktop
Method: Docker · ghcr.io/cuotos/rock-regeneration-gigs-mcp
Claude Code CLI
claude mcp add rock-regeneration-gigs-mcp -- docker run -i --rm ghcr.io/cuotos/rock-regeneration-gigs-mcp
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "rock-regeneration-gigs-mcp": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "ghcr.io/cuotos/rock-regeneration-gigs-mcp"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Casos de uso

Resumen de MCP Servers

# rock-regeneration-gigs-mcp

An MCP server for searching upcoming gigs and live music events from the [Rock Regeneration gig guide](https://www.rock-regeneration.co.uk/gig-guide/), covering venues across southern England (Hampshire, Dorset, Wiltshire, Isle of Wight, etc).

## Usage

Add to your Claude config:

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

Or with the Claude CLI:

```bash
claude mcp add --transport stdio gigs -- docker run --rm -i ghcr.io/cuotos/rock-regeneration-gigs-mcp
```

## Tools

### `search_gigs`

Search for upcoming gigs. All filters are optional — omit to return everything.

| Parameter   | Type   | Description                                      |
|-------------|--------|--------------------------------------------------|
| `location`  | string | Town or city (expands to nearby towns)           |
| `artist`    | string | Artist or band name (partial, case-insensitive)  |
| `venue`     | string | Venue name (partial, case-insensitive)           |
| `from_date` | string | Start date filter — `YYYY-MM-DD`                 |
| `to_date`   | string | End date filter — `YYYY-MM-DD`                   |

## Testing

Build the image locally:

```bash
docker build -t rock-regeneration-gigs-mcp .
```

Test it responds correctly:

```bash
echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"0"}}}' \
  | docker run --rm -i rock-regeneration-gigs-mcp
```

Expected output:

```json
{"jsonrpc":"2.0","id":1,"result":{"capabilities":{"tools":{}},"protocolVersion":"2024-11-05","serverInfo":{"name":"rock-regeneration-gigs-mcp","version":"..."}}}
```

## Publishing

Pushing a version tag does both halves of a release:

```bash
git tag v1.0.0
git push origin v1.0.0
```

1. The image is built and pushed to `ghcr.io/cuotos/rock-regeneration-gigs-mcp`.
2. The server is published to the [MCP Registry](https://registry.modelcontextprotocol.io) as
   `io.github.cuotos/rock-regeneration-gigs-mcp`, using GitHub OIDC — no secrets needed.

`server.json` keeps a placeholder `0.0.0` version in git; CI rewrites it, and the image tag, from
the git tag at publish time.

The registry verifies ownership by pulling the image and reading its
`io.modelcontextprotocol.server.name` label, so **the GHCR package must be public**. It is private
on first push — make it public once, under the package settings on GitHub.

Check the published entry with:

```bash
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.cuotos/rock-regeneration-gigs-mcp"
```

Lo que la gente pregunta sobre rock-regeneration-gigs-mcp

¿Qué es cuotos/rock-regeneration-gigs-mcp?

+

cuotos/rock-regeneration-gigs-mcp es mcp servers para el ecosistema de Claude AI con 0 estrellas en GitHub.

¿Cómo se instala rock-regeneration-gigs-mcp?

+

Puedes instalar rock-regeneration-gigs-mcp clonando el repositorio (https://github.com/cuotos/rock-regeneration-gigs-mcp) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar cuotos/rock-regeneration-gigs-mcp?

+

Nuestro agente de seguridad ha analizado cuotos/rock-regeneration-gigs-mcp y le ha asignado un Trust Score de 52/100 (tier: OK). Revisa el desglose completo de comprobaciones superadas y flags en esta página.

¿Quién mantiene cuotos/rock-regeneration-gigs-mcp?

+

cuotos/rock-regeneration-gigs-mcp es mantenido por cuotos. La última actividad registrada en GitHub es del 2026-09-22, con 1 issues abiertos.

¿Hay alternativas a rock-regeneration-gigs-mcp?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega rock-regeneration-gigs-mcp en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: cuotos/rock-regeneration-gigs-mcp
[![Featured on ClaudeWave](https://claudewave.com/api/badge/cuotos-rock-regeneration-gigs-mcp)](https://claudewave.com/repo/cuotos-rock-regeneration-gigs-mcp)
<a href="https://claudewave.com/repo/cuotos-rock-regeneration-gigs-mcp"><img src="https://claudewave.com/api/badge/cuotos-rock-regeneration-gigs-mcp" alt="Featured on ClaudeWave: cuotos/rock-regeneration-gigs-mcp" width="320" height="64" /></a>

Más MCP Servers

Alternativas a rock-regeneration-gigs-mcp