Hostinger Check Configuration

Immutable Catalog Entry

This descriptor comes from the active versioned Portal catalog.

READhostinger.check_configuration

• Contract tier: agent_ready
• Risk: read
• Catalog version: hostinger-2026.07.12.1
• Descriptor hash: 63b72a5a107f3cc86f71dc241842fbfa1597a8e0f8be1e1f6304502b62ec02d3

Use this tool to inspect whether Portal access and per-request Hostinger configuration are ready without returning credential values. It is part of the Hostinger MCP agent contract. It never returns Portal grants, Hostinger API tokens, request headers, or raw credential values. Prefer the typed endpoint tools for provider work and use the five unprefixed navigation tools for new discovery flows. The result is a compact Hostinger MCP envelope designed for the next agent action. Runtime summary: Check Portal and per-request Hostinger readiness without contacting Hostinger or returning credential values.

Request Body

{
  "jsonrpc": "2.0",
  "id": "hostinger-check-configuration-example",
  "method": "tools/call",
  "params": {
    "name": "hostinger.check_configuration",
    "arguments": {}
  }
}

Arguments Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Output Schema

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "ok",
    "data",
    "error",
    "meta"
  ],
  "properties": {
    "ok": {
      "type": "boolean",
      "description": "True only when the requested Hostinger or local catalog operation succeeded."
    },
    "data": {
      "description": "Normalized result data, or null when the operation failed."
    },
    "meta": {
      "type": "object",
      "description": "Safe endpoint, timing, pagination, rate, catalog, and next-action metadata.",
      "additionalProperties": true
    },
    "error": {
      "description": "Secret-safe structured error details, or null on success."
    }
  },
  "description": "Normalized Hostinger MCP response envelope.",
  "additionalProperties": false
}

Code Examples

cURL

curl -X POST 'https://portal.madpanda3d.com/api/mcp' \
  -H 'Authorization: Bearer mad_live_***' \
  -H 'Content-Type: application/json' \
  -d '{
  "jsonrpc": "2.0",
  "id": "hostinger-check-configuration-example",
  "method": "tools/call",
  "params": {
    "name": "hostinger.check_configuration",
    "arguments": {}
  }
}'

Node.js

const response = await fetch('https://portal.madpanda3d.com/api/mcp', {
  method: 'POST',
  headers: {
    Authorization: 'Bearer mad_live_***',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "jsonrpc": "2.0",
  "id": "hostinger-check-configuration-example",
  "method": "tools/call",
  "params": {
    "name": "hostinger.check_configuration",
    "arguments": {}
  }
}),
});
const data = await response.json();
console.log(data);

Python

import requests

url = 'https://portal.madpanda3d.com/api/mcp'
headers = {
    'Authorization': 'Bearer mad_live_***',
    'Content-Type': 'application/json',
}
payload = {
  "jsonrpc": "2.0",
  "id": "hostinger-check-configuration-example",
  "method": "tools/call",
  "params": {
    "name": "hostinger.check_configuration",
    "arguments": {}
  }
}
response = requests.post(url, headers=headers, json=payload, timeout=60)
print(response.json())

Example Responses

200 Success

{
  "ok": true,
  "message": "Tool hostinger.check_configuration executed successfully.",
  "note": "Response shape varies by MCP tool. Inspect live responses for exact fields."
}

502 Upstream Error

{
  "ok": false,
  "classification": "upstream_http_error",
  "message": "Upstream MCP returned a non-success status."
}