Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

ai.spideriq/leads

NPM · @SPIDERIQ/MCP-LEADS · SCANNED AUG 3

SpiderIQ Leads: lead-gen MCP (jobs, campaigns, IDAP, Maps, People, Verify, company intel, spiderPR)

Available components

npm · @spideriq/mcp-leads 60
+41 this week 60 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (100 of 104), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (100 of 104), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability57
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 9196 tokens (~180/item across 51 items; 51 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 98% of tool parameters carry a description.Partial
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @spideriq/mcp-leads

# add to Claude Code
claude mcp add ai-spideriq-leads -- npx -y @spideriq/mcp-leads
# add to Codex CLI
codex mcp add ai-spideriq-leads -- npx -y @spideriq/mcp-leads
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-spideriq-leads": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@spideriq/mcp-leads"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-spideriq-leads --command npx --arg -y --arg @spideriq/mcp-leads
# ~/.hermes/config.yaml
mcp_servers:
  ai-spideriq-leads:
    command: "npx"
    args: ["-y", "@spideriq/mcp-leads"]
// mcp.json
{
  "mcpServers": {
    "ai-spideriq-leads": {
      "command": "npx",
      "args": [
        "-y",
        "@spideriq/mcp-leads"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +47
    • Provenance: unverified → fail ▼ security
    • Install scripts: unverified → pass ▲ security
    • Known CVEs: unverified → partial ▲ security
    • Malware scan: unverified → pass ▲ security
    • Tool coverage: 100 → unverified ▼ functional
    • License: unverified → pass ▲ functional
    • Maintenance: unverified → pass ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Stability: unverified → 0.23 ▲ functional
    • Schema quality: unverified → good ▲ functional
    • Dependency health: unverified → partial ▲ functional
    • Licence: MIT functional
  • 1 Aug 26 +13
    • Tool coverage: unverified → 100 ▲ functional
  • 31 Jul 26 −19
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 19

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@spideriq/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 100 packages

100 packages in the resolved dependency tree · 100 deprecated · 29 stale · 1 without a linked repository.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 51 exposed · ~9,196 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
verify_emails ~57

Verify email addresses for deliverability. This is a convenience wrapper for submit_job with type=spiderVerify.

NameTypeReqDescription
emailsarrayyesList of email addresses to verify
workspacestring—Workspace name (default: default)

No output schema declared.

No examples provided.