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

Results / oddsrail

oddsrail

version tested 0.19.0PyPItested 2026-11-20Sealmark 1.0.1methodology 0.3-draftSTANDARD run42 tools

Sealmark's automated test of oddsrail 0.19.0 on 2026-11-20 gave it grade D, its lowest test-area grade (protocol A and effects D). Only 15 of 42 tools could be called with default settings, so the deeper test areas cover only those tools. Of its 6 checks, 4 passed, 1 partial 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.

D

Grade D

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

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

Grade by test area

A
Protocol4/4 points
D
Effects0.5/1 pointsincludes a weak signal, not a security finding

Protocol checks

CheckVerdictWhat happened
protocol
Valid MCP handshake and tool schemas
pass
handshake ok, 42 well-formed tool(s)
Evidence for protocol: 1 line
  1. Probe initialize + tools/list
    Outcome server oddsrail 0.19.0 answered; 42 tool(s)
    Decided from the MCP exchange (protocol)
tool-poisoningcritical
No tool-poisoning indicators in tool metadata
pass
scanned 42 tool definition(s), the server instructions and serverInfo, 4 prompt(s), including parameter text: nothing suspicious
robust-input
Survives malformed tool input
pass
103 invalid call(s) rejected cleanly
Evidence for robust-input: 1 line
  1. Probe 103 invalid call(s) across 22 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 106 captured response(s), 3 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

Effects checks

CheckVerdictWhat happened
annotation-honestyweak signal
Read-only tools change nothing
partial
declared read-only; only caches changed (sandbox home or temp): paper_positions
Weak signal, not a security finding. A tool declared read-only changed only cache files, in its sandbox home or temp folder. A partial counts as half a point.
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
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
search_marketsNo check listed here called it with a valid call.None
get_marketNo check listed here called it with a valid call.None
get_orderbookNo check listed here called it with a valid call.None
price_historyNo check listed here called it with a valid call.None
get_positionsNo check listed here called it with a valid call.None
overshoot_signalNo check listed here called it with a valid call.None
dispute_riskNo check listed here called it with a valid call.None
check_orderNo check listed here called it with a valid call.None
place_orderNo check listed here called it with a valid call.None
cancel_orderNo check listed here called it with a valid call.None
open_ordersNone
builder_statsNo check listed here called it with a valid call.None
attribution_ledgerNone
kalshi_search_marketsNo check listed here called it with a valid call.None
kalshi_get_marketNo check listed here called it with a valid call.None
kalshi_get_orderbookNo check listed here called it with a valid call.None
kalshi_get_tradesNo check listed here called it with a valid call.None
kalshi_balanceNone
kalshi_positionsNo check listed here called it with a valid call.None
kalshi_open_ordersNo check listed here called it with a valid call.None
kalshi_place_orderNo check listed here called it with a valid call.None
kalshi_cancel_orderNo check listed here called it with a valid call.None
find_marketsNo check listed here called it with a valid call.None
compare_venuesNo check listed here called it with a valid call.None
quote_costNo check listed here called it with a valid call.None
order_statusNo check listed here called it with a valid call.
my_fillsNo check listed here called it with a valid call.
my_positionsNo check listed here called it with a valid call.
my_balanceNo check listed here called it with a valid call.
cancel_all_ordersNo check listed here called it with a valid call.
split_positionNo check listed here called it with a valid call.
merge_positionsNo check listed here called it with a valid call.
redeem_positionsNo check listed here called it with a valid call.
paper_positionsNo check listed here called it with a valid call.
paper_resetNo check listed here called it with a valid call.
watch_bookNo check listed here called it with a valid call.
redeemable_positionsNo check listed here called it with a valid call.
resolution_criteriaNo check listed here called it with a valid call.
closing_soonNo check listed here called it with a valid call.
settlement_auditNo check listed here called it with a valid call.
position_sizeNo check listed here called it with a valid call.
server_infoNo 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 (0.19.0), the same Sealmark version (1.0.1).

  1. Dv0.19.0Sealmark 1.0.0
  2. Dv0.19.0Sealmark 1.0.1
  3. Dv0.19.0Sealmark 1.0.1

Badge for the README

The badge shows this automated result for version 0.19.0. It is a link to this page, not a certificate, and it changes when the next re-test does.

Sealmark badge for oddsrail
The flat badge, one letter per graded test area.
[![Sealmark](https://sealmark.dev/badge/oddsrail.svg)](https://sealmark.dev/results/oddsrail/)

Files: badge SVG, card SVG, shields endpoint JSON.

Package facts

License
MIT License
Latest release
0.19.0, published 24 Sep 2026 (the version graded on this page)
Repository
hmesutozsoy/oddsrail
Last push
29 Oct 2026
Open issues and pull requests
0

From PyPI 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.19.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": {
    "oddsrail": {
      "command": "uvx",
      "args": [
        "oddsrail==0.19.0"
      ]
    }
  }
}

Or add it to Claude Code:

claude mcp add oddsrail -- uvx oddsrail==0.19.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 "uvx oddsrail==0.19.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 oddsrail 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.