Is the Minglesai Ai Site Scorer MCP server down?

mcp-registry/io.github.minglesai/ai-site-scorer · v1.0.0

As of 2026-10-23 12:18 UTC, the Minglesai Ai Site Scorer MCP server is up with a Glimind reliability score of 65/100 (grade C). Over the last 30 days it answered 98.2% of Glimind's liveness checks. It had 277 outages in 90 days, with a median recovery of 3 minutes.

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

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

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (80/100)

What to fix (4)

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.minglesai%2Fai-site-scorer/fixes

{
  "name": "analyze_url",
  "description": "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 nee",
  "inputSchema": {
    "type": "object",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "description": "The URL to analyze (must include http:// or https://)."
      },
      "enhance": {
        "type": "boolean",
        "default": false,
        "description": "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: false."
      },
      "wait_for_result": {
        "type": "boolean",
        "default": true,
        "description": "If true (default), wait for the analysis to complete and return the full report. If false, return the job_id immediately."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_report",
  "description": "Fetch a previously completed analysis report by job ID. Returns scores, check details, and recommendations.",
  "inputSchema": {
    "type": "object",
    "required": [
      "job_id"
    ],
    "properties": {
      "job_id": {
        "type": "string",
        "description": "The UUID job_id returned by analyze_url."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "list_recent_analyses",
  "description": "List the 10 most recent analyses for the authenticated account. Returns URLs, scores, and statuses.",
  "inputSchema": {
    "type": "object",
    "required": [],
    "properties": {
      "limit": {
        "type": "integer",
        "default": 10,
        "description": "Number of results to return (1-50, default 10)."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.minglesai/ai-site-scorer"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.minglesai/ai-site-scorer"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~721 tokens).
• Tool names are unique and portable across clients.
• No breaking contract changes in 30 days.

Largest tool definitions

• analyze_url ~321 tokens
• generate_fix_prompt ~117 tokens
• enhance_report ~113 tokens
• list_recent_analyses ~87 tokens
• get_report ~83 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.minglesai%2Fai-site-scorer.svg)](https://glimind.com/server/mcp-registry%2Fio.github.minglesai%2Fai-site-scorer?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.minglesai%2Fai-site-scorer?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.minglesai%2Fai-site-scorer.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.minglesai%2Fai-site-scorer.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.minglesai%2Fai-site-scorer?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:b1bffaa99b5dc175…, first seen 2026-10-17, included at leaf 2388 of 52,011. Version history · verify what your client received.

Tools (5)

• analyze_url
• enhance_report
• generate_fix_prompt
• get_report
• list_recent_analyses

Compare: most reliable web servers · most reliable ml servers · most reliable code servers · most reliable knowledge servers · most reliable data servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Minglesai Ai Site Scorer MCP server down right now?

As of 2026-10-23 12:18 UTC, the Minglesai Ai Site Scorer MCP server is up with a Glimind reliability score of 65/100 (grade C). Over the last 30 days it answered 98.2% of Glimind's liveness checks. It had 277 outages in 90 days, with a median recovery of 3 minutes.

How many tools does Minglesai Ai Site Scorer MCP server provide?

Minglesai Ai Site Scorer MCP server advertises 5 tools, including analyze_url, enhance_report, generate_fix_prompt, get_report, list_recent_analyses.

How do I install Minglesai Ai Site Scorer MCP server?

Point your MCP client at this streamable-http endpoint: https://ai-readiness.mingles.ai/api/mcp/

Is the Minglesai Ai Site Scorer MCP server safe to connect to an AI agent?

Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Minglesai Ai Site Scorer MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.