WPVibe (INSANE AI for WP)
I'm trying to use WPVibe to build out my automation for me in FluentCRM and am getting an error. I think this is on the backed of FluentCRM, not with WPVibe.
Thoughts here Shahjahan JewelΒ
βSecurity verification failedβ
Cloudflare Ray ID:a42320c7ee8cfa06-ORD
Thatβs a Cloudflare Ray ID, so Iβd check your Cloudflare Security Events first.
Search for that Ray ID and you should be able to see exactly which request/path was blocked, which security rule triggered it, and why.
If it turns out to be a false positive, you can then create a specific exception for that request/rule rather than broadly whitelisting the whole path.
Jorge de los ReyesΒ My client isn't on Cloudflare, so I'm curious where that would be coming from.
Matthew Steinman WPVibe does use Cloudflare (just verified this now), so it may actually be a block on their side.
Iβm not entirely sure how WPVibe operates behind the scenes, but if the block isnβt coming from your own Cloudflare setup, then itβs likely coming from whichever server or service WPVibe (or your site/app) is trying to connect to.
The Ray ID should help identify exactly where the request is being blocked.
Matthew SteinmanΒ One extra thought after looking a bit deeper into this project...
WPVibe itself seems to rely on a hosted relay through Cloudflare Workers, so thereβs another infrastructure layer involved here.
That alone would make me quite cautious with MCP connections, especially with very new or relatively unknown services (this was released in april).
Youβre not just connecting βa toolβ (depending on the permissions involved, you may effectively be creating a bridge into your site, your business data and potentially your clientsβ data too).
More generally, Iβm not fully convinced by their compliance setup either. Iβve already noticed a few cookie-related practices that I personally wouldnβt be comfortable with from an EU/GDPR perspective, and the whole thing still gives me a bit of a very early-stage / βvibe-codedβ feeling π
So Iβd definitely review where the data is processed, what subprocessors are involved, what gets logged or retained, what permissions the MCP connection actually has, and whether youβre comfortable with that risk before connecting anything sensitive.
That Cloudflare warning may actually have been you dodging a bullet, mate π Sometimes fate works in mysterious ways.
Jorge de los ReyesΒ I'd run away from there... I don't want any third on my site/data/code/nothing.
Jose Luis DuronΒ Absolutely, just saying.
Appreciate the responses guys. Might have to uninstall, as cool as it seems to be..
Matthew Steinman The present is local and, when needed, private.
The exciting part is that you shouldnβt have to choose between privacy and capability.
You can still have powerful AI, automations, tools and connectors while keeping control of your data and infrastructure.
Thatβs where things are heading. Just be careful.