# Merlonix Monitoring (remote · api.merlonix.com)

Monitoring for agencies — uptime, SSL, DNS, AI visibility, MCP health. 6 public tools, no auth.

- Trust score: 60/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.merlonix.com`: 60/100 (this document), [markdown](https://verifymcp.io/servers/com-merlonix-monitoring/api.md), [page](https://verifymcp.io/servers/com-merlonix-monitoring/api)

## Channel facts

- Endpoint: `https://api.merlonix.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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-08-03.

- **Endpoint Security**: 54/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_asset).
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1372 tokens (~98/item across 14 items; 14 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add --transport http com-merlonix-monitoring https://api.merlonix.com/mcp
```

### Codex

```toml
[mcp_servers.com-merlonix-monitoring]
url = "https://api.merlonix.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-merlonix-monitoring": {
      "type": "remote",
      "url": "https://api.merlonix.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-merlonix-monitoring --url https://api.merlonix.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-merlonix-monitoring:
    url: "https://api.merlonix.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-merlonix-monitoring": {
      "type": "http",
      "url": "https://api.merlonix.com/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-08-03 (score 60)

First indexed and scored.

## MCP tools (14)

### `check_domain_health` (~74 tokens)

Check the live SSL/TLS certificate (validity + expiry + issuer), DNS records (A/AAAA/MX/NS resolution), and domain-registration (RDAP) expiry of any public hostname. Each leg fails soft and is reported independently.

Input parameters:

- `hostname` (string, required): A public hostname, e.g. example.com

### `check_agent_readiness` (~77 tokens)

Score how ready a website is for AI agents and answer engines. Fetches /llms.txt, /robots.txt, and the homepage and returns a letter grade with per-signal findings. No browser rendering or LLM call — deterministic HTTP/parse.

Input parameters:

- `hostname` (string, required): A public hostname, e.g. example.com

### `check_mcp_health` (~113 tokens)

Health-check a live MCP (Model Context Protocol) server by URL: performs a real JSON-RPC initialize handshake, then tools/list, and returns whether it is up/degraded/down, its protocol version, server name/version, the callable tool/resource/prompt inventory, transport, and handshake latency. Deterministic — no LLM. Use it to verify your own MCP server is alive and spec-compliant.

Input parameters:

- `url` (string, required): The MCP endpoint URL, e.g. https://example.com/mcp

### `list_vendor_status` (~54 tokens)

List the current operational status and recent incidents of every third-party vendor Merlonix monitors (e.g. Cloudflare, GitHub, Stripe). Returns each vendor's slug, current status, and 24h incident count.

### `get_vendor_status` (~58 tokens)

Get the current status plus 30-day status history of one monitored vendor by slug (e.g. "cloudflare"). Use list_vendor_status to discover valid slugs.

Input parameters:

- `slug` (string, required): Vendor slug, e.g. cloudflare

### `list_plans` (~31 tokens)

List Merlonix subscription plans and pricing (Starter, Team, Agency, Compliance) with their monitoring limits.

### `list_my_assets` (~64 tokens)

List the monitored assets (websites/domains) in YOUR Merlonix account. Returns each asset id, hostname, type, and monitoring status. Requires an API key (Authorization: Bearer mk_… from app.merlonix.com → Settings → API keys).

### `get_asset_checks` (~65 tokens)

Get the latest check results (SSL, DNS, uptime, heartbeat, port) for ONE of your monitored assets, by its asset id (from list_my_assets). Requires an API key.

Input parameters:

- `asset_id` (string, required): The asset id from list_my_assets (a UUID).

### `list_my_alerts` (~43 tokens)

List recent alerts across YOUR monitored assets (SSL changes, downtime, DNS drift, vendor incidents, etc.) with their severity and lifecycle status. Requires an API key.

### `create_asset` (~197 tokens)

Start monitoring a new asset (website/domain) in YOUR Merlonix account. Provide a hostname and asset_type; optionally a label and which checks to enable. Returns the created asset. Requires an API key with write scope. Subject to your plan asset quota (a full or non-paying plan returns an error).

Input parameters:

- `asset_type` (string, required): Asset kind: "hostname" (a website/host), "domain", "certificate", or "dns_record".
- `dns_enabled` (boolean): Monitor DNS records.
- `domain_enabled` (boolean): Monitor domain-registration (RDAP) expiry.
- `hostname` (string, required): The hostname to monitor, e.g. example.com
- `label` (string): Optional human label (max 120 chars).
- `ssl_enabled` (boolean): Monitor the TLS certificate (default on for hostnames).
- `uptime_check_url` (string): Optional URL to probe for uptime (enables uptime checks).

### `update_asset` (~124 tokens)

Update one of YOUR monitored assets by its asset id (from list_my_assets): relabel it or toggle which checks run. Returns the updated asset. Requires an API key with write scope.

Input parameters:

- `asset_id` (string, required): The asset id from list_my_assets (a UUID).
- `dns_enabled` (boolean): Enable/disable DNS monitoring.
- `domain_enabled` (boolean): Enable/disable domain-registration (RDAP) monitoring.
- `label` (string): New label (max 120 chars).
- `ssl_enabled` (boolean): Enable/disable TLS-certificate monitoring.

### `delete_asset` (~64 tokens)

STOP monitoring one of YOUR assets and remove it, by its asset id (from list_my_assets). This is irreversible — its check history goes too. Requires an API key with write scope.

Input parameters:

- `asset_id` (string, required): The asset id from list_my_assets (a UUID).

### `acknowledge_alert` (~86 tokens)

Acknowledge one of YOUR alerts by its alert id (from list_my_alerts) — marks it as seen/being-handled without resolving it. Optionally attach a note. Requires an API key with write scope.

Input parameters:

- `alert_id` (string, required): The alert id from list_my_alerts (a UUID).
- `note` (string): Optional note (max 500 chars).

### `resolve_alert` (~104 tokens)

Resolve one of YOUR alerts by its alert id (from list_my_alerts) — closes it. Optionally set resolution ("fixed" | "false_positive" | "wontfix") and a note. Requires an API key with write scope.

Input parameters:

- `alert_id` (string, required): The alert id from list_my_alerts (a UUID).
- `note` (string): Optional note (max 500 chars).
- `resolution` (string): Why the alert is being closed.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-merlonix-monitoring/api#diagnostics

## Score history

- 2026-08-03: 60

## Links

- Remote endpoint: https://api.merlonix.com/mcp
- Website: https://merlonix.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-merlonix-monitoring/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-merlonix-monitoring/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-merlonix-monitoring/api