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

Results / spaces-mcp-server

spaces-mcp-server

version tested 1.10.0npmtested 2026-11-20Sealmark 1.0.1methodology 0.3-draftSTANDARD run30 tools

Sealmark's automated test of spaces-mcp-server 1.10.0 on 2026-11-20 gave it grade B, its lowest test-area grade (protocol B and effects A). Only 4 of 30 tools could be called with default settings, so the deeper test areas cover only those tools. Of its 10 checks, 5 passed, 1 partial, 2 inconclusive and 2 not applicable. 3 more checks are advisory, and advisory checks never change a grade: 1 passed and 2 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

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

Grade by test area

B
Protocol3.5/4 points
A
Effects2/2 points

Protocol checks

CheckVerdictWhat happened
protocol
Valid MCP handshake and tool schemas
pass
handshake ok, 30 well-formed tool(s)
Evidence for protocol: 1 line
  1. Probe initialize + tools/list
    Outcome server myspaice 1.10.0 answered; 30 tool(s)
    Decided from the MCP exchange (protocol)
tool-poisoningcritical
No tool-poisoning indicators in tool metadata
pass
scanned 30 tool definition(s), the server instructions and serverInfo, 1 resource(s), including parameter text: nothing suspicious
robust-input
Survives malformed tool input
partial
0 internals leak(s), 7 invalid call(s) accepted
Evidence for robust-input: first 6 of 7 lines
  1. Probe list_spaces: every typed argument has the wrong type
    Outcome call succeeded: the server accepted schema-invalid arguments
    Decided from what the server returned (response) · tool list_spaces
  2. Probe list_spaces: every typed argument is null
    Outcome call succeeded: the server accepted schema-invalid arguments
    Decided from what the server returned (response) · tool list_spaces
  3. Probe list_spaces: wrong types plus an unexpected extra argument
    Outcome call succeeded: the server accepted schema-invalid arguments
    Decided from what the server returned (response) · tool list_spaces
  4. Probe list_spaces: every string argument is an object
    Outcome call succeeded: the server accepted schema-invalid arguments
    Decided from what the server returned (response) · tool list_spaces
  5. Probe browse_marketplace: every typed argument has the wrong type
    Outcome call succeeded: the server accepted schema-invalid arguments
    Decided from what the server returned (response) · tool browse_marketplace
  6. Probe browse_marketplace: wrong types plus an unexpected extra argument
    Outcome call succeeded: the server accepted schema-invalid arguments
    Decided from what the server returned (response) · tool browse_marketplace
secret-echocritical
No environment secret echoed in responses
pass
canary secrets absent from tools/list and 114 captured response(s), 9 of them successful result(s)
instructions-hygiene (advisory)
Server instructions name only tools that exist
pass
the instructions name no tool the server lacks
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 18 of 18 probes were not explicitly refused (18 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 12 of 12 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
whoami, list_spaces, list_kits declared read-only and changed nothing in the observed directories during a benign call (browse_marketplace not judged: the control call failed)
openworld-honesty
Closed-world tools stay on the machine
pass
4 closed-world tool(s) called; nothing connected to the loopback listener (path and git tools cannot be pointed at it, so this confirms only that nothing connected out during the call)
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
whoamiNone
register_agentNo check listed here called it with a valid call.None
update_profileNo check listed here called it with a valid call.None
list_spacesNo check listed here called it with a valid call.None
get_space_detailsNo check listed here called it with a valid call.None
create_spaceNo check listed here called it with a valid call.None
list_kitsNone
join_spaceNo check listed here called it with a valid call.None
get_game_statusNo check listed here called it with a valid call.None
get_updatesNo check listed here called it with a valid call.None
submit_actionNo check listed here called it with a valid call.None
send_messageNo check listed here called it with a valid call.None
react_to_messageNo check listed here called it with a valid call.None
voteNo check listed here called it with a valid call.None
leave_spaceNo check listed here called it with a valid call.None
ready_upNo check listed here called it with a valid call.None
share_contentNo check listed here called it with a valid call.None
send_gifNo check listed here called it with a valid call.None
pokeNo check listed here called it with a valid call.None
emoteNo check listed here called it with a valid call.None
mention_playerNo check listed here called it with a valid call.None
send_ghost_messageNo check listed here called it with a valid call.None
send_ghost_gifNo check listed here called it with a valid call.None
browse_marketplaceNo check listed here called it with a valid call.None
get_agent_profileNo check listed here called it with a valid call.None
recall_memoriesNo check listed here called it with a valid call.
invite_agentNo check listed here called it with a valid call.
space_commandNo check listed here called it with a valid call.
drawNo check listed here called it with a valid call.
look_atNo 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.10.0), the same Sealmark version (1.0.1).

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

Package facts

License
MIT
Latest release
1.10.0, published 9 Oct 2026 (the version graded on this page)
Repository
neltomw/spaces-mcp-server
Last push
9 Oct 2026
Open issues and pull requests
1

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.10.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": {
    "spaces-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "spaces-mcp-server@1.10.0"
      ]
    }
  }
}

Or add it to Claude Code:

claude mcp add spaces-mcp-server -- npx -y "spaces-mcp-server@1.10.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 spaces-mcp-server@1.10.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 spaces-mcp-server 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.

The issue we opened No reply yet

Sealmark opened a public issue on this project's repository on 17 Nov 2026 to share this grade. No reply yet. A reply is optional.

Read the issue on GitHub. State as of the last re-test run.

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.