# moontide-mcp

Claude steers live music by writing Strudel code played in a browser page

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 2.0.2
- **Author:** Konni
- **License:** AGPL-3.0-or-later
- **npm:** moontide-mcp
- **Source:** https://github.com/konni-arcadia/moontide
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 1 day

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-13T11:42:49.284Z
- **Version scanned:** 2.0.2
- **CVEs:** none found by OSV at scan time

## Tools

14 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `get_code` — Reads the Strudel code currently playing in the Moontide page, i.e. the last code the page confirmed,
- `get_strudel_reference`
- `set_code` — Replaces the music in the Moontide page with new Strudel code; the new pattern takes over within a fraction of a second, mid-cycle, without stopping the music.
- `edit_code`
- `list_history` — Lists the versions of the music that played, newest first, one per row: "#id — time (UTC) — origin — \"label\" — first line of code". Ids never change. Rows wit
- `favorite_version` — Keeps a version as a named favorite, by its id from list_history (the version playing now is the one shown as v{id} in the page top bar). Favorites are never dr
- `restore_version`
- `stop` — Stops all sound in the Moontide page right away, even when the current code is broken. The code stays in the editor; get_code still returns it, and the next set
- `get_midi_instruments`
- `search_midi_sounds`
- `save_midi_model`
- `save_midi_catalog`
- `set_page_requests`
- `start`

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"moontide\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"moontide-mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Moderate to extensive — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: mutates data; runs on your machine.
- Floor 30, ceiling 54 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/moontide-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/moontide-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/moontide-mcp
- HTML page: https://forgeregistry.com/registry/moontide-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.