Skip to content

MCP Server

Contributors

The Tophhie Cloud MCP Server lets an AI assistant query Tophhie Cloud directly. Connect it to Claude, or any other client that speaks Model Context Protocol, and the assistant can check a domain’s mail security, look up Tophhie Social statistics, or read the platform policies without you copying anything into the conversation.

Endpoint https://mcp.tophhie.cloud/mcp
Transport Streamable HTTP, stateless
Authentication None
Tools 9, all read-only
Repository Tophhie/tophhie-cloud-mcp-cf
Area Tools
Domains Run a full DNS and mail security health check, or list Tophhie Cloud domains
Tophhie Social Repositories, handle availability, posting heatmap, blob storage usage
Platform API health and the Tophhie Cloud policy list

There is no authentication. Anyone who knows the endpoint can call it.

That is a deliberate choice rather than an oversight. Every tool is read-only, and each one is a thin wrapper over an endpoint the Tophhie Cloud API already serves publicly and without a key. The MCP server does not expose anything that was not already available at api.tophhie.cloud; it just makes it reachable by an assistant.

Nothing here can change anything, and no tool accepts credentials. Do not send one any.

The endpoint is plain JSON-RPC over HTTP, so curl is enough to see what it offers:

Terminal window
curl -sS -X POST https://mcp.tophhie.cloud/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Calling a tool is the same shape:

Terminal window
curl -sS -X POST https://mcp.tophhie.cloud/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call",
"params":{"name":"check_api_health","arguments":{}}}'
{"result":{"content":[{"type":"text","text":"API Health Status: ok"}]},"jsonrpc":"2.0","id":2}