Bring Website Auditing
to CrewAI
Learn how to connect Geekflare to CrewAI and start using 7 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Geekflare MCP Server?
Connect your Geekflare account to any AI agent and simplify how you monitor website performance, secure your domains, and analyze SEO health through natural conversation.
What you can do
- Audit & SEO — Run full Google Lighthouse audits to measure speed, accessibility, and search engine optimization.
- Performance Testing — Measure server response times (TTFB) and overall page load speed to identify bottlenecks.
- Security Scanning — Analyze SSL/TLS certificates for validity and security vulnerabilities in real-time.
- Network Intelligence — Retrieve DNS records (A, MX, CNAME, TXT) and Whois registration data for any domain.
- Link Oversight — Automatically identify broken links (404s) on any page to improve user experience.
- Visual Monitoring — Capture full-page screenshots of target URLs programmatically via AI.
- Operational Visibility — Verify API health and monitor your digital infrastructure directly from the agent.
How it works
1. Subscribe to this server
2. Enter your Geekflare API Key (found in your account dashboard)
3. Start auditing your web presence from Claude, Cursor, or any MCP client
Who is this for?
- Web Developers & DevOps — quickly check SSL status and measure page speed via simple AI commands.
- SEO Specialists — run Lighthouse audits and identify broken links directly from the workspace.
- IT Managers — verify DNS records and monitor domain ownership details via the AI assistant.
Built-in capabilities (7)
Identify broken links on a page
Retrieve DNS records
Retrieve Whois information
Measure page speed and TTFB
Run Lighthouse SEO/Performance audit
Scan SSL/TLS certificate
Capture a website screenshot
Why CrewAI?
When paired with CrewAI, Geekflare becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Geekflare 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
Geekflare in CrewAI
Geekflare and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Geekflare 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 Geekflare in CrewAI
The Geekflare 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 7 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
Geekflare for CrewAI
Every tool call from CrewAI to the Geekflare MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I run a full Lighthouse SEO audit via AI?
Yes! Use the run_lighthouse_audit tool and provide the target URL. Your agent will return scores for Performance, SEO, Accessibility, and Best Practices.
How do I check if my SSL certificate is valid using the agent?
Use the scan_ssl_tls_cert tool. Provide the domain name, and Geekflare will verify the issuer, expiration date, and security protocols used by your site.
Is it possible to see the DNS records for a domain via AI?
Absolutely. Use the get_dns_records query. Provide the URL, and the agent will retrieve A, MX, CNAME, and TXT records registered for that domain.
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.