Compatible with every major AI agent and IDE
What is the ChangeDetection.io MCP Server?
Connect your ChangeDetection.io instance to any AI agent to automate web monitoring and data extraction through natural conversation.
What you can do
- Watch Management — Create, update, and delete monitors for any URL to track content changes
- Snapshot Analysis — Retrieve historical snapshots and compare differences (diffs) to see exactly what changed
- Tagging & Organization — Categorize your watches with tags to manage large-scale monitoring projects
- Instant Rechecks — Trigger immediate checks for specific watches to get the most up-to-date information
- History Tracking — Access the full history of a watch to analyze trends and previous versions of a page
How it works
- Subscribe to this server
- Enter your ChangeDetection.io Instance URL and API Key
- Start monitoring the web from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Data Analysts — track price changes, availability, or content updates across multiple competitors automatically
- Developers — monitor API documentation or website changes to stay ahead of breaking updates
- SEO Specialists — keep an eye on SERP changes or competitor landing page modifications
Built-in capabilities (14)
Create a new tag
Create a new watch
Delete a watch
Use "latest" for the most recent check. Get single snapshot
Use "previous" and "latest" as keywords. Get snapshot difference (diff)
Get single tag
Get single watch
Get watch favicon
Get watch history
io. Import API
List all tags
List all watches
Search API
Update an existing watch
Why CrewAI?
When paired with CrewAI, ChangeDetection.io becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call ChangeDetection.io 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
ChangeDetection.io in CrewAI
ChangeDetection.io and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect ChangeDetection.io 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 | 4,000+ 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 ChangeDetection.io in CrewAI
The ChangeDetection.io 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 14 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
ChangeDetection.io for CrewAI
Every tool call from CrewAI to the ChangeDetection.io MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see exactly what text changed on a page between the last two checks?
Yes! Use the get_snapshot_diff tool with the watch UUID. It will return the specific differences between the current state and the previous snapshot.
How do I trigger an immediate recheck of a specific website?
You can use the get_watch tool and set the recheck parameter to '1'. This forces the server to fetch the latest version of the page immediately.
Can I filter my monitors by tags using the AI?
Absolutely. When using list_watches, you can provide a tag name to filter the results and only see monitors associated with that specific category.
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.
Explore More MCP Servers
View all →
Hyprace F1 Data
12 toolsQuery Formula 1 race results, driver standings, constructor rankings, and historical data since 1950 from any AI agent.

Criteo Retail Media API
10 toolsEquip your AI agent to manage Criteo retail campaigns, line items, and product data directly via the Criteo API.

Invoice Ninja
11 toolsManage clients, invoices, and products directly through AI.

Tango
12 toolsDocument any process by recording your screen clicks and turning them into step-by-step guides with annotated screenshots.
