← Registry

Analytics

qomvia.com

An MCP server that scans websites to calculate AI-readiness scores and provides detailed rubric breakdowns with remediation guidance.

1 endpoint3 known toolsFirst detected September 21, 2026Last detected September 21, 2026

ENDPOINT 1

https://qomvia.com/api/mcp

No auth detected

MCP server metadata

Name
Qomvia AI readiness
Version
1.0.0
Capabilities
tools

Known tools 3

get_ai_readiness_score

Return the published AI-readiness score for a website: core score out of 100 (same checks for every site), grade, per-dimension breakdown, separate add-on scores (e.g.

Inferred read-only
scan_website

Measure a website's AI-readiness now and return the score.

Inferred read-only
list_readiness_checks

List the rubric: every pack (core, e-commerce), its dimensions and the individual checks with why each one matters and how to fix it.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.qomvia-ai-readiness]
url = "https://qomvia.com/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "qomvia-ai-readiness": {
      "type": "http",
      "url": "https://qomvia.com/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: qomvia-ai-readiness
Remote MCP URL: https://qomvia.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "qomvia-ai-readiness": {
      "url": "https://qomvia.com/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "qomvia-ai-readiness": {
      "type": "http",
      "url": "https://qomvia.com/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "qomvia-ai-readiness",
  "transport": "streamable-http",
  "url": "https://qomvia.com/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.