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

Results / @spideriq/mcp-gate

@spideriq/mcp-gate

version tested 1.16.0npmtested 2026-11-20Sealmark 1.0.1methodology 0.3-draftSTANDARD run46 tools

Sealmark's automated test of @spideriq/mcp-gate 1.16.0 on 2026-11-20 gave it grade B, its lowest test-area grade (protocol B). None of the 46 tools could be called with default settings, so this grade covers the handshake and tool metadata only. Of its 6 checks, 2 passed, 2 partial and 2 not applicable. 3 more checks are advisory, and advisory checks never change a grade: 3 not applicable. The run used Sealmark 1.0.1 with the standard settings.

B

Grade B

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

None of the 46 tools could be called with default settings, so this grade covers the handshake and tool metadata only.

Grade by test area

B
Protocol3/4 pointsincludes a weak signal, not a security finding

Protocol checks

CheckVerdictWhat happened
protocol
Valid MCP handshake and tool schemas
pass
handshake ok, 46 well-formed tool(s)
Evidence for protocol: 1 line
  1. Probe initialize + tools/list
    Outcome server spideriq-gate 1.16.0 answered; 46 tool(s)
    Decided from the MCP exchange (protocol)
tool-poisoningweak signal
No tool-poisoning indicators in tool metadata
partial
1 weak indicator(s) worth reading, none conclusive
Weak signal, not a security finding. Some wording in the tool text is worth a read, but none of it is conclusive. A partial counts as half a point.
robust-input
Survives malformed tool input
partial
0 internals leak(s), 101 invalid call(s) accepted, 3 unhandled runtime error(s)
Evidence for robust-input: first 6 of 104 lines
  1. Probe request_access: every typed argument has the wrong type
    Outcome an unhandled runtime error, not a validation decision: Error: (opts.recoverAs ?? "").trim is not a function
    Decided from what the server returned (response) · tool request_access
  2. Probe request_access: wrong types plus an unexpected extra argument
    Outcome an unhandled runtime error, not a validation decision: Error: (opts.recoverAs ?? "").trim is not a function
    Decided from what the server returned (response) · tool request_access
  3. Probe request_access: every string argument is an object
    Outcome an unhandled runtime error, not a validation decision: Error: (opts.recoverAs ?? "").trim is not a function
    Decided from what the server returned (response) · tool request_access
  4. Probe check_access_status: required arguments missing
    Outcome call succeeded: the server accepted schema-invalid arguments
    Decided from what the server returned (response) · tool check_access_status
  5. Probe check_access_status: every typed argument is null
    Outcome call succeeded: the server accepted schema-invalid arguments
    Decided from what the server returned (response) · tool check_access_status
  6. Probe get_auth_status: every typed argument has the wrong type
    Outcome call succeeded: the server accepted schema-invalid arguments
    Decided from what the server returned (response) · tool get_auth_status
secret-echocritical
No environment secret echoed in responses
pass
canary secrets absent from tools/list and 109 captured response(s), 101 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

Effects checks

CheckVerdictWhat happened
annotation-honestycritical
Read-only tools change nothing
n/a
no tool declares readOnlyHint: true
openworld-honesty
Closed-world tools stay on the machine
n/a
no tool declares openWorldHint: false that could be given a harness-owned control argument
undeclared-writes (advisory)
Unannotated tools leave the sandbox unchanged
n/a
no unannotated read-style tool could be given a harness-owned control argument

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
request_accessNo check listed here called it with a valid call.None
check_access_statusNo check listed here called it with a valid call.None
get_auth_statusNo check listed here called it with a valid call.None
logoutNo check listed here called it with a valid call.None
list_workspacesNo check listed here called it with a valid call.
health_checkNo check listed here called it with a valid call.None
get_queue_statsNo check listed here called it with a valid call.None
get_api_infoNo check listed here called it with a valid call.None
gate_chatNo check listed here called it with a valid call.None
gate_modelsNo check listed here called it with a valid call.None
gate_aliasesNo check listed here called it with a valid call.None
gate_healthNo check listed here called it with a valid call.None
gate_media_modelsNo check listed here called it with a valid call.None
gate_media_generateNo check listed here called it with a valid call.None
gate_catalog_listNo check listed here called it with a valid call.None
gate_catalog_getNo check listed here called it with a valid call.None
gate_leaderboardNo check listed here called it with a valid call.None
gate_catalog_model_evalsNo check listed here called it with a valid call.None
gate_statsNo check listed here called it with a valid call.None
gate_usageNo check listed here called it with a valid call.None
gate_capacityNo check listed here called it with a valid call.None
gate_flowNo check listed here called it with a valid call.None
gate_usage_by_taskNo check listed here called it with a valid call.None
gate_subscriptionsNo check listed here called it with a valid call.None
gate_groupNo check listed here called it with a valid call.None
gate_agentsNo check listed here called it with a valid call.
gate_providersNo check listed here called it with a valid call.
gate_tracesNo check listed here called it with a valid call.
gate_trace_detailNo check listed here called it with a valid call.
gate_trace_statsNo check listed here called it with a valid call.
gate_prompt_createNo check listed here called it with a valid call.
gate_prompt_listNo check listed here called it with a valid call.
gate_prompt_searchNo check listed here called it with a valid call.
gate_prompt_getNo check listed here called it with a valid call.
gate_prompt_deleteNo check listed here called it with a valid call.
gate_client_alias_listNo check listed here called it with a valid call.
gate_client_alias_getNo check listed here called it with a valid call.
gate_client_alias_createNo check listed here called it with a valid call.
gate_client_alias_updateNo check listed here called it with a valid call.
gate_client_alias_deleteNo check listed here called it with a valid call.
gate_onboarding_statusNo check listed here called it with a valid call.
gate_onboarding_updateNo check listed here called it with a valid call.
gate_recipesNo check listed here called it with a valid call.
gate_provider_guideNo check listed here called it with a valid call.
gate_add_keyNo check listed here called it with a valid call.
gate_invite_contributorNo 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 server version (1.16.0), the same Sealmark version (1.0.1).

  1. Bv1.16.0Sealmark 1.0.0
  2. Bv1.16.0Sealmark 1.0.1
  3. Bv1.16.0Sealmark 1.0.1

Package facts

License
MIT
Latest release
1.16.0, published 25 Oct 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 1.16.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": {
    "spideriq-mcp-gate": {
      "command": "npx",
      "args": [
        "-y",
        "@spideriq/mcp-gate@1.16.0"
      ]
    }
  }
}

Or add it to Claude Code:

claude mcp add spideriq-mcp-gate -- npx -y "@spideriq/mcp-gate@1.16.0"

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 @spideriq/mcp-gate@1.16.0"

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 @spideriq/mcp-gate 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.