dynamic-health-monitor
Server Details
Give it one seed; it finds every service and checks HTTP, TCP, SSL and DNS.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 5 tools
health_check and health_discover both operate on a seed and could be confused at a glance, but the descriptions make the boundary clear (full monitoring cycle with persistence vs. free read-only dry run). health_exclude and health_history are clearly distinct operations on separate concerns.
Four of the five tools follow a clean health_<verb/noun> pattern, which is predictable and readable. selftest breaks the convention entirely (no prefix, no separator), a minor but noticeable deviation.
Five tools is well-scoped for a health monitoring server: discovery, monitoring, exclusion, history, and verification each earn their place. No filler or redundancy.
The lifecycle is mostly covered: discover, monitor, add excludes, view history, self-verify. Minor gaps exist—no way to list or remove existing .healthignore entries, and no removal of a monitored seed—but agents can work around these.
Available Tools
5 toolshealth_checkAInspect
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: seed (required), seed_type, healthignore.
health_discoverAInspect
FREE dry run: discover everything a seed would monitor — subdomains, compose services, ports, dependency chains — without monitoring or storing anything.
Inputs: seed (required), seed_type, healthignore.
health_excludeCInspect
FREE: add .healthignore patterns for a seed. Applies next cycle.
Inputs: seed (required), patterns (required).
health_historyBInspect
Timeline of status changes for a seed over the last N hours.
Inputs: seed (required), hours.
selftestAInspect
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.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
External checks of TLS, HTTP, email domain, DNS, ports, blocklists and domain expiry
DNS, TLS, HTTP and SEO checks, plus stateful change watches that diff a page over time.
Audit active CISA KEV ransomware CVEs, SSL/TLS CT log subdomains, SPF/DMARC security & ICANN RDAP.
Passive OSINT and security recon: DNS, TLS, email posture, IP reputation, CVE/KEV, CT logs.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceProvides safe network reconnaissance through DNS resolution, TLS inspection, HTTP security header grading, and bounded port scanning over the stateless MCP protocol.MIT
- AlicenseNot gradedqualityBmaintenancePerforms domain, email, and web audits in a single tool call, checking DNS, RDAP, TLS, SPF, DMARC, DKIM, MTA-STS, BIMI, security headers, and cookies, and returning reproducible findings with an A–F score. Also captures PNG screenshots of public URLs, working read-only against public records with no caching between calls.MIT
- AlicenseNot gradedqualityBmaintenancePassive external attack-surface mapping server that discovers subdomains, DNS records, TLS posture, HTTP headers, and registration data via public sources like CT logs, Shodan, and RDAP/WHOIS, enabling security reconnaissance without active scanning.462 npm3Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides DNS and network-reconnaissance tools that let agents run lookups for records, reverse DNS, ping, passive subdomain discovery, shared nameservers, geolocation, reverse IP, ASN, HTTP headers, subnet arithmetic and page links, plus key-gated WHOIS, MTR and traceroute. Responses are parsed into structured JSON with verbatim raw text, and it runs either through a hosted gateway or as a local stdio server.89 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.