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

Results / @workpods/agent-ready

@workpods/agent-ready

version tested 0.1.1npmtested 2026-11-20Sealmark 1.0.1methodology 0.3-draftSTANDARD run12 tools

Sealmark's automated test of @workpods/agent-ready 0.1.1 on 2026-11-20 gave it grade F, its lowest test-area grade (protocol A, network F and effects A). Tools reached with a valid call: 9 of 12. Of its 10 checks, 5 passed, 3 failed, 1 partial and 1 not applicable. 3 more checks are advisory, and advisory checks never change a grade: 1 failed and 2 not applicable. The run used Sealmark 1.0.1 with the standard settings. The grade includes a finding under private disclosure; it still counts in full.

F

Grade F

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

The grade includes a finding under private disclosure. It still counts in full.

Tools reached with a valid call: 9 of 12.

Grade by test area

A
Protocol4/4 points
F
Network0.5/4 pointscritical: net-loopback-ssrfincludes a finding under private disclosure
A
Effects1/1 points

Protocol checks

CheckVerdictWhat happened
protocol
Valid MCP handshake and tool schemas
pass
handshake ok, 12 well-formed tool(s)
tool-poisoningcritical
No tool-poisoning indicators in tool metadata
pass
scanned 12 tool definition(s) and serverInfo, including parameter text: nothing suspicious
robust-input
Survives malformed tool input
pass
59 invalid call(s) rejected cleanly
secret-echocritical
No environment secret echoed in responses
pass
canary secrets absent from tools/list and 59 captured response(s), 0 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
fail
0 of 9 refusal(s) say what to do instead or why retrying will not help (0 %)

Network checks

CheckVerdictWhat happened
net-loopback-ssrfcritical
Refuses loopback targets (SSRF)
fail
A security finding is being reported to the maintainer privately. Details will be published when it is fixed or 90 days after the report (disclosure policy).
net-scheme-allowlistcritical
Only http(s) schemes accepted
partial
A security finding is being reported to the maintainer privately. Details will be published when it is fixed or 90 days after the report (disclosure policy).
net-caps
Response size and time are capped
fail
size: the server read the whole 64 MiB body (the listener sent 64 of 64 MiB) and returned 0.01 MiB: it capped its reply, not what it reads; time: no reply within 18 s (timeout_probe_sec 10 + 8 s; a server whose own fetch timeout is longer fails this half although it caps: set --timeout-probe to its value)
net-redirect
Redirects are re-validated
fail
A security finding is being reported to the maintainer privately. Details will be published when it is fixed or 90 days after the report (disclosure policy).

Effects checks

CheckVerdictWhat happened
annotation-honestycritical
Read-only tools change nothing
pass
audit_page, crawl_site, site_files declared read-only and changed nothing in the observed directories during a benign call (see_as_agent, compare_pages, read_ai_answer, keyword_ideas, keyword_gap, journey_observe not judged: the control call failed)
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>.

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

  1. –did not run
  2. Fv0.1.1Sealmark 1.0.1
  3. Fv0.1.1Sealmark 1.0.1

Badge for the README

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

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

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

Package facts

License
Apache-2.0

From npm, checked 22 Nov 2026. Plain facts about the package; they play no part in the grade.

Run it yourself

The command for this run is withheld while a security finding is reported privately. It is published with the report, when the finding is fixed or 90 days after the report.

Other servers graded in the same test area, most areas in common first, then by grade.

Grade alerts

One email when the grade of @workpods/agent-ready changes after a re-test. Nothing else, and every email has a link to stop them.

Each of 613 verdicts was checked independently, and Sealmark was wrong on some: how reliable Sealmark is.

Is this wrong?

Reply to our private report 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.