Results / dsail
dsail
Sealmark's automated test of dsail 1.0.6 on 2026-11-20 gave it grade B, its lowest test-area grade (protocol B and effects A). Only 8 of 20 tools could be called with default settings, so the deeper test areas cover only those tools. Of its 6 checks, 4 passed and 2 partial. 3 more checks are advisory, and advisory checks never change a grade: 1 passed, 1 failed and 1 not applicable. The run used Sealmark 1.0.1 with the standard settings.
Grade B
The server's grade is its lowest test-area grade. How grading works
Only 8 of 20 tools could be called with default settings, so the deeper test areas cover only those tools.
Grade by test area
Protocol checks
| Check | Verdict | What happened |
|---|---|---|
| protocol Valid MCP handshake and tool schemas | pass | handshake ok, 20 well-formed tool(s) Evidence for protocol: 1 line
|
| tool-poisoningweak signal No tool-poisoning indicators in tool metadata | partial | 4 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), 1 invalid call(s) accepted Evidence for robust-input: 1 line
|
| secret-echocritical No environment secret echoed in responses | pass | canary secrets absent from tools/list and 71 captured response(s), 3 of them successful result(s) |
| instructions-hygiene (advisory) Server instructions name only tools that exist | fail | the server instructions names 27 tool(s) the server does not offer (dsail_review, within_hard_cap, signed_in, consumer_finance, capital_markets) |
| 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
| Check | Verdict | What happened |
|---|---|---|
| annotation-honestycritical Read-only tools change nothing | pass | dsail_get_account_status, dsail_unit_library, dsail_list_workspaces declared read-only and changed nothing in the observed directories during a benign call (dsail_load_ruleset, dsail_list_rulesets not judged: the control call failed) |
| openworld-honesty Closed-world tools stay on the machine | pass | 7 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 | pass | dsail_open_review 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.
| Tool | Called by | Not exercised by |
|---|---|---|
| dsail_compile | No check listed here called it with a valid call. | None |
| dsail_check | No check listed here called it with a valid call. | None |
| dsail_get_prompt_pack | No check listed here called it with a valid call. | |
| dsail_save_ruleset | No check listed here called it with a valid call. | None |
| dsail_load_ruleset | No check listed here called it with a valid call. | None |
| dsail_list_rulesets | No check listed here called it with a valid call. | |
| dsail_record_approval | No check listed here called it with a valid call. | None |
| dsail_get_account_status |
| None |
| dsail_issue_api_key | No check listed here called it with a valid call. | |
| dsail_unit_library | No check listed here called it with a valid call. | |
| dsail_add_unit_converter | No check listed here called it with a valid call. | None |
| dsail_list_workspaces |
| None |
| dsail_use_workspace | No check listed here called it with a valid call. | None |
| dsail_create_team | No check listed here called it with a valid call. | None |
| dsail_invite_to_team | No check listed here called it with a valid call. | None |
| dsail_team_members | No check listed here called it with a valid call. | None |
| dsail_set_team_role | No check listed here called it with a valid call. | None |
| dsail_remove_from_team | No check listed here called it with a valid call. | None |
| dsail_copy_ruleset | No check listed here called it with a valid call. | None |
| dsail_open_review |
| None |
What was not covered
- Database: Not applicable. The start command takes no database connection, so the database tests did not run. ({dsn}, {host} and the like are placeholders that Sealmark fills in with its own test database.)
- HTTP: Not applicable. The server is started over stdio; the http test area needs server.url
- Files: Not applicable. The server config has no {sandbox} placeholder, so the harness cannot tell which directory the server is allowed to use (a server with a wider root would read the canary legitimately); pass {sandbox} as its directory argument, or, if the server has no root argument and works in its working directory, set server.rootless: true
- Git: Not applicable. No tool is classified as taking a git repository path with medium confidence or higher
- Network: Not applicable. No tool is classified as taking a URL with medium confidence or higher
- SQLite: Not applicable. No tool takes a SQL string
- Tool "dsail_compile" (path) was not probed by the fs test area: the server config has no {sandbox} placeholder, so the harness cannot tell which directory the server is allowed to use (a server with a wider root would read the canary legitimately); pass {sandbox} as its directory argument, or, if the server has no root argument and works in its working directory, set server.rootless: true
- Tool "dsail_copy_ruleset" (path) was not probed by the fs test area: the server config has no {sandbox} placeholder, so the harness cannot tell which directory the server is allowed to use (a server with a wider root would read the canary legitimately); pass {sandbox} as its directory argument, or, if the server has no root argument and works in its working directory, set server.rootless: true
- Tools that a server lists only for clients that declare roots, sampling or elicitation capabilities are not seen: the harness declares none
- Tool "dsail_check" is covered by the protocol checks only: would be path (param "source"), but required parameter "claims" cannot be filled by the harness; write a probes: entry to call it
- Tool "dsail_list_rulesets" is covered by the protocol checks only: the tool takes no parameters
- Tool "dsail_record_approval" is covered by the protocol checks only: argument "name" could be a path, but nothing in the tool name, its title or the parameter's own description says so; add it under tools: to include it
- Tool "dsail_get_account_status" is covered by the protocol checks only: the tool takes no parameters
- Tool "dsail_issue_api_key" is covered by the protocol checks only: free-text parameter "label": no path, URL, command, SQL or repository signal; add it under tools: to include it
- Tool "dsail_unit_library" is covered by the protocol checks only: free-text parameter "from_unit": no path, URL, command, SQL or repository signal; add it under tools: to include it
- Tool "dsail_add_unit_converter" is covered by the protocol checks only: free-text parameter "attribution": no path, URL, command, SQL or repository signal; add it under tools: to include it
- Tool "dsail_list_workspaces" is covered by the protocol checks only: the tool takes no parameters
- Tool "dsail_use_workspace" is covered by the protocol checks only: free-text parameter "workspace": no path, URL, command, SQL or repository signal; add it under tools: to include it
- Tool "dsail_create_team" is covered by the protocol checks only: argument "name" could be a path, but nothing in the tool name, its title or the parameter's own description says so; add it under tools: to include it
- Tool "dsail_invite_to_team" is covered by the protocol checks only: free-text parameter "email": no path, URL, command, SQL or repository signal; add it under tools: to include it
- Tool "dsail_team_members" is covered by the protocol checks only: free-text parameter "team_id": no path, URL, command, SQL or repository signal; add it under tools: to include it
- 2 more tool(s) are covered by the protocol checks only (see the classification)
- Tool "dsail_get_prompt_pack" was not covered by the core test area: needs probes: to be called (no argument the harness can safely malform)
- Tool "dsail_list_rulesets" was not covered by the core test area: its no-argument call returned an error, so no tool behaviour was exercised
- Tool "dsail_issue_api_key" was not covered by the core test area: needs probes: to be called (no argument the harness can safely malform)
- Tool "dsail_unit_library" was not covered by the core test area: needs probes: to be called (no argument the harness can safely malform)
- The sandbox is a convention the harness follows, not a security boundary. A malicious server runs with your user's privileges, sees the real file system and network, and can ignore cwd, HOME and PATH. Run untrusted servers in a throwaway VM or container.
- Prompt injection carried in tool output (only tool metadata is scanned)
- Authentication and transport security
- Audit logging (not measured by these test areas; only the db test area has an advisory audit check)
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 (1.0.6), the same Sealmark version (1.0.1).
- –did not run
- Bv1.0.6Sealmark 1.0.1
- Bv1.0.6Sealmark 1.0.1
Badge for the README
The badge shows this automated result for version 1.0.6. It is a link to this page, not a certificate, and it changes when the next re-test does.
[](https://sealmark.dev/results/dsail/)
Files: badge SVG, card SVG, shields endpoint JSON.
Package facts
- License
- Apache-2.0
- Latest release
- 1.0.6, published 9 Oct 2026 (the version graded on this page)
From PyPI, 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.6, the version graded on this page, with the start command from the test run. For a client that reads an mcpServers JSON file:
{
"mcpServers": {
"dsail": {
"command": "uvx",
"args": [
"dsail==1.0.6",
"mcp"
]
}
}
}Or add it to Claude Code:
claude mcp add dsail -- uvx dsail==1.0.6 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 "uvx dsail==1.0.6 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 dsail 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.