# ai.getvda/dynamic-health-monitor (remote · health.getvda.ai)

Give it one seed; it finds every service and checks HTTP, TCP, SSL and DNS.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `health.getvda.ai`: 71/100 (this document), [markdown](https://verifymcp.io/servers/ai-getvda-dynamic-health-monitor/health.md), [page](https://verifymcp.io/servers/ai-getvda-dynamic-health-monitor/health)

## Channel facts

- Endpoint: `https://health.getvda.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-09-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 322 tokens (~64/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 60% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the ai.getvda/dynamic-health-monitor MCP server?

ai.getvda/dynamic-health-monitor is a hosted endpoint at https://health.getvda.ai/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.

### Claude

```bash
claude mcp add --transport http ai-getvda-dynamic-health-monitor 'https://health.getvda.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-getvda-dynamic-health-monitor": {
      "url": "https://health.getvda.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-getvda-dynamic-health-monitor": {
      "type": "http",
      "url": "https://health.getvda.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-getvda-dynamic-health-monitor]
url = "https://health.getvda.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-getvda-dynamic-health-monitor": {
      "type": "remote",
      "url": "https://health.getvda.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-getvda-dynamic-health-monitor --url 'https://health.getvda.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-getvda-dynamic-health-monitor:
    url: "https://health.getvda.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-getvda-dynamic-health-monitor": {
      "Transport": "http",
      "Url": "https://health.getvda.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-getvda-dynamic-health-monitor -t streamable-http -u 'https://health.getvda.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-getvda-dynamic-health-monitor": {
      "type": "http",
      "url": "https://health.getvda.ai/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-09-20 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `health_discover` (~75 tokens)

FREE dry run: discover everything a seed would monitor — subdomains, compose services, ports, dependency chains — without monitoring or storing anything.

Input parameters:

- `healthignore`: gitignore-style exclusion patterns
- `seed` (required): domain, URL list, docker-compose content, or GitHub repo URL
- `seed_type` (string)

### `health_check` (~85 tokens)

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.

Input parameters:

- `healthignore`: gitignore-style exclusion patterns
- `seed` (required): the same seed you discovered with
- `seed_type` (string)

### `health_history` (~38 tokens)

Timeline of status changes for a seed over the last N hours.

Input parameters:

- `hours` (integer)
- `seed` (required): the seed to report on

### `health_exclude` (~40 tokens)

FREE: add .healthignore patterns for a seed. Applies next cycle.

Input parameters:

- `patterns` (array, required)
- `seed` (required): the seed to update

### `selftest` (~84 tokens)

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) with a proof link for every claim. Intended for registries, graders and auditors: this is behavioural evidence, not a self-description.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-getvda-dynamic-health-monitor/health#diagnostics

## Score history

- 2026-09-21: 71
- 2026-09-20: 71
- 2026-09-19: 70
- 2026-09-18: 70
- 2026-09-17: 69
- 2026-09-16: 69
- 2026-09-15: 68
- 2026-09-14: 68
- 2026-09-13: 67
- 2026-09-12: 67
- 2026-09-11: 66
- 2026-09-10: 66
- 2026-09-09: 65
- 2026-09-08: 65
- 2026-09-07: 64
- 2026-09-06: 64
- 2026-09-05: 64
- 2026-09-04: 63
- 2026-09-03: 63

## Common questions

### What is the ai.getvda/dynamic-health-monitor MCP server?

ai.getvda/dynamic-health-monitor is an MCP server listed in the public MCP registry as ai.getvda/dynamic-health-monitor. Give it one seed; it finds every service and checks HTTP, TCP, SSL and DNS. This page covers its hosted endpoint (https://health.getvda.ai/mcp).

### Is the ai.getvda/dynamic-health-monitor MCP server safe to use?

ai.getvda/dynamic-health-monitor scores 71 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 ai.getvda/dynamic-health-monitor MCP server expose?

ai.getvda/dynamic-health-monitor exposes 5 tools: health_discover, health_check, health_history, health_exclude, selftest. Their descriptions and schemas cost roughly 322 tokens of context every time the server is loaded.

### Does the ai.getvda/dynamic-health-monitor MCP server require authentication?

No. We connected to ai.getvda/dynamic-health-monitor without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ai.getvda/dynamic-health-monitor MCP server still maintained?

ai.getvda/dynamic-health-monitor is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://health.getvda.ai/mcp
- Website: https://health.getvda.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-getvda-dynamic-health-monitor/health.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-getvda-dynamic-health-monitor/health.json
- HTML version of this page: https://verifymcp.io/servers/ai-getvda-dynamic-health-monitor/health