Merlonix Monitoring
REMOTE · API.MERLONIX.COM · SCANNED SEP 20
Monitoring for agencies — uptime, SSL, DNS, blocklists, AI visibility, MCP health. 8 no-auth tools.
Available components
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. How we score → Why this is hard to score →
Endpoint Security54
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_asset). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1605 tokens (~100/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Merlonix Monitoring MCP server?
Merlonix Monitoring is a hosted endpoint at https://api.merlonix.com/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.
remote · api.merlonix.com
claude mcp add --transport http com-merlonix-monitoring 'https://api.merlonix.com/mcp'
{
"mcpServers": {
"com-merlonix-monitoring": {
"url": "https://api.merlonix.com/mcp"
}
}
} {
"servers": {
"com-merlonix-monitoring": {
"type": "http",
"url": "https://api.merlonix.com/mcp"
}
}
} [mcp_servers.com-merlonix-monitoring] url = "https://api.merlonix.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-merlonix-monitoring": {
"type": "remote",
"url": "https://api.merlonix.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-merlonix-monitoring --url 'https://api.merlonix.com/mcp' --transport streamable-http
mcp_servers:
com-merlonix-monitoring:
url: "https://api.merlonix.com/mcp" {
"McpServers": {
"com-merlonix-monitoring": {
"Transport": "http",
"Url": "https://api.merlonix.com/mcp"
}
}
} assistant mcp add com-merlonix-monitoring -t streamable-http -u 'https://api.merlonix.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Sept 26 0
- Stability: 0.97 → pass security
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1372 → 1605 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “check_broken_links” functional
- New tool “check_email_blacklist” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.merlonix.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=merlonix.com | CN=WE1,O=Google Trust Services,C=US | 20 Aug 2026 | 18 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | ec5fdc0cd2ee1de50e8cb1a72e85d957 |
| SANs: merlonix.com, api.merlonix.com, *.api.merlonix.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.merlonix.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| merlonix.com. | present | 2371 | 13 | Verified |
| api.merlonix.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.merlonix.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.merlonix.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
acknowledge_alert ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_id | string | yes | The alert id from list_my_alerts (a UUID). |
| note | string | – | Optional note (max 500 chars). |
No output schema declared.
No examples provided.
check_agent_readiness ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hostname | string | yes | A public hostname, e.g. example.com |
No output schema declared.
No examples provided.
check_broken_links ~100
Scan one web page for dead links (4xx/5xx/unreachable) and mixed content (http subresources on an https page). Returns each link with its status. Single-page scan, not a crawl — pass the exact page URL. Rate-limited to a few scans per minute, so batch calls will be throttled.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The exact page URL to scan, e.g. https://example.com/pricing |
No output schema declared.
No examples provided.
check_domain_health ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hostname | string | yes | A public hostname, e.g. example.com |
No output schema declared.
No examples provided.
check_email_blacklist ~101
Check whether a domain or IP is listed on the major DNS blocklists (DNSBLs) that mail providers consult before accepting mail — the usual reason legitimate mail silently lands in spam. Returns each zone checked, whether it is listed, and the return code. Deterministic DNS lookups, no LLM.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | A public domain or IP address, e.g. example.com or 203.0.113.10 |
No output schema declared.
No examples provided.
check_mcp_health ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The MCP endpoint URL, e.g. https://example.com/mcp |
No output schema declared.
No examples provided.
create_asset ~197
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).
| Name | Type | Req | Description |
|---|---|---|---|
| asset_type | string | yes | 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 | yes | 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). |
No output schema declared.
No examples provided.
delete_asset ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | The asset id from list_my_assets (a UUID). |
No output schema declared.
No examples provided.
get_asset_checks ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | The asset id from list_my_assets (a UUID). |
No output schema declared.
No examples provided.
get_vendor_status ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Vendor slug, e.g. cloudflare |
No output schema declared.
No examples provided.
list_my_alerts ~43
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_my_assets ~64
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_plans ~31
List Merlonix subscription plans and pricing (Starter, Team, Agency, Compliance) with their monitoring limits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_vendor_status ~54
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
resolve_alert ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_id | string | yes | The alert id from list_my_alerts (a UUID). |
| note | string | – | Optional note (max 500 chars). |
| resolution | string | – | Why the alert is being closed. |
No output schema declared.
No examples provided.
update_asset ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | 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. |
No output schema declared.
No examples provided.
What is the Merlonix Monitoring MCP server?
Merlonix Monitoring is an MCP server listed in the public MCP registry as com.merlonix/monitoring. Monitoring for agencies, uptime, SSL, DNS, blocklists, AI visibility, MCP health. 8 no-auth tools. This page covers its hosted endpoint (https://api.merlonix.com/mcp).
Is the Merlonix Monitoring MCP server safe to use?
Merlonix Monitoring scores 77 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 Merlonix Monitoring MCP server expose?
Merlonix Monitoring exposes 16 tools: check_domain_health, check_agent_readiness, check_mcp_health, check_email_blacklist, check_broken_links, and 11 more. Their descriptions and schemas cost roughly 1,355 tokens of context every time the server is loaded.
Does the Merlonix Monitoring MCP server require authentication?
No. We connected to Merlonix Monitoring without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Merlonix Monitoring MCP server still maintained?
Merlonix Monitoring is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.