viraill-mcp
Related Servers
Alternatives to viraill-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to run brand-visibility audits by querying multiple AI engines, generating competitive leaderboards, and identifying growth opportunities. Integrates with any MCP-capable client to measure and act on brand discoverability in AI recommendations.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to check whether AI assistants recommend a brand and audit a site's AI-agent readiness, providing visibility scores and specific gaps.MIT
- AlicenseBqualityAmaintenanceMCP server for auditing product pages to determine AI shopping agent readiness, providing a 0–100 score and actionable fixes.115Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to perform bounded website Quick Audits via MCP tools, covering crawlability, indexability, and metadata.MIT
- AlicenseAqualityBmaintenanceAn MCP server that gives AI agents tools to inspect a website's visibility to AI answer engines, including crawler permissions, llms.txt, structured data, on-page signals, and a full 29-check AI-readiness audit.521 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI-powered LinkedIn content creation, profile and company analytics, lead generation, and connection request automation through MCP tools.-
TDQS
Scored across 3 tools
The three tools are clearly distinct: geo_audit analyzes generative search visibility, geo_social_generate creates social content, and agentic_scan measures agentic commerce readiness. There is no functional overlap, and each tool targets a unique domain with clear descriptions.
The naming pattern is inconsistent. Two tools share the 'geo_' prefix but use different verb structures (audit vs. generate), while the third uses 'agentic_' with a different verb. The mixing of prefixes and verb placements disrupts a predictable convention.
Three tools is a reasonable, focused count for a server dedicated to GEO and agentic commerce. It avoids bloat and covers core auditing and generation tasks, though it borders on the lower end of the ideal range.
The server covers the primary workflows: auditing generative search visibility, creating social content to build citations, and assessing agentic commerce readiness. Minor gaps exist (e.g., no monitoring or content update tools), but the core lifecycle is well represented for its scope.