Sealmark
Automated re-test on 2026-11-14: not checked by hand, and not yet reviewed by the maintainers.

Results / galaxymovies-mcp

galaxymovies-mcp

version tested 1.0.1npmtested 2026-11-14Sealmark 1.0.1methodology 0.3-draftSTANDARD run7 tools

galaxymovies-mcp 1.0.1: There is no current grade. The last grade was from version 1.0.1, tested on 2026-11-14. The current version, 1.0.2, has failed to start since 2026-11-17, so Sealmark cannot grade it now. The earlier grade stays in this server's history. Of its 4 checks, 4 passed. 2 more checks are advisory, and advisory checks never change a grade: 2 not applicable. The run used Sealmark 1.0.1 with the standard settings.

No current grade

There is no current grade. The last grade was from version 1.0.1, tested on 2026-11-14. The current version, 1.0.2, has failed to start since 2026-11-17, so Sealmark cannot grade it now. The earlier grade stays in this server's history.

Test areas from the last run, 2026-11-14 (not current)

A
Protocol4/4 points

Protocol checks

CheckVerdictWhat happened
protocol
Valid MCP handshake and tool schemas
pass
handshake ok, 7 well-formed tool(s)
tool-poisoningcritical
No tool-poisoning indicators in tool metadata
pass
scanned 7 tool definition(s) and serverInfo, including parameter text: nothing suspicious
robust-input
Survives malformed tool input
pass
30 invalid call(s) rejected cleanly
secret-echocritical
No environment secret echoed in responses
pass
canary secrets absent from tools/list and 30 captured response(s), 0 of them successful result(s)
instructions-hygiene (advisory)
Server instructions name only tools that exist
n/a
the server sent no instructions
refusal-quality (advisory)
Refusals say what to do next
n/a
no refusal was recorded in this run, so there is nothing to judge

Each check id links to what it tests and how to fix a failure. The same text is in sealmark explain <id>.

What was not covered

Grade over time

Since the run on

  • Sealmark changed from 1.0.0 to 1.0.1.

Unchanged: the same grade in every test area, the same server version (1.0.1).

  1. Av1.0.1Sealmark 1.0.0
  2. Av1.0.1Sealmark 1.0.1
  3. –did not run
  4. –did not run
  5. –did not run
  6. –did not run
  7. –did not run
  8. –did not run

Package facts

License
MIT
Latest release
1.0.2, published 17 Nov 2026. This page graded 1.0.1.
Repository
NickFasulo/galaxymovies-mcp
Last push
17 Nov 2026
Open issues and pull requests
0

From npm and GitHub, checked 22 Nov 2026. Plain facts about the package; they play no part in the grade.

Add it to an MCP client

This starts version 1.0.1, the version graded on this page, with the start command from the test run. For a client that reads an mcpServers JSON file:

{
  "mcpServers": {
    "galaxymovies-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "galaxymovies-mcp@1.0.1"
      ]
    }
  }
}

Or add it to Claude Code:

claude mcp add galaxymovies-mcp -- npx -y "galaxymovies-mcp@1.0.1"

The test run started the server with no API keys or other secrets, and with a cleaned environment. If the server needs some, its own documentation says how to pass them.

Run it yourself

This repeats the run with the same Sealmark version and the standard settings, starting the server the same way:

npx -y sealmark@1.0.1 run --start "npx -y galaxymovies-mcp@1.0.1"

To confirm your run used the standard settings, add --format json --out report.json to the command. In the report, config.standard should be true and config.hash should start with sha256:d13e7893a0ac, as they did in this run. If either differs, so did the settings, and the verdicts may too (STANDARD and CUSTOM runs).

To keep the setup, put the start command in sealmark.yaml as the server.

Grade alerts

One email when the grade of galaxymovies-mcp changes after a re-test. Nothing else, and every email has a link to stop them.

Or follow it in a feed reader: the Atom feed lists each move of the overall grade that came with a different version of this server, tested with the same Sealmark version as the graded run before.

Each of 613 verdicts was checked independently, and Sealmark was wrong on some: how reliable Sealmark is.

Is this wrong?

Reply on the GitHub issue or email disclosure@sealmark.dev and we will recheck it. Maintainers can ask for their server to be removed.

If we were wrong, we correct the page and add your reply. Security findings go to the maintainer privately first; see the disclosure policy.