Tools
Contributors
Nine tools, all read-only, grouped by what they cover.
| Tool | Arguments | Page |
|---|---|---|
check_domain_health |
domain |
Domains |
list_domains |
none | Domains |
get_pds_repos |
none | Tophhie Social |
verify_pds_handle_availability |
handle |
Tophhie Social |
get_pds_bsky_heatmap |
year |
Tophhie Social |
get_pds_blob_storage_usage |
none | Tophhie Social |
get_pds_blob_storage_usage_for_did |
did |
Tophhie Social |
check_api_health |
none | Platform |
fetch_tophhie_cloud_policies |
none | Platform |
Listing them yourself
Section titled “Listing them yourself”This page can go stale; the server cannot. Ask it directly:
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"}'The response includes each tool’s name, title, description and JSON Schema, which is exactly what a connected assistant sees.
What they return
Section titled “What they return”Every tool returns text content rather than structured JSON. That is normal for MCP: the result is meant to be read by a model, so it comes back as a readable string rather than something you would parse.
If you want parseable output, call the Tophhie Cloud API directly. The MCP server is a wrapper over it, and the API returns JSON.

