Results / @workpods/agent-ready
@workpods/agent-ready
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.
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
Protocol checks
| Check | Verdict | What 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
| Check | Verdict | What 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
| Check | Verdict | What 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
- 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
- SQLite: Not applicable. No tool takes a SQL string
- Tool "journey_observe" was not covered by the net test area: only the first 6 URL tools are probed
- Tools that a server lists only for clients that declare roots, sampling or elicitation capabilities are not seen: the harness declares none
- Tool "backlinks_summary" is covered by the protocol checks only: argument "target" 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 "link_gap" is covered by the protocol checks only: free-text parameter "domain": no path, URL, command, SQL or repository signal; add it under tools: to include it
- Tool "journey_act" is covered by the protocol checks only: free-text parameter "journeyId": no path, URL, command, SQL or repository signal; its required parameter "action" cannot be filled by the harness; write a probes: entry to call it
- SSRF: link-local and private-range addresses are never contacted; redirects from a public host to loopback and DNS rebinding are not tested (the harness contacts only its own loopback listener)
- 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 server version (0.1.1), the same Sealmark version (1.0.1).
- –did not run
- Fv0.1.1Sealmark 1.0.1
- 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.
[](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.
Related servers
Other servers graded in the same test area, most areas in common first, then by grade.
- @certscore/mcp · grade A · Network
- @kazuph/mcp-fetch · grade A · Network
- duckduckgo-mcp-server · grade A · Network
- mcp-server-fetch · grade A · Network
- @cleanor/mcp · grade F (the grade includes a finding under private disclosure) · Network
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.