✓ Watched since 2026-06-03 — behavioral baseline locked. We re-check this server's tool surface on a schedule; if it adds, removes, or silently rewrites a tool (rug-pull), we record it.
What it offers — 5 tools · Developer Tools
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 q
enhance_report
Run LLM deep analysis on a completed report. Returns detailed AI analysis with priority issues and actionable recommendations. Pricing: Free with Pro
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 w
get_report
Fetch a previously completed analysis report by job ID. Returns scores, check details, and recommendations.
list_recent_analyses
List the 10 most recent analyses for the authenticated account. Returns URLs, scores, and statuses.
Spec conformance20%100
✓ initialize → protocolVersion 2024-11-05
✓ initialize HTTP 200
✓ unknown method → -32601
✓ tools/list → 5 tools
✓ every tool has name + inputSchema
Security (OWASP MCP)30%100
5 tools scanned
no injection markup
no secret-path refs
Reliability / performance20%84
single-probe latency 738ms (PRELIMINARY — continuous uptime/p95 from proxy telemetry lands in v2)
Tool hygiene15%80
100% of tools have typed inputSchema
0/5 declare outputSchema
no unannotated destructive tools
Transparency / provenance15%90
HTTPS ✓
RFC 9728 oauth-protected-resource metadata ✓
advertises protocol 2024-11-05
Observed behavior
No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.
Findings
No blocking issues found in the static + spec checks.
We re-grade ai-readiness.mingles.ai on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.
Share this report card
A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.
A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.
Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:
https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.