AI Site Scorer MCP Server

by minglesai Your server? Claim it

answering

AI Site Scorer is answering right now. Last checked 2 min ago. It exposes 5 tools.

Check website AI-readiness: Schema.org, llms.txt, E-E-A-T, robots.txt. Works in Cursor & Claude.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 91 days of history · worst day 97%

91 days agonow

98.9%

Uptime 24h

91 of 92 checks

Tools

read from the server

169 ms

Response time

average over 24h

open, no key

Access

streamable-http

AI Site Scorer missed 3 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add ai-site-scorer --transport http https://ai-readiness.mingles.ai/api/mcp/

Settings → Connectors → Add custom connector, then paste this address

https://ai-readiness.mingles.ai/api/mcp/

~/.codex/config.toml

[mcp_servers.ai-site-scorer]
url = "https://ai-readiness.mingles.ai/api/mcp/"

.cursor/mcp.json

{
  "mcpServers": {
    "ai-site-scorer": {
      "url": "https://ai-readiness.mingles.ai/api/mcp/"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "ai-site-scorer": {
      "type": "http",
      "url": "https://ai-readiness.mingles.ai/api/mcp/"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

analyze

analyze_url

Submit a URL for AI-readiness analysis. Checks how well the site is structured for AI/LLM crawling (robots.txt, structured data, page speed, content quality, etc.). Returns scores and recommendations. Set wait_for_result=true to wait for completion (up to 60s). Pricing: Free for registered users (100/mo). Anonymous (x402): $0.001 USDC for analysis only; $0.006 USDC combined when enhance=true ($0.001 analyze + $0.005 enhance, charged as a single upfront payment so only one X-PAYMENT header is needed per request).

enhance

enhance_report

Run LLM deep analysis on a completed report. Returns detailed AI analysis with priority issues and actionable recommendations. Pricing: Free with Pro subscription, or $0.005 USDC via x402 (anonymous or free-tier).

generate

generate_fix_prompt

Generate a Cursor/IDE-ready prompt to fix AI readiness issues found in a report. Returns a comprehensive, actionable developer prompt. Pricing: Free with Pro subscription, or $0.002 USDC via x402 (anonymous or free-tier).

recent

list_recent_analyses

List the 10 most recent analyses for the authenticated account. Returns URLs, scores, and statuses.

report

get_report

Fetch a previously completed analysis report by job ID. Returns scores, check details, and recommendations.

Endpoints

URL	Transport	State	Latency	Checked
https://ai-readiness.mingles.ai/api/mcp/	streamable-http	answering	170 ms	2 min ago

Alternatives to AI Site Scorer

same job, measured the same way

llms.txt Checker - AI Readiness Audit

by apifymcpfactory-droid

Checks llms.txt, AI crawler access in robots.txt, and sitemap - with a 0-100 AI readiness score.

answering

Wake site readiness

by sadri-dridi

How an AI agent sees a public website: robots, llms.txt, sitemap, agent card, scored fixes. Host in.

2 tools answering

Agent-readiness check

by wondaverse

Checks a website for AI agents: robots.txt, llms.txt, MCP, A2A. Ranked fixes, text to paste.

1 tools answering

Agent Ready Website Check

by sadri-dridi

Check whether a website is readable by AI agents: robots, llms.txt, sitemap, HTML. Bounded.

31 tools answering

Scovant Core

by scovant

Passive AI-agent readiness scan of a website: robots, llms.txt, JSON-LD, MCP discovery, security.

1 991 installs/wk local only

Website Tech Stack, SEO & llms.txt Check

by fairquery

Website tech stack, SEO issues, robots.txt AI-bot rules, sitemap and llms.txt in one call.

answering

LanceRoylo

by lanceroylo

AEO scoring, llms.txt audit, and agent-readiness checks for AI agents.

294 installs/wk local only

QueryRev AI Readiness

by queryrev

Checks a site for AI crawler access, robots.txt and llms.txt. Runs locally, no telemetry.

471 installs/wk local only

AI Site Scorer — questions

Answers built from our own checks of this server.

What can AI Site Scorer do?

It exposes 5 tools, read directly from the server on our last check. Among them: analyze_url, enhance_report, generate_fix_prompt, get_report, list_recent_analyses. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is AI Site Scorer working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 92 checks got a reply (98.9%), average response time 169 ms. The bar chart above shows every period we have measured.

Is AI Site Scorer still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect AI Site Scorer?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does AI Site Scorer need an API key?

No. AI Site Scorer completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is AI Site Scorer?

It answers our handshake in 169 ms on average, which is faster than 77% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.