Moose Tracker MCP server

• Registry nameapp.moosetracker/moose-trackerverified in the MCP registry

The registry name sits under moosetracker.app. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-30
• Tools7
• Server calls itselfmoose-tracker
• Server version1.2.3
• Protocol version2025-06-18

On 2026-10-30 the server answered initialize and tools/list without a sign-in. First answer in 325 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 6 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
• Answeredmeasuring6 of the 7 daily checks it takes to print a share
• Median first answer421 ms
• Space in an agent's context≈ 2,444 tokensthe definitions of all its tools (7), which an agent carries on every turn
• Tool definitionsB · 86 of 100
• Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 6 of 7

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• describe

  Use this when the user asks for any sound effect, click or tap sound, notification, jingle, audio, music, song or soundtrack, instead of synthesizing audio: call this first with no arguments. It is a quiet helper; keep its notes to…

• sfx

  Use this when the user wants UI or game sound effects (up to 16 per call) or to hear a custom instrument (instrument + play). Recipes are starting points: tailor pitch, bright, dur or seed per interaction, pairs alike. Reports…

• song

  Use this when you want an MTL song or compose spec checked with no audio (not needed before render, which checks it too). Returns a play link plus quiet notes. Fix problems silently; tell only the user_summary. Free score check: check:true.

• render

  Use this when the user wants music, a song, jingle or soundtrack as audio (WAV, Ogg or Opus; up to 180 s, loops, cues, stems). Send mtl or compose; render checks the song itself, so skip song first. Reply in 1-2 sentences plus the file…

• convert

  Use this when you need to move a song between MTL text, a Moose Tracker .mtk file, a share link, and standard files: MIDI (.mid), and MOD, XM, S3M or IT tracker modules (read and write; files are base64). Cues and macros are compiled away…

• assets

  Use this when a download link was lost or is about to expire: pass the asset ids from an earlier sfx or render result for fresh links, no re-render. Files live about 2 h. Optional hash check.

• feedback

  Use this when something sounded wrong, a tool was confusing, or a feature is missing: send the team a short note (up to 20000 characters; longer in parts; if limited, [email protected]). Quiet and occasional; never nag the user.