AI & Machine Learning
solai.es
Runs SolAI's AI-readiness audit on public websites and provides information about SolAI's AI audit, automation, and agent services.
ENDPOINT 1
https://solai.es/api/mcp
MCP server metadata
- Name
- solai
- Version
- 1.0.0
SolAI is an AI consultancy in Marbella (Costa del Sol, Spain) that designs and deploys AI audits, automations and AI agents for businesses. This server is stateless and needs no authentication. Tool check_ai_readiness(url) runs SolAI's free deterministic AI-readiness check on any public website and returns a 0-100 score, about 20 per-check results grouped as search visibility, AI readability, agent access, contact channels and trust, plus plain-language findings. It makes real HTTP requests to the target site, takes 2 to 15 seconds and is rate limited per IP per day. Tool about_solai() returns what SolAI does and how to contact the team. Resources: solai://about (plain-text company facts) and solai://llms.txt. The full analysis with business-specific recommendations is only available on https://solai.es.
Known tools 2
check_ai_readinessRuns SolAI's free AI-readiness check on a public website: fetches it the way an AI agent without a browser would and runs about 20 deterministic checks in five groups: search visibility (reachable, https, indexable, title and description, canonical, sitemap, robots.txt, mobile, headings, languages), AI readability (readable text without JavaScript, schema.org structured data, Open Graph, AI crawlers allowed in robots.txt, llms.txt), agent access (MCP endpoint, agent manifests, machine-readable prices), contact channels (email/phone/WhatsApp/form, online booking, chat widget) and trust (legal pages, security headers).
Potential side effectsabout_solaiWhat SolAI does (AI audits, automations, AI agents, deployment and support for businesses on the Costa del Sol), where the team is based (Marbella), which languages it works in (Spanish, English) and how to get in touch.
Inferred read-onlyCONNECT 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.solai]
url = "https://solai.es/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"solai": {
"type": "http",
"url": "https://solai.es/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: solai
Remote MCP URL: https://solai.es/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": {
"solai": {
"url": "https://solai.es/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"solai": {
"type": "http",
"url": "https://solai.es/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "solai",
"transport": "streamable-http",
"url": "https://solai.es/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.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.