4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
ChangeDetection.io MCP Server

Bring Web Monitoring
to CrewAI

Learn how to connect ChangeDetection.io to CrewAI and start using 14 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Create TagCreate WatchDelete WatchGet SnapshotGet Snapshot DiffGet TagGet WatchGet Watch FaviconGet Watch HistoryImport UrlsList TagsList WatchesSearch WatchesUpdate Watch

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
ChangeDetection.io

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

  1. Subscribe to this server
  2. Enter your ChangeDetection.io Instance URL and API Key
  3. 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_tag

Create a new tag

create_watch

Create a new watch

delete_watch

Delete a watch

get_snapshot

Use "latest" for the most recent check. Get single snapshot

get_snapshot_diff

Use "previous" and "latest" as keywords. Get snapshot difference (diff)

get_tag

Get single tag

get_watch

Get single watch

get_watch_favicon

Get watch favicon

get_watch_history

Get watch history

import_urls

io. Import API

list_tags

List all tags

list_watches

List all watches

search_watches

Search API

update_watch

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 mcps parameter 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

See it in action

ChangeDetection.io in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

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.

ChangeDetection.io
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

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.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

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.

05

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.

06

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.

07

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.

08

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.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

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 →