Bring Skip Tracing
to CrewAI
Learn how to connect ProspectX to CrewAI and start using 17 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the ProspectX MCP Server?
Accelerate your real estate investing with an AI agent connected directly to ProspectX. Stop manually switching between lists and skip tracing tools—your agent can automatically find property owner contact info, filter distressed properties, and trigger targeted direct mail campaigns seamlessly.
What you can do
- Filter and search for highly motivated seller leads
- Run instant skip tracing to discover owner phone numbers and emails
- Search properties by address, vacancy status, or type
- Manage and organize direct mail campaign lists
- Track the delivery and response rates of your marketing efforts
How it works
1. Sign in to your ProspectX account 2. Navigate to Settings to generate your developer API key 3. Connect to Vinkius to enable AI-powered real estate prospectingWho is it for?
Designed for real estate investors, wholesalers, and acquisitions teams looking to automate their lead generation and outreach at scale.Built-in capabilities (17)
Verify connectivity
Create a lead
Create a list
Get campaign details
Get dashboard
Get lead details
Get property details
Get list details
List campaigns
List all leads
Filter leads by status
List properties
Filter properties by type
List property lists
Search properties
Skip trace a property
Update a lead
Why CrewAI?
When paired with CrewAI, ProspectX becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call ProspectX tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
ProspectX in CrewAI
ProspectX and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect ProspectX to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for ProspectX in CrewAI
The ProspectX MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 17 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
ProspectX for CrewAI
Every tool call from CrewAI to the ProspectX MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
What is skip tracing?
Skip tracing finds the current phone number, email, and mailing address for property owners, enabling direct outreach to motivated sellers.
Can I search by property type?
Yes, filter properties by type (residential, commercial, vacant, multi-family) to build targeted mailing lists for specific investment strategies.
How are campaigns tracked?
View campaign status, delivery metrics, and response rates for all direct mail campaigns, with a centralized dashboard showing overall lead generation performance.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.