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

Results / @spideriq/mcp-publish

@spideriq/mcp-publish

version tested 1.43.1npmtested 2026-11-20Sealmark 1.0.1methodology 0.3-draftSTANDARD run164 tools

Sealmark's automated test of @spideriq/mcp-publish 1.43.1 on 2026-11-20 gave it grade B, its lowest test-area grade (protocol B). Only 6 of 164 tools could be called with default settings, so this grade covers the handshake and tool metadata only. Of its 10 checks, 3 passed, 1 partial, 2 inconclusive and 4 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 164 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, 164 well-formed tool(s)
Evidence for protocol: 1 line
  1. Probe initialize + tools/list
    Outcome server spideriq-publish 1.43.1 answered; 164 tool(s)
    Decided from the MCP exchange (protocol)
tool-poisoningcritical
No tool-poisoning indicators in tool metadata
pass
scanned 164 tool definition(s) and serverInfo, including parameter text: nothing suspicious
robust-input
Survives malformed tool input
partial
0 internals leak(s), 104 invalid call(s) accepted, 3 unhandled runtime error(s)
Evidence for robust-input: first 6 of 107 lines
  1. Probe request_access: every typed argument has the wrong type
    Outcome an unhandled runtime error, not a validation decision: Error: (opts.recoverAs ?? "").trim is not a function
    Decided from what the server returned (response) · tool request_access
  2. Probe request_access: wrong types plus an unexpected extra argument
    Outcome an unhandled runtime error, not a validation decision: Error: (opts.recoverAs ?? "").trim is not a function
    Decided from what the server returned (response) · tool request_access
  3. Probe request_access: every string argument is an object
    Outcome an unhandled runtime error, not a validation decision: Error: (opts.recoverAs ?? "").trim is not a function
    Decided from what the server returned (response) · tool request_access
  4. Probe check_access_status: required arguments missing
    Outcome call succeeded: the server accepted schema-invalid arguments
    Decided from what the server returned (response) · tool check_access_status
  5. Probe check_access_status: every typed argument is null
    Outcome call succeeded: the server accepted schema-invalid arguments
    Decided from what the server returned (response) · tool check_access_status
  6. Probe get_auth_status: every typed argument has the wrong type
    Outcome call succeeded: the server accepted schema-invalid arguments
    Decided from what the server returned (response) · tool get_auth_status
secret-echocritical
No environment secret echoed in responses
pass
canary secrets absent from tools/list and 112 captured response(s), 104 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

Network checks

CheckVerdictWhat happened
net-loopback-ssrfcritical
Refuses loopback targets (SSRF)
inconclusive
the listener saw nothing, but 18 of 18 probes were not explicitly refused (0 failed without saying the target was refused), so a refusal cannot be told from a tool that cannot fetch at all (a reply that only reports a failed fetch (proxy, socket, DNS) is not read as a refusal; set net.control_url to a URL the tool can reach; the tool may be a lookup rather than a fetcher, settle it with tools.overrides)
net-scheme-allowlistcritical
Only http(s) schemes accepted
inconclusive
no scheme had an observable effect, but 12 of 12 scored probes were not explicitly refused, so a refusal cannot be told from a tool that cannot fetch at all (a reply that only reports a failed fetch (proxy, socket, DNS) is not read as a refusal; set net.control_url to a URL the tool can reach)
net-caps
Response size and time are capped
n/a
net-loopback-ssrf was inconclusive: the server never reached the loopback listener, so no loopback URL is known to be fetchable; response size and time caps were not measured
net-redirect
Redirects are re-validated
n/a
the server refused or never reached the loopback listener, so redirect handling could not be observed (a server that blocks loopback cannot be sent a redirect it would follow)

Effects checks

CheckVerdictWhat happened
annotation-honestycritical
Read-only tools change nothing
n/a
no tool declares readOnlyHint: true
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
content_upload_component_preview, content_upload_bg_video, content_upload_site_template_preview, template_get, upload_local_file, upload_local_directory 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
request_accessNo check listed here called it with a valid call.None
check_access_statusNo check listed here called it with a valid call.None
get_auth_statusNo check listed here called it with a valid call.None
logoutNo check listed here called it with a valid call.None
list_workspacesNo check listed here called it with a valid call.
health_checkNo check listed here called it with a valid call.None
get_queue_statsNo check listed here called it with a valid call.None
get_api_infoNo check listed here called it with a valid call.None
content_list_pagesNo check listed here called it with a valid call.None
content_create_pageNo check listed here called it with a valid call.None
content_get_pageNo check listed here called it with a valid call.None
content_export_pageNo check listed here called it with a valid call.None
content_update_pageNo check listed here called it with a valid call.None
content_delete_pageNo check listed here called it with a valid call.None
content_publish_pageNo check listed here called it with a valid call.None
content_unpublish_pageNo check listed here called it with a valid call.None
content_get_page_versionNo check listed here called it with a valid call.None
content_list_postsNo check listed here called it with a valid call.None
content_create_postNo check listed here called it with a valid call.None
content_publish_postNo check listed here called it with a valid call.None
content_preview_postNo check listed here called it with a valid call.None
content_create_docNo check listed here called it with a valid call.None
content_list_docsNo check listed here called it with a valid call.None
content_get_docNo check listed here called it with a valid call.None
content_update_docNo check listed here called it with a valid call.None
content_publish_docNo check listed here called it with a valid call.
content_unpublish_docNo check listed here called it with a valid call.
changelog_listNo check listed here called it with a valid call.
changelog_createNo check listed here called it with a valid call.
changelog_publishNo check listed here called it with a valid call.
changelog_updateNo check listed here called it with a valid call.
changelog_deleteNo check listed here called it with a valid call.
content_delete_docNo check listed here called it with a valid call.
content_export_docNo check listed here called it with a valid call.
content_import_markdownNo check listed here called it with a valid call.
content_import_openapiNo check listed here called it with a valid call.
content_export_markdownNo check listed here called it with a valid call.
content_get_navigationNo check listed here called it with a valid call.
content_update_navigationNo check listed here called it with a valid call.
content_get_settingsNo check listed here called it with a valid call.
content_update_settingsNo check listed here called it with a valid call.
content_list_domainsNo check listed here called it with a valid call.
content_add_domainNo check listed here called it with a valid call.
content_verify_domainNo check listed here called it with a valid call.
content_set_primary_domainNo check listed here called it with a valid call.
content_delete_domainNo check listed here called it with a valid call.
content_get_postNo check listed here called it with a valid call.
content_update_postNo check listed here called it with a valid call.
content_delete_postNo check listed here called it with a valid call.
content_unpublish_postNo check listed here called it with a valid call.
content_update_post_statusNo check listed here called it with a valid call.
content_search_postsNo check listed here called it with a valid call.
content_featured_postsNo check listed here called it with a valid call.
content_list_authorsNo check listed here called it with a valid call.
content_create_authorNo check listed here called it with a valid call.
content_get_authorNo check listed here called it with a valid call.
content_update_authorNo check listed here called it with a valid call.
content_delete_authorNo check listed here called it with a valid call.
content_list_tagsNo check listed here called it with a valid call.
content_create_tagNo check listed here called it with a valid call.
content_update_tagNo check listed here called it with a valid call.
content_delete_tagNo check listed here called it with a valid call.
content_list_categoriesNo check listed here called it with a valid call.
content_create_categoryNo check listed here called it with a valid call.
content_update_categoryNo check listed here called it with a valid call.
content_delete_categoryNo check listed here called it with a valid call.
content_list_componentsNo check listed here called it with a valid call.
content_create_componentNo check listed here called it with a valid call.
content_create_agent_componentNo check listed here called it with a valid call.
content_get_componentNo check listed here called it with a valid call.
content_get_component_by_slugNo check listed here called it with a valid call.
content_update_componentNo check listed here called it with a valid call.
content_delete_componentNo check listed here called it with a valid call.
content_publish_componentNo check listed here called it with a valid call.
content_archive_componentNo check listed here called it with a valid call.
content_get_build_statusNo check listed here called it with a valid call.
content_rebuild_componentNo check listed here called it with a valid call.
content_upload_component_preview
content_upload_bg_video
content_upload_site_template_preview
content_visual_checkNo check listed here called it with a valid call.
collection_listNo check listed here called it with a valid call.
collection_getNo check listed here called it with a valid call.
collection_createNo check listed here called it with a valid call.
collection_updateNo check listed here called it with a valid call.
collection_deleteNo check listed here called it with a valid call.
collection_record_listNo check listed here called it with a valid call.
collection_record_getNo check listed here called it with a valid call.
collection_record_createNo check listed here called it with a valid call.
collection_record_updateNo check listed here called it with a valid call.
collection_record_deleteNo check listed here called it with a valid call.
collection_record_bulkNo check listed here called it with a valid call.
template_get_helpNo check listed here called it with a valid call.
template_inspect_block_fieldsNo check listed here called it with a valid call.
content_get_variablesNo check listed here called it with a valid call.
template_listNo check listed here called it with a valid call.
template_get
template_upsertNo check listed here called it with a valid call.
template_deleteNo check listed here called it with a valid call.
template_list_themesNo check listed here called it with a valid call.
template_apply_themeNo check listed here called it with a valid call.
template_get_configNo check listed here called it with a valid call.
template_update_configNo check listed here called it with a valid call.
template_previewNo check listed here called it with a valid call.
content_deploy_site_previewNo check listed here called it with a valid call.
content_deploy_site_productionNo check listed here called it with a valid call.
content_deploy_siteNo check listed here called it with a valid call.
content_deploy_statusNo check listed here called it with a valid call.
content_deploy_readinessNo check listed here called it with a valid call.
import_from_urlNo check listed here called it with a valid call.
list_filesNo check listed here called it with a valid call.
delete_fileNo check listed here called it with a valid call.
list_videosNo check listed here called it with a valid call.
get_video_statusNo check listed here called it with a valid call.
get_media_statsNo check listed here called it with a valid call.
video_to_scroll_sequenceNo check listed here called it with a valid call.
component_update_and_propagateNo check listed here called it with a valid call.
component_rollbackNo check listed here called it with a valid call.
upload_local_file
upload_local_directory
media_ingest_urlNo check listed here called it with a valid call.
directory_list_categoriesNo check listed here called it with a valid call.
directory_create_categoryNo check listed here called it with a valid call.
directory_get_categoryNo check listed here called it with a valid call.
directory_update_categoryNo check listed here called it with a valid call.
directory_delete_categoryNo check listed here called it with a valid call.
directory_list_listingsNo check listed here called it with a valid call.
directory_upsert_listingNo check listed here called it with a valid call.
directory_bulk_upsert_listingsNo check listed here called it with a valid call.
directory_import_from_idapNo check listed here called it with a valid call.
directory_delete_listingNo check listed here called it with a valid call.
directory_refresh_statsNo check listed here called it with a valid call.
content_get_playbookNo check listed here called it with a valid call.
content_duplicate_pageNo check listed here called it with a valid call.
content_duplicate_blockNo check listed here called it with a valid call.
content_duplicate_postNo check listed here called it with a valid call.
content_duplicate_docNo check listed here called it with a valid call.
content_list_site_templatesNo check listed here called it with a valid call.
content_get_site_templateNo check listed here called it with a valid call.
content_apply_site_templateNo check listed here called it with a valid call.
content_create_site_templateNo check listed here called it with a valid call.
content_update_site_templateNo check listed here called it with a valid call.
content_list_page_templatesNo check listed here called it with a valid call.
content_get_page_templateNo check listed here called it with a valid call.
content_apply_page_templateNo check listed here called it with a valid call.
content_list_marketplace_componentsNo check listed here called it with a valid call.
content_list_marketplace_bg_videosNo check listed here called it with a valid call.
content_get_marketplace_bg_videoNo check listed here called it with a valid call.
page_insert_sectionNo check listed here called it with a valid call.
marketplace_searchNo check listed here called it with a valid call.
list_data_sourcesNo check listed here called it with a valid call.
list_data_source_itemsNo check listed here called it with a valid call.
set_component_kindNo check listed here called it with a valid call.
set_component_agent_metaNo check listed here called it with a valid call.
set_bg_video_agent_metaNo check listed here called it with a valid call.
set_site_template_agent_metaNo check listed here called it with a valid call.
marketplace_suggest_agent_metaNo check listed here called it with a valid call.
marketplace_form_test_submitNo check listed here called it with a valid call.
content_audit_linksNo check listed here called it with a valid call.
list_projectsNo check listed here called it with a valid call.
create_projectNo check listed here called it with a valid call.
agent_flowNo check listed here called it with a valid call.
list_recipesNo check listed here called it with a valid call.
get_recipeNo 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 (1.43.1), the same Sealmark version (1.0.1).

  1. Bv1.43.1Sealmark 1.0.0
  2. Bv1.43.1Sealmark 1.0.1
  3. Bv1.43.1Sealmark 1.0.1

Package facts

License
MIT
Latest release
1.43.1, published 25 Oct 2026 (the version graded on this page)

From npm, 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.43.1, the version graded on this page, with the start command from the test run. For a client that reads an mcpServers JSON file:

{
  "mcpServers": {
    "spideriq-mcp-publish": {
      "command": "npx",
      "args": [
        "-y",
        "@spideriq/mcp-publish@1.43.1"
      ]
    }
  }
}

Or add it to Claude Code:

claude mcp add spideriq-mcp-publish -- npx -y "@spideriq/mcp-publish@1.43.1"

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 @spideriq/mcp-publish@1.43.1"

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 @spideriq/mcp-publish 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.