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

Results / statuz-cli

statuz-cli

version tested 2.4.0npmtested 2026-11-20Sealmark 1.0.1methodology 0.3-draftSTANDARD run34 tools

Sealmark's automated test of statuz-cli 2.4.0 on 2026-11-20 gave it grade A, its lowest test-area grade (protocol A and effects A). Only 12 of 34 tools could be called with default settings, so the deeper test areas cover only those tools. Of its 10 checks, 6 passed, 2 inconclusive and 2 not applicable. 3 more checks are advisory, and advisory checks never change a grade: 1 failed and 2 not applicable. The run used Sealmark 1.0.1 with the standard settings.

A

Grade A

The server's grade is its lowest test-area grade. How grading works

Only 12 of 34 tools could be called with default settings, so the deeper test areas cover only those tools.

Grade by test area

A
Protocol4/4 points
A
Effects2/2 points

Protocol checks

CheckVerdictWhat happened
protocol
Valid MCP handshake and tool schemas
pass
handshake ok, 34 well-formed tool(s)
Evidence for protocol: 1 line
  1. Probe initialize + tools/list
    Outcome server statuz 2.4.0 answered; 34 tool(s)
    Decided from the MCP exchange (protocol)
tool-poisoningcritical
No tool-poisoning indicators in tool metadata
pass
scanned 34 tool definition(s), the server instructions and serverInfo, 1 resource(s), including parameter text: nothing suspicious
robust-input
Survives malformed tool input
pass
114 invalid call(s) rejected cleanly
Evidence for robust-input: 1 line
  1. Probe 114 invalid call(s) across 24 tool(s)
    Outcome all rejected cleanly and the server stayed responsive
    Decided from the MCP exchange (protocol)
secret-echocritical
No environment secret echoed in responses
pass
canary secrets absent from tools/list and 115 captured response(s), 1 of them successful result(s)
instructions-hygiene (advisory)
Server instructions name only tools that exist
fail
the server instructions names 1 tool(s) the server does not offer (statuz)
refusal-quality (advisory)
Refusals say what to do next
n/a
no refusal was recorded in this run, so there is nothing to judge

Network checks

CheckVerdictWhat happened
net-loopback-ssrfcritical
Refuses loopback targets (SSRF)
inconclusive
the listener saw nothing, but 27 of 27 probes were not explicitly refused (27 failed without saying the target was refused), so a refusal cannot be told from a tool that cannot fetch at all (a reply that only reports a failed fetch (proxy, socket, DNS) is not read as a refusal; set net.control_url to a URL the tool can reach)
net-scheme-allowlistcritical
Only http(s) schemes accepted
inconclusive
no scheme had an observable effect, but 6 of 18 scored probes were not explicitly refused, so a refusal cannot be told from a tool that cannot fetch at all (a reply that only reports a failed fetch (proxy, socket, DNS) is not read as a refusal; set net.control_url to a URL the tool can reach)
net-caps
Response size and time are capped
n/a
net-loopback-ssrf was inconclusive: the server never reached the loopback listener, so no loopback URL is known to be fetchable; response size and time caps were not measured
net-redirect
Redirects are re-validated
n/a
the server refused or never reached the loopback listener, so redirect handling could not be observed (a server that blocks loopback cannot be sent a redirect it would follow)

Effects checks

CheckVerdictWhat happened
annotation-honestycritical
Read-only tools change nothing
pass
posts_list, accounts_list, accounts_check, media_list, config_list, agents_list, status, logs, cloud_pricing declared read-only and changed nothing in the observed directories during a benign call (reach_check, open not judged: the control call failed)
openworld-honesty
Closed-world tools stay on the machine
pass
10 closed-world tool(s) called; none reached out beyond what was asked
undeclared-writes (advisory)
Unannotated tools leave the sandbox unchanged
n/a
every tool carries annotations, nothing to check

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

Under a check, Evidence shows what it probed (sent or inspected) and what it observed in this run: up to 6 lines per check, each cut at 240 characters, for checks that are not security checks. The text is shortened, and paths and anything that looks like a secret or token are replaced. Run sealmark run --format json yourself for every line in full.

By tool

Which checks called each tool with a valid call in this run, and which did not exercise it. A check can leave a tool out for several reasons: a limit Sealmark sets, a tool left out by design, input the run could not fill in, or a call that returned an error. The CLI report gives the reason. A verdict belongs to the whole check, not to one tool: a failed check that called three tools does not say which one failed. Security checks are left out of this table.

ToolCalled byNot exercised by
posts_createNo check listed here called it with a valid call.None
posts_listNo check listed here called it with a valid call.None
posts_getNo check listed here called it with a valid call.None
posts_editNo check listed here called it with a valid call.None
posts_deleteNo check listed here called it with a valid call.None
posts_publishNo check listed here called it with a valid call.None
posts_recentNo check listed here called it with a valid call.None
posts_lookupNo check listed here called it with a valid call.None
posts_searchNo check listed here called it with a valid call.None
reach_checkNo check listed here called it with a valid call.None
dms_sendNo check listed here called it with a valid call.None
accounts_listNo check listed here called it with a valid call.None
accounts_connectNo check listed here called it with a valid call.None
accounts_removeNo check listed here called it with a valid call.None
accounts_defaultNo check listed here called it with a valid call.None
accounts_moveNo check listed here called it with a valid call.None
accounts_checkNo check listed here called it with a valid call.None
accounts_flairsNo check listed here called it with a valid call.None
media_addNo check listed here called it with a valid call.None
media_listNo check listed here called it with a valid call.None
media_editNo check listed here called it with a valid call.None
media_removeNo check listed here called it with a valid call.None
config_listNone
config_getNo check listed here called it with a valid call.None
config_setNo check listed here called it with a valid call.None
config_unsetNo check listed here called it with a valid call.
initNo check listed here called it with a valid call.
agents_listNo check listed here called it with a valid call.
statusNo check listed here called it with a valid call.
logsNo check listed here called it with a valid call.
openNo check listed here called it with a valid call.
feedbackNo check listed here called it with a valid call.
cloud_moveNo check listed here called it with a valid call.
cloud_pricingNo check listed here called it with a valid call.

What was not covered

Grade over time

Since the run on

Same as that run: the same grade in every test area, the same tools with the same input schemas, the same server version (2.4.0), the same Sealmark version (1.0.1).

  1. –did not run
  2. Av2.4.0Sealmark 1.0.1
  3. Av2.4.0Sealmark 1.0.1

Package facts

License
UNLICENSED (npm's word for no rights granted to others)
Latest release
2.4.0, published 10 Nov 2026 (the version graded on this page)

From npm, 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 2.4.0, the version graded on this page, with the start command from the test run. For a client that reads an mcpServers JSON file:

{
  "mcpServers": {
    "statuz-cli": {
      "command": "npx",
      "args": [
        "-y",
        "statuz-cli@2.4.0",
        "mcp"
      ]
    }
  }
}

Or add it to Claude Code:

claude mcp add statuz-cli -- npx -y "statuz-cli@2.4.0" mcp

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 statuz-cli@2.4.0 mcp"

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 statuz-cli 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.