Home / MCP registry index / ai.hostingfor/hosting
HostingFor.AI
ai.hostingfor/hosting in the official MCP registry.
Endpoint https://hostingfor.ai/mcp.
The registry describes it as: Publish and manage websites on HostingFor.AI: files, DNS, MySQL, SSL and site checks.
On 2026-10-22 this server asked for credentials before it would list its tools, so we could not read them. Nothing was checked: this is not a clean result.
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-hostingfor-hosting)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
| MariaDB Documentation com.mariadb/mariadb-docs | 3 tools, nothing matched 2026-10-22 |
| ai.getvda/elasticsearch-redis-mysql-stack-generator ai.getvda/elasticsearch-redis-mysql-stack-generator | 2 tools, nothing matched 2026-10-21 |
| ai.getvda/mysql-redis-compose-generator ai.getvda/mysql-redis-compose-generator | 2 tools, nothing matched 2026-10-21 |
| ai.getvda/mysql-redis-compose-generator-adminer ai.getvda/mysql-redis-compose-generator-adminer | 2 tools, nothing matched 2026-10-21 |
| ai.getvda/mysql-redis-compose-generator-nginx ai.getvda/mysql-redis-compose-generator-nginx | 2 tools, nothing matched 2026-10-21 |
| ai.getvda/nats-mysql-redis-stack-generator ai.getvda/nats-mysql-redis-stack-generator | 2 tools, nothing matched 2026-10-21 |