Leviathan Systems MCP server

Add a remote connection

Use https://www.leviathansystems.co/mcp with Streamable HTTP in your client's remote MCP settings. The server is stateless, returns JSON responses and does not assign a session ID or keep a persistent SSE connection. Configuration fields vary by client; this is the endpoint configuration shape:

{
  "mcpServers": {
    "leviathan-public-content": {
      "url": "https://www.leviathansystems.co/mcp"
    }
  }
}

Start with initialize, send notifications/initialized, then use tools/list to discover the live tool schemas. A protocol-capable MCP client handles these messages. Raw HTTP requests must accept both application/json and text/event-stream, and include the negotiated MCP-Protocol-Version on subsequent requests.

Search, read and verify the source

1. Call search_resources with a title query, optional article/service kind and a limit from 1 to 50. Follow next_cursor using the original query.
2. Use the returned catalog ID with read_resource. Native Markdown is returned when available. Otherwise, follow the published canonical HTML link.
3. Call read_company_profile with an optional view of full, services or boundaries. Check service exclusions and source evidence before assessing project fit.

curl https://www.leviathansystems.co/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2025-11-25' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"read_resource","arguments":{"id":"service:rack-and-stack"}}}'

The example shows a read after initialization. Tools return JSON text plus structuredContent. Resource discovery also exposes leviathan://company/profile and leviathan://content/index through resources/list and resources/read.

Recover from a failed call

• An unknown tool name returns a top-level JSON-RPC error with code -32602 and data.code: UNKNOWN_TOOL. Refresh tools/list and choose a supported name.
• Invalid arguments for a known tool return isError: true with a structured code and message. Correct the arguments using the live input schema.
• RESOURCE_NOT_FOUND means the ID is outside the published catalog. Search again. INVALID_QUERY means a cursor or filter needs correction; begin a new search when a content revision changes.
• For HTTP 429, honor Retry-After. For CONTENT_UNAVAILABLE, retry later or read the canonical page. Do not retry unchanged invalid requests in a loop.

Limits and service scope

Request bodies are limited to 32 KiB. The best-effort 300-request budget per 60 seconds is shared by public content handlers on the current server instance. It is not an account allowance or a global service guarantee. Unexpected browser origins are rejected; server clients can connect without an Origin header.

Tools accept published catalog IDs and bounded queries. They cannot retrieve arbitrary URLs, read private drafts, send messages, book appointments, purchase services or approve a project. Physical service scope and customer/OEM/facility responsibilities remain in the company profile.

The server card is experimental discovery metadata. The live protocol remains authoritative for available tools. See the MCP transport specification for client implementation details.