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

Results / @spideriq/mcp-leads

@spideriq/mcp-leads

version tested 1.19.1npmtested 2026-11-20Sealmark 1.0.1methodology 0.3-draftSTANDARD run62 tools

Sealmark's automated test of @spideriq/mcp-leads 1.19.1 on 2026-11-20 gave it grade B, its lowest test-area grade (protocol B). Only 1 of 62 tools could be called with default settings, so this grade covers the handshake and tool metadata only. Of its 10 checks, 2 passed, 2 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 1 of 62 tools could be called with default settings, so this grade covers the handshake and tool metadata only.

Grade by test area

B
Protocol3/4 pointsincludes a weak signal, not a security finding

Protocol checks

CheckVerdictWhat happened
protocol
Valid MCP handshake and tool schemas
pass
handshake ok, 62 well-formed tool(s)
Evidence for protocol: 1 line
  1. Probe initialize + tools/list
    Outcome server spideriq-leads 1.19.1 answered; 62 tool(s)
    Decided from the MCP exchange (protocol)
tool-poisoningweak signal
No tool-poisoning indicators in tool metadata
partial
2 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), 106 invalid call(s) accepted, 3 unhandled runtime error(s)
Evidence for robust-input: first 6 of 109 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 114 captured response(s), 106 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 45 of 45 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 30 of 30 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
idap_list_resources 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
submit_jobNo check listed here called it with a valid call.None
get_job_statusNo check listed here called it with a valid call.None
get_job_resultsNo check listed here called it with a valid call.None
list_jobsNo check listed here called it with a valid call.None
cancel_jobNo check listed here called it with a valid call.None
scrape_websiteNo check listed here called it with a valid call.
research_websiteNo check listed here called it with a valid call.
search_google_mapsNo check listed here called it with a valid call.None
verify_emailsNo check listed here called it with a valid call.None
create_videoNo check listed here called it with a valid call.None
search_peopleNo check listed here called it with a valid call.None
capture_landing_pageNo check listed here called it with a valid call.
get_company_dataNo check listed here called it with a valid call.None
submit_vayapinNo check listed here called it with a valid call.None
submit_social_enrichmentNo check listed here called it with a valid call.
pr_submitNo check listed here called it with a valid call.None
pr_get_resultNo check listed here called it with a valid call.None
submit_bulk_lead_sourcingNo check listed here called it with a valid call.
list_bulk_sourcesNo check listed here called it with a valid call.
estimate_bulk_lead_sourcingNo check listed here called it with a valid call.
create_campaignNo check listed here called it with a valid call.
list_campaignsNo check listed here called it with a valid call.
get_campaign_statusNo check listed here called it with a valid call.
stop_campaignNo check listed here called it with a valid call.
continue_campaignNo check listed here called it with a valid call.
update_campaignNo check listed here called it with a valid call.
retry_campaign_locationNo check listed here called it with a valid call.
retry_failed_locationsNo check listed here called it with a valid call.
delete_campaignNo check listed here called it with a valid call.
list_countriesNo check listed here called it with a valid call.
list_regionsNo check listed here called it with a valid call.
list_selectable_unitsNo check listed here called it with a valid call.
idap_fetch_resourceNo check listed here called it with a valid call.
idap_list_resources
idap_write_flagsNo check listed here called it with a valid call.
idap_batch_fetchNo check listed here called it with a valid call.
idap_searchNo check listed here called it with a valid call.
idap_statsNo check listed here called it with a valid call.
idap_resolve_resourceNo check listed here called it with a valid call.
idap_mediaNo check listed here called it with a valid call.
idap_find_duplicatesNo check listed here called it with a valid call.
idap_delete_businessNo check listed here called it with a valid call.
lead_searchNo check listed here called it with a valid call.
company_intel_researchNo check listed here called it with a valid call.
company_intel_batchNo check listed here called it with a valid call.
subscribe_eventsNo check listed here called it with a valid call.
get_event_statusNo check listed here called it with a valid call.
list_bulk_corpus_fieldsNo check listed here called it with a valid call.
list_bulk_corpus_valuesNo check listed here called it with a valid call.
count_bulk_corpus_leadsNo check listed here called it with a valid call.
browse_bulk_corpus_leadsNo check listed here called it with a valid call.
list_bulk_past_runsNo check listed here called it with a valid call.
create_bulk_selectionNo check listed here called it with a valid call.
submit_bulk_internal_sourcingNo 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.19.1), the same Sealmark version (1.0.1).

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

Package facts

License
MIT
Latest release
1.19.1, published 24 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.19.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-leads": {
      "command": "npx",
      "args": [
        "-y",
        "@spideriq/mcp-leads@1.19.1"
      ]
    }
  }
}

Or add it to Claude Code:

claude mcp add spideriq-mcp-leads -- npx -y "@spideriq/mcp-leads@1.19.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-leads@1.19.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-leads 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.