Developer · Remote MCP server
Merlonix Monitoring
Monitoring for agencies - uptime, SSL, DNS, blocklists, AI visibility, MCP health. 8 no-auth tools.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.merlonix/monitoring- Version
- 1.0.2
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-08-04
- Updated
- 2026-08-04
- Publisher
- com.merlonix
- Namespace
- Namespace verified by the MCP Registry via the domain merlonix.com · how
- Website
- merlonix.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.merlonix.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- merlonix 1.0.0 · protocol 2025-06-18
- Tools discovered
16 - show names
check_domain_health,check_agent_readiness,check_mcp_health,check_email_blacklist,check_broken_links,list_vendor_status,get_vendor_status,list_plans,list_my_assets,get_asset_checks,list_my_alerts,create_asset,update_asset,delete_asset,acknowledge_alert,resolve_alert- Checked on
- 2026-10-05
How to connect Merlonix Monitoring
Merlonix Monitoring is a remote MCP server: there is nothing to install. Its endpoint is https://api.merlonix.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Merge Conflict Forecaster MCPPredict local Git merge-conflict pressure from branch topology and changed-file overlap without... | Local · stdio |
| MergetrainQueue parallel-agent worktree branches, test together, serialize and recover Git pushes. | Local · stdio |
| MergewardenCheck whether a coding agent's changes stayed inside the scope it was given. | Local · stdio |
| Meridian SkillsRoutes AI tasks to dynamic LLM-generated skills via an orbital classifier. | Local · stdio |
| Mermaid MCP AppMCP App that renders Mermaid diagrams as interactive UI in Claude, VS Code and other MCP clients. | Local · stdio |
| MeroFoundryBuild and publish full-stack apps from your coding agent: models, rules, pages, auth, per-app MCP. | Remote · HTTPLive check: sign-in required |
| MERX - TRON Resource ExchangeTRON energy exchange for AI agents. 54 tools, 30 prompts, 21 resources. A2A + ACP. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| MessInventory of your service accounts, kept current by your coding agents. Metadata only, no secrets. | Remote · HTTPLive check: sign-in required |