Skip to content

MCP servers › io.github.konni-arcadia › moontide

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.konni-arcadia/moontide

Claude steers live music by writing Strudel code played in a browser page — the publisher's description

9 of 9 record checks metRead-only · tools listed 2026-10-23Topic: media-and-design · AI-classifiedversion 2.2.0JavaScriptAGPL-3.0-or-laterstandard input/output15 tools

Summary

io.github.konni-arcadia/moontide is a local MCP server listed in the official MCP registry at version 2.2.0. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 15 tools, 10 resources and 3 prompts.

Record checks

9 of 9 record checks met

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • met: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • met: npm package carries build provenance (attestation)
  • met: No known critical or high advisory in the package or its dependencies
  • #2,738 of 15,112 packages by monthly downloads, tied with 4 others
  • Not ranked by stars: 4 stars (ranked from 10)
  • #429 of 1,074 packages meeting all 9 record checks, by downloads

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
local package
Transport
standard input/output
Package
npm · listed version current
License
AGPL-3.0-or-later
Dependencies
no known high or critical advisories
Repository
public
Tools
15
Described as changing data
10 of 15 toolsAI-classified
Mainly works on
files and code on the machine it runs on; a web browser or desktop applicationsAI-classified
Topic
media-and-designAI-classified
Last tested
2026-10-23

Add to your client

Worth knowing before you connect it

  • 10 tools are described as changing something (set_code, edit_code, favorite_version, …): our AI model's reading of the descriptions, not something we tested. We did not call them.
  • Its package is signed and carries a build record naming its source.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
2.2.0, published 2026-10-17 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-11 (earliest version still in the registry; older removed versions would be earlier)
Version history
5 versions listed, 2026-10-11 to 2026-10-17; 5 in the 90 days before the 2026-10-23 snapshot.
Most recent 5 versions
  • 2.2.0 · 2026-10-17
  • 2.1.0 · 2026-10-15
  • 2.0.2 · 2026-10-12
  • 2.0.1 · 2026-10-11
  • 2.0.0 · 2026-10-11
(versions still listed in the registry only)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-23
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 2.2.0 (published 2026-10-17).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
15tools
10resources
3prompts

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on; a web browser or desktop applications.

10 of 15 tools are described as changing something (creating, editing, deleting, sending or running).

  • get_codeon 4 other serversreads or searches

    “Reads the Strudel code currently playing in the Moontide page, i.e.”

    Publisher declares: read-only yes

    Takes no inputs.

  • get_strudel_referencereads or searches

    “Returns the Strudel reference for @strudel/repl 1.3.0, the version the Moontide page loads: facts about what exists and how to write it, not what to choose.”

    Publisher declares: read-only yes

    1 input
    • topicstring“One topic to return; omit it to get the index of topics”
  • set_codecreates or changes datadescribed as changing data

    “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.”

    6 inputs, 1 required
    • codestringrequired“Complete Strudel code to play”
    • labelstring“A few words saying what this change is, for example "added a bass"; shown by list_history”
    • atstring“When the change takes over: 'now' (the default) within a fraction of a second, 'bar' on the next bar line, 'phrase' on the next phrase line (4 cycles, counted …”
    • phraseCyclesinteger“How many cycles one phrase lasts, for at: 'phrase' (2 to 64, default 4)”
    • glideBarsinteger“Whole bars, 1 to 64, to move the tempo smoothly from the tempo that plays to the one this code sets with setcps or setcpm; with at, it starts at the line.”
    • answeringstring“The id of the page request this change answers, from its request line; the page shows that request as applied only when the change names it here”
  • edit_codecreates or changes datadescribed as changing data

    “Changes part of the code that will play by exact text replacement, sending only the change.”

    7 inputs, 1 required
    • editsarrayrequired“The replacements, 1 to 50, applied all together or not at all”
    • baseinteger“The version number get_code shows (#N); the edit is refused when another version plays now”
    • labelstring“A few words saying what this change is, for example "added a bass"; shown by list_history”
    • atstring“When the change takes over: 'now' (the default) within a fraction of a second, 'bar' on the next bar line, 'phrase' on the next phrase line (4 cycles, counted …”
    • phraseCyclesinteger“How many cycles one phrase lasts, for at: 'phrase' (2 to 64, default 4)”
    • glideBarsinteger“Whole bars, 1 to 64, to move the tempo smoothly from the tempo that plays to the one this code sets with setcps or setcpm; with at, it starts at the line.”
    • answeringstring“The id of the page request this change answers, from its request line; the page shows that request as applied only when the change names it here”
  • list_historyon 9 other serversreads or searches

    “Lists the versions of the music that played, newest first, one per row: "#id — time (UTC) — origin — \"label\" — first line of code".”

    Publisher declares: read-only yes

    3 inputs
    • limitinteger“How many versions to list, newest first (default 20)”
    • filterstring“Only versions whose label, code or favorite name contains this text (case-insensitive)”
    • favoritesboolean“true to list only favorites”
  • favorite_versioncreates or changes datadescribed as changing data

    “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).”

    2 inputs, 2 required
    • idintegerrequired“Version id from list_history”
    • namestringrequired“Name to keep it under, in the user's words”
  • restore_versionon 7 other serverscreates or changes datadescribed as changing data

    “Plays a past version again, by its id from list_history, in one call: it takes over within a fraction of a second without stopping the music, with the same checks as set_code.”

    2 inputs, 1 required
    • idintegerrequired“Version id from list_history, for example 41 for #41”
    • answeringstring“The id of the page request this change answers, from its request line; the page shows that request as applied only when the change names it here”
  • answer_requeston 2 other serverssends messagesdescribed as changing data

    “Closes a request typed in the Moontide page without changing the music.”

    Publisher declares: destructive no

    3 inputs, 3 required
    • idstringrequired“The id of the page request to close, from its request line”
    • outcomestringrequired“answered when the request was answered in words, declined when it will not or cannot be done”
    • textstringrequired“One sentence for the user, at most 200 characters; the page shows it under the request”
  • stopon 16 other serversdescribed as changing data

    “Stops all sound in the Moontide page right away, even when the current code is broken.”

    Publisher declares: destructive no · idempotent yes

    Takes no inputs.

  • get_midi_instrumentsreads or searches

    “When the user has described their instruments, call this before writing MIDI code.”

    Publisher declares: read-only yes

    1 input
    • instrumentstring“An instrument id from instruments.json, to list its sounds”
  • search_midi_soundsreads or searches

    “Searches the sound catalog of one instrument: a list of the model's sounds kept in the user's data folder, built from a patch-name file or a sound list the user owns.”

    Publisher declares: read-only yes

    3 inputs, 1 required
    • instrumentstringrequired“An instrument id from instruments.json whose model has a sound catalog”
    • querystring“Words to find in the sound name or its category, in any order; case and spaces do not matter”
    • categorystring“Only sounds of this category; case and spaces do not matter”
  • save_midi_modelcreates or changes datadescribed as changing data

    “Saves an instrument model that you drafted from a page of the instrument's manual the user pasted, into the user's Moontide data folder (models/<id>.json), never into Moontide itself.”

    3 inputs, 2 required
    • modelobjectrequired“The drafted model, as a JSON object”
    • confirmedbooleanrequired“false to check and summarize without saving; true only after the user said yes to the summary”
    • overwriteboolean“true to replace an existing user model with the same id”
Show 3 more tools
  • save_midi_catalogcreates or changes datadescribed as changing data

    “Saves a sound catalog that you drafted from a sound list the user gave you (for example the maker's PDF list), into the user's Moontide data folder (catalogs/<model id>.json), never into Moontide its…”

    8 inputs, 1 required
    • modelstringrequired“The id of the model the catalog extends: a model Moontide ships or one saved with save_midi_model”
    • confirmedboolean“true only after the user said yes to the summary; send it with model and nothing else”
    • appendboolean“true to add this part to the draft of the model; absent or false starts a new draft”
    • moreboolean“true while more parts remain; absent or false on the last part”
    • sourcestring“The document title and version the list comes from; required when a draft starts”
    • programNumberingstring“How the list numbers programs: from-1 when the first program is printed as 1; required when a draft starts”
    • overwriteboolean“true to replace an existing catalog of the model; read when a draft starts”
    • banksarray“The sounds of this part, grouped by bank and category; at most 500 sounds in the call”
  • set_page_requestscreates or changes datadescribed as changing data

    “Switches how requests the user types in the Moontide page reach you.”

    Publisher declares: destructive no · idempotent yes

    1 input, 1 required
    • statestringrequired“on to receive each page request right away, off to let them wait for the reply of your next other Moontide tool”
  • starton 6 other serversdescribed as changing data

    “Starts Moontide: its web server on this computer and its page, which opens in a new browser tab; one click in that tab turns the sound on.”

    Publisher declares: destructive no · idempotent yes

    Takes no inputs.

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 15 tools
Says what it returns
69% of 13 tools
States limits, defaults or errors
47% of 15 tools
Says when to use it
100% of 5 tools
Items covered per tool
3.1 of 4 on average

Counted from the listing

Parameters with a description
100% of 40
Tools with a description
100% of 15
Typical description length
819 characters

The tool set

Counted from the listing

Tools
15
Size of the list
about 5,962 tokens for an agent to load (characters ÷ 4)
Naming
13 of 15 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 15 of 15 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the npm package moontide-mcp

Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
  "mcpServers": {
    "moontide": {
      "command": "npx",
      "args": [
        "-y",
        "moontide-mcp@2.2.0"
      ]
    }
  }
}
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "moontide": {
      "command": "npx",
      "args": [
        "-y",
        "moontide-mcp@2.2.0"
      ]
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "moontide": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "moontide-mcp@2.2.0"
      ]
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"moontide","type":"stdio","command":"npx","args":["-y","moontide-mcp@2.2.0"]}'
Claude Code
claude mcp add --transport stdio moontide -- npx -y moontide-mcp@2.2.0
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y moontide-mcp@2.2.0
  • This runs the publisher's code on your machine (npx). Read its README first.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
2.2.0
Latest stable
2.2.0
Status
current
Withdrawn
no

Source: registry.npmjs.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

critical0high0moderate0low0

Counted in the full dependency tree as resolved on 2026-10-23 (npm audit). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity
sha512-iCoZhoDp0pDArwVDG…
Signature
signed and attested
License
AGPL-3.0-or-later

Source: the package registry · 2026-10-23.

Usage

Downloads
952 in the last month

Source: api.npmjs.org · 2026-10-23.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Published package can be startedStarted and answeredmatchesour test · 2026-10-23
Version 2.2.0 on npmExists and can be installedmatchesnpm · 2026-10-23
Repository github.com/konni-arcadia/moontideOpens publiclymatchesapi.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.konni-arcadia
GitHub owner
a personal account (konni-arcadia)
Build record
signed and attested
Repository
github.com/konni-arcadia/moontide
Stars
4
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
SECURITY.md

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

9 of 9 record checks met

  • #2,738 of 15,112 packages by monthly downloads, tied with 4 others
  • Not ranked by stars: 4 stars (ranked from 10)
  • #429 of 1,074 packages meeting all 9 record checks, by downloads
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
  • MetPackage names its licence with a standard (SPDX) identifierAGPL-3.0-or-later
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
  • Metnpm package carries build provenance (attestation)Signed, with a build attestation naming the source and workflow.
  • MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.konni-arcadia/moontide

Answered from the data above

Is io.github.konni-arcadia/moontide safe to install?

We do not rate servers as safe or unsafe. 9 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its npm package carries a build-provenance attestation that names its source repository and build workflow. Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 10 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.konni-arcadia/moontide been security tested?

Partly. 4 of the 13 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.konni-arcadia/moontide do?

It lists 15 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data and send messages. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.konni-arcadia/moontide change or delete data?

10 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.konni-arcadia/moontide publish a security policy?

Yes: its repository has a public security policy (github.com/konni-arcadia/moontide/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Is the listed version current?

Yes. The registry lists 2.2.0, the latest stable release on npm.

Where is the source code of io.github.konni-arcadia/moontide?

In github.com/konni-arcadia/moontide, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “media-and-design” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: exercised
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not applicable
  17. Consent handling: not applicable
  18. Sign-in metadata: not applicable

4 exercised9 not run (reason given)5 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 13 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 4
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.exercised
Not run, with the reason · 9
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
Does not apply to this server · 5
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted the published package in an isolated sandbox (read-only mode)
  2. 5,284 msConnected after 0 redirects.
  3. Read the inventory: 15 tools, 10 resources, 3 prompts.
  4. 6,622 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
AI-classified · 2026-10-23
Pricing modelAI-classified
not checked
no website in the registry entry
Programming language
api.github.com · 2026-10-23
Hosting type
registry · 2026-10-23
MCP capability
prompts, resources, tools
our test · 2026-10-23
Transport
standard input/output
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
registry · 2026-10-23
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
package registry · 2026-10-23
Integrity hash
declared (sri)
package registry · 2026-10-23
Signature / provenance
package registry · 2026-10-23
Dependency advisories
none known
npm audit · 2026-10-23
Popularity
952 downloads a month
package registry · 2026-10-23
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9 · build record: signed and attested
api.github.com · 2026-10-23
Maintenance
api.github.com · 2026-10-23
Environment
your machine
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.konni-arcadia/moontide: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.konni-arcadia/moontide

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 9 of 9 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.konni-arcadia/moontide)](https://protocolprobe.com/mcp/servers/io.github.konni-arcadia/moontide)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology