AI Site Scorer
REMOTE · AI-READINESS.MINGLES.AI · SCANNED AUG 3
Check website AI-readiness: Schema.org, llms.txt, E-E-A-T, robots.txt. Works in Cursor & Claude.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 567 tokens (~113/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · ai-readiness.mingles.ai
claude mcp add --transport http minglesai-ai-site-scorer https://ai-readiness.mingles.ai/api/mcp/
[mcp_servers.minglesai-ai-site-scorer] url = "https://ai-readiness.mingles.ai/api/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"minglesai-ai-site-scorer": {
"type": "remote",
"url": "https://ai-readiness.mingles.ai/api/mcp/",
"enabled": true
}
}
} openclaw mcp add minglesai-ai-site-scorer --url https://ai-readiness.mingles.ai/api/mcp/ --transport streamable-http
mcp_servers:
minglesai-ai-site-scorer:
url: "https://ai-readiness.mingles.ai/api/mcp/" {
"mcpServers": {
"minglesai-ai-site-scorer": {
"type": "http",
"url": "https://ai-readiness.mingles.ai/api/mcp/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 55
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://ai-readiness.mingles.ai/api/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ai-readiness.mingles.ai | CN=YR1,O=Let's Encrypt,C=US | 1 Jul 2026 | 29 Sept 2026 | RSA 4096 | SHA256-RSA | 5fe4e63ce6f4121915ea9b8e425ec64361f |
| SANs: ai-readiness.mingles.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of ai-readiness.mingles.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| mingles.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ai-readiness.mingles.ai/api/mcp/ | Verified | 200 | |
| http (plaintext) | http://ai-readiness.mingles.ai/api/mcp/ | Inconclusive | 404 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
analyze_url ~238
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).
| Name | Type | Req | Description |
|---|---|---|---|
| enhance | boolean | — | If true, automatically run LLM deep analysis after basic analysis completes. Anonymous users: combined $0.006 USDC ($0.001 analyze + $0.005 enhance) charged as a single upfront payment. Default: fals… |
| url | string | yes | The URL to analyze (must include http:// or https://). |
| wait_for_result | boolean | — | If true (default), wait for the analysis to complete and return the full report. If false, return the job_id immediately. |
No output schema declared.
No examples provided.
enhance_report ~68
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).
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The UUID job_id of a completed report. |
No output schema declared.
No examples provided.
generate_fix_prompt ~73
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).
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The UUID job_id of a completed report. |
No output schema declared.
No examples provided.
get_report ~43
Fetch a previously completed analysis report by job ID. Returns scores, check details, and recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The UUID job_id returned by analyze_url. |
No output schema declared.
No examples provided.
list_recent_analyses ~51
List the 10 most recent analyses for the authenticated account. Returns URLs, scores, and statuses.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | Number of results to return (1-50, default 10). |
No output schema declared.
No examples provided.