aivis-mcp
Related Servers
Alternatives to aivis-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to run live SEO/readiness audits against 50+ AI crawlers, validate schema and robots.txt, and generate llms.txt, robots.txt, and JSON-LD files directly from MCP-compatible clients like Claude Desktop and Cursor.8728 npmMIT
- AlicenseBqualityCmaintenanceEnables MCP clients to audit AI search visibility, generate intent-aligned social content, and assess Agentic Commerce Readiness with remediation files.3MIT
- AlicenseBqualityAmaintenanceMCP server for auditing product pages to determine AI shopping agent readiness, providing a 0–100 score and actionable fixes.115Apache 2.0
- AlicenseAqualityCmaintenanceEnables inspection of any website's AI-search readiness, checking AI crawler blocks, llms.txt, schema markup, and indexing directives from MCP clients like Claude.434 npmMIT
- AlicenseAqualityDmaintenanceAn 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.537 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to check whether a public website is crawlable, understandable, and ready for AI search workflows through local-only audits of robots.txt, sitemaps, metadata, and llms.txt.350 npm1MIT
TDQS
Scored across 2 tools
The two tools target completely different activities: one performs a technical visibility audit (robots.txt, raw HTML, agent-commerce layer), while the other generates prompts and a rubric for recommendation testing. Their descriptions make the distinction unambiguous, so an agent can easily pick the right tool.
Both tool names follow a clear verb_noun pattern in snake_case (check_ai_visibility, build_recommendation_test). The naming is consistent and predictable, with no deviations in style or convention.
The server has only 2 tools, which feels thin even for a focused audit service. While each tool is substantive, the surface lacks depth—for example, no tool to run or score the recommendation test, or to track changes over time—making the set borderline.
The tools cover the core diagnostic tasks: technical AI visibility checks and prompt generation for recommendation testing. There are minor gaps, such as no tool to apply the generated rubric or to store historical results, but these can be worked around by the calling assistant or user.