visiblyai-mcp-server
Provides an MCP server that exposes VisiblyAI SEO tools to Claude Code, including local/free SEO helper tools and paid API-powered analysis tools (credits-based), plus tools that can query connected Google Search Console/GA4 data via the VisiblyAI platform.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
README indicates Bearer token usage over HTTP and API key via environment variable for local stdio mode. It does not document TLS guarantees beyond typical HTTPS usage, rate-limit behavior, or how errors/logs handle secrets. Dependency list is minimal but does not provide vulnerability/CVE status.
⚡ Reliability
Best When
Used from Claude Code via MCP to perform SEO research, validation, and audits interactively with a mix of free local tools and credit-consuming remote/API tools.
Avoid When
Avoid for workflows that cannot tolerate missing details on error codes, rate limits, or data-handling guarantees—especially for paid API calls and Google-connected queries.
Use Cases
- • Classify keyword intent and funnel stage for SEO planning
- • Generate SEO checklists and best-practice guidance
- • Run URL structure checks and perform on-page SEO audits
- • Validate structured data, hreflang, sitemaps, and discover broken links
- • Analyze traffic, competitors, backlinks, SERPs, and PageSpeed/Core Web Vitals
- • Query connected GSC/GA4 properties for performance by query/page/country/device
Not For
- • Teams needing a documented public REST/GraphQL/SDK interface outside of MCP
- • Use cases requiring strict on-prem/no-external-network operation for all features
- • Applications that need guaranteed, published uptime/SLA
Interface
Authentication
Paid tools require VISIBLYAI_API_KEY. Some tools use the user's Google OAuth connections managed via the VisiblyAI platform; README does not describe OAuth scopes explicitly.
Pricing
Paid tools are described as requiring an API key and using credits; Google-connected tools are described as requiring an API key but 0 credits.
Agent Metadata
Known Gotchas
- ⚠ Some tools require an API key and will fail or be limited when VISIBLYAI_API_KEY is missing/insufficient.
- ⚠ Paid tools consume credits; agents should avoid unbounded repeated calls (e.g., crawls/workflows) without cost awareness.
- ⚠ Google-connected tools rely on user-managed connections via VisiblyAI; availability depends on proper OAuth connection setup.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for visiblyai-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.