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

Results / @bolthub/mcp

@bolthub/mcp

version tested 0.7.2npmtested 2026-11-20Sealmark 1.0.1methodology 0.3-draftSTANDARD run22 tools

Sealmark's automated test of @bolthub/mcp 0.7.2 on 2026-11-20 gave it grade B, its lowest test-area grade (protocol B). Only 6 of 22 tools could be called with default settings, so this grade covers the handshake and tool metadata only. Of its 6 checks, 3 passed, 1 partial, 1 inconclusive and 1 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 6 of 22 tools could be called with default settings, so this grade covers the handshake and tool metadata only.

Grade by test area

B
Protocol3.5/4 points

Protocol checks

CheckVerdictWhat happened
protocol
Valid MCP handshake and tool schemas
pass
handshake ok, 22 well-formed tool(s)
Evidence for protocol: 1 line
  1. Probe initialize + tools/list
    Outcome server bolthub 0.7.2 answered; 22 tool(s)
    Decided from the MCP exchange (protocol)
tool-poisoningcritical
No tool-poisoning indicators in tool metadata
pass
scanned 22 tool definition(s) and serverInfo, including parameter text: nothing suspicious
robust-input
Survives malformed tool input
partial
0 internals leak(s), 5 invalid call(s) accepted, 4 unhandled runtime error(s)
Evidence for robust-input: first 6 of 9 lines
  1. Probe search_apis: every typed argument has the wrong type
    Outcome call succeeded: the server accepted schema-invalid arguments
    Decided from what the server returned (response) · tool search_apis
  2. Probe search_apis: every typed argument is null
    Outcome call succeeded: the server accepted schema-invalid arguments
    Decided from what the server returned (response) · tool search_apis
  3. Probe search_apis: wrong types plus an unexpected extra argument
    Outcome call succeeded: the server accepted schema-invalid arguments
    Decided from what the server returned (response) · tool search_apis
  4. Probe search_apis: every string argument is an object
    Outcome call succeeded: the server accepted schema-invalid arguments
    Decided from what the server returned (response) · tool search_apis
  5. Probe call_api: every typed argument has the wrong type
    Outcome an unhandled runtime error, not a validation decision: Error: (args.method ?? "GET").toUpperCase is not a function
    Decided from what the server returned (response) · tool call_api
  6. Probe call_api: every typed argument is null
    Outcome an unhandled runtime error, not a validation decision: Error: Cannot read properties of null (reading 'startsWith')
    Decided from what the server returned (response) · tool call_api
secret-echocritical
No environment secret echoed in responses
pass
canary secrets absent from tools/list and 95 captured response(s), 5 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
inconclusive
every control call failed, so the read-only annotation could not be checked
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
pass
call_api, revoke_token carry no annotations and changed nothing

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
search_apisNo check listed here called it with a valid call.None
get_api_detailsNo check listed here called it with a valid call.None
preview_costNo check listed here called it with a valid call.
call_apiNone
buy_creditNo check listed here called it with a valid call.
mint_scoped_tokenNo check listed here called it with a valid call.
revoke_tokenNone
deploy_nodeNo check listed here called it with a valid call.None
node_statusNo check listed here called it with a valid call.None
list_apiNo check listed here called it with a valid call.None
publish_listingNo check listed here called it with a valid call.None
analyze_listingNo check listed here called it with a valid call.None
get_earningsNo check listed here called it with a valid call.None
usage_summaryNo check listed here called it with a valid call.None
connect_accountNo check listed here called it with a valid call.None
connect_statusNo check listed here called it with a valid call.
create_workspaceNo check listed here called it with a valid call.None
connect_walletNo check listed here called it with a valid call.None
get_onboarding_stateNo check listed here called it with a valid call.None
open_streamNo check listed here called it with a valid call.None
read_streamNo check listed here called it with a valid call.None
close_streamNo check listed here called it with a valid call.None

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 (0.7.2), the same Sealmark version (1.0.1).

  1. Bv0.7.2Sealmark 1.0.0
  2. Bv0.7.2Sealmark 1.0.1
  3. Bv0.7.2Sealmark 1.0.1

Package facts

License
MIT
Latest release
0.7.2, published 25 Jul 2026 (the version graded on this page)
Repository
signaltech-org/bolthub-sdk
Last push
18 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 0.7.2, the version graded on this page, with the start command from the test run. For a client that reads an mcpServers JSON file:

{
  "mcpServers": {
    "bolthub-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@bolthub/mcp@0.7.2"
      ]
    }
  }
}

Or add it to Claude Code:

claude mcp add bolthub-mcp -- npx -y "@bolthub/mcp@0.7.2"

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 @bolthub/mcp@0.7.2"

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 @bolthub/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.