# Leviathan Systems Public Content (remote · www.leviathansystems.co)

Search Leviathan Systems articles and services; read public documents and company scope.

- Trust score: 75/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.leviathansystems.co`: 75/100 (this document), [markdown](https://verifymcp.io/servers/co-leviathansystems-public-content/www.md), [page](https://verifymcp.io/servers/co-leviathansystems-public-content/www)

## Channel facts

- Endpoint: `https://www.leviathansystems.co/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 42/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 295 tokens (~59/item across 5 items; 3 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Leviathan Systems Public Content MCP server?

Leviathan Systems Public Content is a hosted endpoint at https://www.leviathansystems.co/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http co-leviathansystems-public-content 'https://www.leviathansystems.co/mcp'
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "co-leviathansystems-public-content": {
      "type": "http",
      "url": "https://www.leviathansystems.co/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-leviathansystems-public-content]
url = "https://www.leviathansystems.co/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-leviathansystems-public-content": {
      "type": "remote",
      "url": "https://www.leviathansystems.co/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-leviathansystems-public-content --url 'https://www.leviathansystems.co/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-leviathansystems-public-content:
    url: "https://www.leviathansystems.co/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-leviathansystems-public-content": {
      "Transport": "http",
      "Url": "https://www.leviathansystems.co/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-leviathansystems-public-content -t streamable-http -u 'https://www.leviathansystems.co/mcp'
```

### Other

```json
{
  "mcpServers": {
    "co-leviathansystems-public-content": {
      "type": "http",
      "url": "https://www.leviathansystems.co/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 69, +44)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.07
- [functional improvement] Schema quality: unverified → 0
- [functional improvement] MCP protocol: unverified → pass

### 2026-10-22 (score 25, −43)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Schema quality: 0 → unverified
- [functional regression] Tool coverage: 100 → unverified

## MCP tools (3)

### `search_resources` (~114 tokens)

Search published resources

Find published article titles and physical service listings. Matches every query word in the title. Follow next_cursor with the same query and kind to read more.

Input parameters:

- `cursor` (string): An opaque next_cursor from the same query and content revision.
- `kind` (string): Restrict the catalog to educational articles or physical services.
- `limit` (integer): Maximum records in this page, from 1 to 50; default 20.
- `q` (string): Words to match in published titles; every word must match.

### `read_resource` (~63 tokens)

Read a published resource

Read a resource returned by search_resources. Returns native Markdown when available, or the canonical HTML link for preserved legacy articles. Accepts catalog IDs, never arbitrary URLs or file paths.

Input parameters:

- `id` (string, required): Exact published catalog ID, for example service:rack-and-stack.

### `read_company_profile` (~61 tokens)

Read company profile and service boundaries

Read Leviathan Systems' public company identity, physical service scope, exclusions and contact guidance. Select a smaller view when only services or scope boundaries are needed.

Input parameters:

- `view` (string): Return the full public profile (default), service listings, or responsibility boundaries.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-leviathansystems-public-content/www#diagnostics

## Score history

- 2026-11-05: 75
- 2026-11-04: 74
- 2026-11-03: 74
- 2026-11-02: 73
- 2026-11-01: 73
- 2026-10-31: 72
- 2026-10-30: 72
- 2026-10-29: 71
- 2026-10-28: 71
- 2026-10-27: 70
- 2026-10-26: 70
- 2026-10-25: 69
- 2026-10-24: 69
- 2026-10-23: 69
- 2026-10-22: 25
- 2026-10-21: 68

## Common questions

### What is the Leviathan Systems Public Content MCP server?

Leviathan Systems Public Content is an MCP server listed in the public MCP registry as co.leviathansystems/public-content. Search Leviathan Systems articles and services; read public documents and company scope. This page covers its hosted endpoint (https://www.leviathansystems.co/mcp).

### Is the Leviathan Systems Public Content MCP server safe to use?

Leviathan Systems Public Content scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Leviathan Systems Public Content MCP server expose?

Leviathan Systems Public Content exposes 3 tools: search_resources, read_resource, read_company_profile. Their descriptions and schemas cost roughly 238 tokens of context every time the server is loaded.

### Does the Leviathan Systems Public Content MCP server require authentication?

No. We connected to Leviathan Systems Public Content without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Leviathan Systems Public Content MCP server still maintained?

Leviathan Systems Public Content is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.leviathansystems.co/mcp
- Website: https://www.leviathansystems.co/developers/mcp
- Changelog RSS feed: https://verifymcp.io/servers/co-leviathansystems-public-content/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-leviathansystems-public-content/www.json
- HTML version of this page: https://verifymcp.io/servers/co-leviathansystems-public-content/www