Developer · Remote MCP server
Dynamic Health Monitor
Give it one seed; it finds every service and checks HTTP, TCP, SSL and DNS.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.getvda/dynamic-health-monitor- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-03
- Updated
- 2026-09-03
- Publisher
- ai.getvda
- Namespace
- Namespace verified by the MCP Registry via the domain getvda.ai · how
- Website
- health.getvda.ai
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://health.getvda.ai/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
- health 0.1.1 · protocol 2026-07-28
- Tools discovered
- 5:
health_discover,health_check,health_history,health_exclude,selftest - Checked on
- 2026-10-05
How to connect Dynamic Health Monitor
Dynamic Health Monitor is a remote MCP server: there is nothing to install. Its endpoint is https://health.getvda.ai/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 |
|---|---|
| DVERA CT verification toolsDVERA drives CT verification of mission-critical C/C++: setup, analysis, tests, coverage. | Local · stdio |
| DvtDashboards as data. Author, validate, render, and share dvt dashboards from any MCP client. | Remote · HTTPLive check: sign-in required |
| dxpert.ai - free UNS tools (no API key)Free Sparkplug B topic linting, UNS naming checks and AI-readiness screening. No API key. | Local · stdio |
| DynadotMCP server for Dynadot domain registrar - domain search, registration, DNS, and transfers. | Local · stdio |
| DynamodbMCP server for AWS DynamoDB with fine-grained tool control and configurable access levels. | Local · stdio |
| DynatraceConnect AI assistants to Dynatrace to query observability data and analyze problems. | Remote · HTTP |
| DynoxideA DynamoDB emulator with an MCP server exposing 35 DynamoDB tools to coding agents. | Local · stdio |
| E2bCreate and manage secure sandboxes for running AI agent code. | Local · stdio |