# electron.dance (remote · electron.dance)

electron.dance MCP server: upcoming gigs, community links, RSVP, and Spotify top tracks.

- Trust score: 82/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `electron.dance`: 82/100 (this document), [markdown](https://verifymcp.io/servers/ric-lavers-electron-dance/api-mcp.md), [page](https://verifymcp.io/servers/ric-lavers-electron-dance/api-mcp)

## Channel facts

- Endpoint: `https://electron.dance/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 275 tokens (~45/item across 6 items; 4 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% 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).

## Install

### How do I install the electron.dance MCP server?

electron.dance is a hosted endpoint at https://electron.dance/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ric-lavers-electron-dance 'https://electron.dance/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ric-lavers-electron-dance": {
      "url": "https://electron.dance/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ric-lavers-electron-dance": {
      "type": "http",
      "url": "https://electron.dance/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ric-lavers-electron-dance]
url = "https://electron.dance/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ric-lavers-electron-dance": {
      "type": "remote",
      "url": "https://electron.dance/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ric-lavers-electron-dance --url 'https://electron.dance/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ric-lavers-electron-dance:
    url: "https://electron.dance/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ric-lavers-electron-dance": {
      "Transport": "http",
      "Url": "https://electron.dance/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ric-lavers-electron-dance -t streamable-http -u 'https://electron.dance/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ric-lavers-electron-dance": {
      "type": "http",
      "url": "https://electron.dance/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-15 (score 82, +1)

- [security] Stability: 0.97 → pass

### 2026-09-13 (score 81, +1)

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

### 2026-09-11 (score 80, +1)

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

### 2026-09-09 (score 79, +1)

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

### 2026-09-07 (score 78, +1)

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

### 2026-09-05 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 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-09-02 (score 76, +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-08-31 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 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.

## MCP tools (4)

### `list_upcoming_gigs` (~86 tokens)

List upcoming gigs

List upcoming electron.dance gigs, each with its current going/maybe attendance. Use this for 'what's on tonight/this week/this weekend' style questions instead of scraping the website — results are sorted soonest-first, so filter/take the first entries for 'tonight'. Open to anyone.

Input parameters:

- `limit` (integer): Max number of gigs to return

### `rsvp_to_gig` (~72 tokens)

RSVP to a gig

Set attendance status for a gig (going, maybe, or none to clear it), on behalf of the site's configured default user. Requires a bearer token.

Input parameters:

- `gigId` (string, required): The gig's Event _id, as returned by list_upcoming_gigs
- `status` (string, required)

### `get_top_tracks` (~27 tokens)

Get Spotify top tracks

Get electron.dance's current Spotify top tracks (short term). Requires a bearer token.

### `get_site_links` (~47 tokens)

Get site links

Get electron.dance's public community/social links (WhatsApp, Instagram, SoundCloud, DJ Cards, mixes, Listen/Navidrome, SMS bot, gigs page). Open to anyone.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ric-lavers-electron-dance/api-mcp#diagnostics

## Score history

- 2026-09-20: 82
- 2026-09-19: 82
- 2026-09-18: 82
- 2026-09-17: 82
- 2026-09-16: 82
- 2026-09-15: 82
- 2026-09-14: 81
- 2026-09-13: 81
- 2026-09-12: 80
- 2026-09-11: 80
- 2026-09-10: 79
- 2026-09-09: 79
- 2026-09-08: 78
- 2026-09-07: 78
- 2026-09-06: 77
- 2026-09-05: 77
- 2026-09-04: 76
- 2026-09-03: 76
- 2026-09-02: 76
- 2026-09-01: 75
- 2026-08-31: 75
- 2026-08-30: 74
- 2026-08-29: 74
- 2026-08-28: 73
- 2026-08-27: 73
- 2026-08-26: 72
- 2026-08-25: 71
- 2026-08-24: 70
- 2026-08-23: 70
- 2026-08-22: 69

## Common questions

### What is the electron.dance MCP server?

electron.dance is an MCP server listed in the public MCP registry as io.github.Ric-Lavers/electron-dance. electron.dance MCP server: upcoming gigs, community links, RSVP, and Spotify top tracks. This page covers its hosted endpoint (https://electron.dance/api/mcp).

### Is the electron.dance MCP server safe to use?

electron.dance scores 82 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 electron.dance MCP server expose?

electron.dance exposes 4 tools: list_upcoming_gigs, rsvp_to_gig, get_top_tracks, get_site_links. Their descriptions and schemas cost roughly 232 tokens of context every time the server is loaded.

### Does the electron.dance MCP server require authentication?

No. We connected to electron.dance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the electron.dance MCP server still maintained?

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

## Links

- Remote endpoint: https://electron.dance/api/mcp
- Repository: https://github.com/Ric-Lavers/electron.dance
- Website: https://electron.dance/
- Changelog RSS feed: https://verifymcp.io/servers/ric-lavers-electron-dance/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ric-lavers-electron-dance/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ric-lavers-electron-dance/api-mcp