SpiderIQ Leads MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to SpiderLeads enrichment and lead campaigns: Do tenant resolution and campaign authority remain visible before contact-data enrichment or outreach?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Lead generation, enrichment, company intelligence, events and campaign workflows under explicit tenant selection.

What we know

Focused SpiderIQ lead-gen slice covering jobs/campaigns, IDAP, maps, people, email verification, company intelligence and event data. Tenancy selection is explicit and refuses to guess when multiple workspaces exist.

Maintenance / activity evidence

@spideriq/mcp-leads 1.16.0 published 2026-09-04T12:25:41.144Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Lead-data read/enrichment plus campaign/job mutations. Writes: Create/update lead/campaign/job state where exposed.
SpiderIQ credential.
Sensitive access: Personal/business contact data, Workspace/client data

Lead data is sensitive and campaign mutations can create external business actions; tenant scoping matters.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do tenant resolution and campaign authority remain visible before contact-data enrichment or outreach?

The bounded review of the publisher's documented SpiderLeads enrichment and lead campaigns and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Lead data is sensitive and campaign mutations can create external business actions; tenant scoping matters.
Lead-data read/enrichment plus campaign/job mutations.
SpiderIQ credential.
People/company/contact data is processed by SpiderIQ/upstream enrichment sources.
Reviewed write actions: Create/update lead/campaign/job state where exposed
Sensitive access: Personal/business contact data, Workspace/client data
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Some actions write campaign/job state and may involve outreach workflows.
Workspace ambiguity is refused rather than silently choosing a tenant.
Lead/contact data can be personal/business-sensitive.
Exact individual write tools vary with package version.

Original activity observations

@spideriq/mcp-leads 1.16.0 published 2026-09-04T12:25:41.144Z

Technical identity

npm/@spideriq/mcp-leads

Exact implementation source: https://www.npmjs.com/package/@spideriq/mcp-leads ↗
Reviewed resource type: MCP Server
Repository identity: SpiderIQ/SpiderIQ
Package identity: npm:@spideriq/mcp-leads

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@spideriq/mcp-leads
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

No third-party MCP installation, execution, connection, payment or mutation performed.
Official documentation may not prove currently operational service.
Package installation is not client connection; verify tenant before writes.
Targeted 2026-10-13 re-research: Publisher requires private https://npm.spideriq.ai registry; access/tenant credentials and pinned version required.
Publisher requires private https://npm.spideriq.ai registry; access/tenant credentials and pinned version required.
Batch08 V3 source-specific finding: Uses separate https://npm.spideriq.ai registry and pinned 1.19.0.
Private npm registry; installation not equivalent to authenticated tenant MCP registration.
Source is publisher npm README static inspection; no third-party runtime test. For installation-only commands, client registration is separate.

Install / connect
Publisher instructions
Private registry install with tenant/project authentication.
publisher documented step or launch · Publisher instructions
npm install @spideriq/mcp-leads@1.19.0 --registry https://npm.spideriq.ai
Configure / authenticate
MCP100 setup guide
SpiderIQ Leads publisher uses its own npm registry https://npm.spideriq.ai and version pins. Avoid unverified registry fallback or unpinned global installs.
Check connection
Suggested check
User-side suggested check (not executed): inspect registered tools/connection and perform publisher-supported read-only status/list operations. Do not send, purchase, publish, delete, sign, trade or alter data as a smoke test.
Remove / uninstall / revoke
MCP100 setup guide
Generic client guidance (not publisher-specific uninstall): unregister MCP entry in the chosen client. If installed globally, remove the npm package separately. Revoke provider access separately through account controls, where supported. This does not erase local data or revoke funds/credentials automatically.
Unregister the named MCP entry from the actual host separately from removing a global npm install; no claim that either revokes remote credentials.
Remove local stored keys/tokens and revoke or rotate corresponding provider authorization using documented provider account controls if available; exact procedure not verified for this package. Wallet private keys cannot be revoked.

Official Documentation & Sources

What it does

Focused SpiderIQ lead-gen slice covering jobs/campaigns, IDAP, maps, people, email verification, company intelligence and event data. Tenancy selection is explicit and refuses to guess when multiple workspaces exist.

Capability: Data & Databases
Resource type: MCP Server
Industry: Media & Marketing, Professional Services
Best fit: Lead generation, enrichment, company intelligence, events and campaign workflows under explicit tenant selection.

Representative uses

Search/enrich people/companies
Run Maps/company intelligence workflows
Verify contact data
Operate lead campaigns/jobs
Drive multiple client workspaces per call

Limitations

Some actions write campaign/job state and may involve outreach workflows.
Workspace ambiguity is refused rather than silently choosing a tenant.
Lead/contact data can be personal/business-sensitive.
Exact individual write tools vary with package version.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: SpiderIQ credential.
Permissions: Lead-data read/enrichment plus campaign/job mutations.
Data handling: People/company/contact data is processed by SpiderIQ/upstream enrichment sources.
Cost: plan_based
Risk and cautions: Lead data is sensitive and campaign mutations can create external business actions; tenant scoping matters.

Access scope and cautions

Write actions: Create/update lead/campaign/job state where exposed
Sensitive access: Personal/business contact data Workspace/client data
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Search/enrich people/companies; Run Maps/company intelligence workflows; Verify contact data; Operate lead campaigns/jobs; Drive multiple client workspaces per call.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @spideriq/mcp-leads. Recorded transport: stdio. Recorded environment-variable notes: SPIDERIQ_WORKSPACE; SPIDERIQ_WORKSPACE_CWD (optional); npm_config_registry=https://npm.spideriq.ai. No configuration values are supplied here. Prerequisites: SpiderIQ workspace. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: SpiderIQ workspace/PAT credential.

Can it modify data or perform write operations?

Documented write actions include: Create/update lead/campaign/job state where exposed. Recorded permission boundary: Lead-data read/enrichment plus campaign/job mutations.

What data-handling boundary should I consider?

People/company/contact data is processed by SpiderIQ/upstream enrichment sources. Recorded sensitive-access context: Personal/business contact data; Workspace/client data.

What limitations and risks should I check before use?

Lead data is sensitive and campaign mutations can create external business actions; tenant scoping matters. Some actions write campaign/job state and may involve outreach workflows. Workspace ambiguity is refused rather than silently choosing a tenant. Lead/contact data can be personal/business-sensitive. Exact individual write tools vary with package version. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is plan based. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.