Dynamic Health Monitor is an MCP server with 5 tools an agent can call, among them health_check, health_discover, health_exclude. It answers at https://health.getvda.ai/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 11 of 11 times since 3 September 2026; the last check, on 19 October 2026, succeeded.
Give it one seed; it finds every service and checks HTTP, TCP, SSL and DNS.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
health_check | Full monitoring cycle: re-discover from the seed, merge with the saved map, check HTTP/TCP/SSL/DNS, detect latency anomalies, roll dependent failures up to one root cause, persist state, and report what changed. Inputs: healthignore, seed, seed_type |
health_discover | FREE dry run: discover everything a seed would monitor — subdomains, compose services, ports, dependency chains — without monitoring or storing anything. Inputs: healthignore, seed, seed_type |
health_exclude | FREE: add .healthignore patterns for a seed. Applies next cycle. Inputs: patterns, seed |
health_history | Timeline of status changes for a seed over the last N hours. Inputs: hours, seed |
selftest | FREE, no payment required. Runs this agent's real capability on a fixed canned input and returns the genuine result, an honest assertion grade, and the full trust manifest (signed Agent Card, JWKS, governance/licence chain, safety posture) |
Every block below points at https://health.getvda.ai/mcp. Pick your client and copy.
claude mcp add --transport http dynamic-health-monitor https://health.getvda.ai/mcp
{
"mcpServers": {
"dynamic-health-monitor": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://health.getvda.ai/mcp"]
}
}
}{
"mcpServers": {
"dynamic-health-monitor": {
"url": "https://health.getvda.ai/mcp"
}
}
}{
"servers": {
"dynamic-health-monitor": {
"type": "http",
"url": "https://health.getvda.ai/mcp"
}
}
}{
"context_servers": {
"dynamic-health-monitor": {
"url": "https://health.getvda.ai/mcp"
}
}
}{
"mcpServers": {
"dynamic-health-monitor": {
"serverUrl": "https://health.getvda.ai/mcp"
}
}
}{
"mcpServers": {
"dynamic-health-monitor": {
"url": "https://health.getvda.ai/mcp"
}
}
}name: Dynamic Health Monitor
version: 0.0.1
schema: v1
mcpServers:
- name: Dynamic Health Monitor
type: streamable-http
url: https://health.getvda.ai/mcp{
"mcpServers": {
"dynamic-health-monitor": {
"httpUrl": "https://health.getvda.ai/mcp"
}
}
}{
"mcpServers": {
"dynamic-health-monitor": {
"type": "http",
"url": "https://health.getvda.ai/mcp"
}
}
}{
"mcpServers": {
"dynamic-health-monitor": {
"url": "https://health.getvda.ai/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fhealth.getvda.ai%2Fmcp&type=streamable_http&id=dynamic-health-monitor&name=Dynamic%20Health%20Monitor
It answered our last check on 19 October 2026 in 201 ms. Over 11 checks since 3 September 2026 it answered 11. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by getvda.ai and served from health.getvda.ai, the vendor's own domain: https://health.getvda.ai/mcp.
5, as returned by the server's own tools/list on 3 September 2026: health_check, health_discover, health_exclude, health_history, selftest.
It answered our last check on 19 October 2026 in 201 ms. Over 11 checks since 3 September 2026 it answered 11.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://health.getvda.ai/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: ai.getvda. Endpoint host: health.getvda.ai. ARD identifier: urn:air:ai.getvda:mcp:dynamic-health-monitor.
First indexed 3 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.