Moose Tracker

Is Moose Tracker MCP server safe?

• No hidden instructions were found in its tool descriptions.
• Its error messages showed no secrets or internal details.
• 4 of its 7 tools are labeled read-only; the others may change or send things.
• Overall it scored 93/100 on 30 Oct 2026.

A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.

What it can do

7 tools, in the server's own words.

Test results

Safe mode: only tools labeled read-only were run. How the test works

• !
  Every tool is described

  5 warnings

  • !describe: Inputs with no description: topic, detail, cursor, limit
  • !render: Inputs with no description: cue, loudness, zip
  • !convert: Inputs with no description: from, to
  • !assets: Inputs with no description: ids
  • !feedback: Inputs with no description: type
  note
• ✓
  ConnectsConnected in 263 ms
  pass
• ✓
  Ready for the newest MCP versionUses the latest MCP version (2026-07-28)
  pass
• ✓
  Lists its toolsFound 7 tools
  pass
• ✓
  Tools are labeled safe or dangerousEvery tool has a safety label
  pass
• ✓
  No hidden instructionsNo hidden instructions found in tool descriptions
  pass
• ✓
  Tools work with good inputs

  All good

  • ✓describe: Worked (230 ms)
  • ✓song: Answered with an error, probably because of our sample input: "mtl or compose" is required: send a song as mtl, or a compose spec (describe topic="generators"). {"ok":false}
  • ✓convert: Answered with an error, probably because of our sample input: Could not convert: The .mtk file could not be read as a Moose Tracker song: Unexpected token 'e', "test" is not valid JSON {"ok":false,"pro…
  • ✓assets: Answered with an error, probably because of our sample input: 0 of 1 links renewed. - test: not an asset id (expected <32 hex>.<wav|ogg|opus|zip|json>) {"status":"error","assets":[{"assetId":"test","st…
  • –sfx: Not run: labeled as changing data
  • –render: Not run: labeled as changing data
  • –feedback: Not run: labeled as changing data
  pass
• ✓
  Bad inputs give a clean error

  All good

  • ✓describe: Refused wrong type for "topic" with a clear error
  • ✓song: Refused wrong type for "mtl" with a clear error
  • ✓convert: Refused missing required input "from" with a clear error
  • ✓convert: Refused wrong type for "from" with a clear error
  • ✓assets: Refused missing required input "ids" with a clear error
  • ✓assets: Refused wrong type for "ids" with a clear error
  pass
• ✓
  Fast enough

  All good

  • ✓Connecting took 263 ms
  • ✓Listing tools took 111 ms
  • ✓Average tool answer: 181 ms
  • ✓describe: Slowest tool: describe (230 ms)
  pass
• ✓
  No secrets leakedChecked 9 error messages: no secrets or internal details
  pass
• ✓
  Follows MCP best practices (not scored yet)Tool names, safety labels and tool list size follow the MCP guide
  pass
• –
  Tools work togetherNo tool's answer could be fed into another tool, so there were no chains to test (not counted either way)
  not tested

Test it yourself

Free and open source. Same checks, same score.

Show this score on GitHub

Free for every server in the directory. Paste this into your README: the badge shows the score from our latest test.

Score over time

• 30 Oct 202693

One test so far. New tests will show here.

Reviews

Coming soon: reviews from people who use Moose Tracker, signed in with GitHub, one per person. Reviews never change the score.