
Leads
ai.spideriqPublished by spideriq.aiv1.9.0Updated Oct 24, 2026
SpiderIQ Leads: lead-gen MCP (jobs, campaigns, IDAP, Maps, People, Verify, company intel, spiderPR)
Overview
SpiderIQ Leads is a local stdio MCP server for lead generation, covering jobs, campaigns, IDAP, Maps, People, verification, company intel and spiderPR.
- What you can do
- The registry lists no individual tools, so capabilities are known only from its one-line description.
- It is presented as a lead-generation server, suggesting the assistant can work with prospect and company data.
- Named areas include jobs, campaigns, Maps, People, verification and company intelligence.
- It also mentions IDAP and spiderPR, whose functions are not explained in the available material.
- When to use it
- Consider it if you want an assistant to help with lead generation and prospect research, such as finding people or companies, running campaigns, or verifying contact data. The sparse documentation means you should confirm the actual tool list before relying on it.
- Requirements
- Runs as a local process over stdio, installed from the npm package @spideriq/mcp-leads, so Node.js and npm are needed. The manifest declares no authentication, environment variables or headers, but the server's data sources are not documented, so account or key requirements may be missing from the listing. Desktop client only.
Installation
In SourceWeft
- Open Leads in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.9.0LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.