@mhdd_24/api-health-mcp
Related Servers
Alternatives to @mhdd_24/api-health-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables live website health checks including TLS, HTTPS, and security headers, returning an A-F grade with specific fixes.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query and monitor service status, latency, and performance through configurable checks (HTTP, TCP, SSL, keyword, JSON-path) and exposes tools for listing services, retrieving metrics, and running on-demand checks.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables live TLS/SSL certificate health checks for any hostname, providing expiry, hostname match, trust verdict, and a health score. Supports both free and paid deep tiers with protocol/cipher analysis.MIT
- AlicenseAqualityCmaintenanceEnables users to check HTTP status codes, find broken same-origin links, review SEO basics, and inspect common security headers with polite, permission-based crawling from any MCP client.4MIT
- AlicenseAqualityCmaintenanceEnables agents to monitor websites for content changes with persistent baselines, durable notifications, and explicit review acknowledgement, using direct HTTPS fetches or isolated Playwright browser rendering for dynamic pages.4Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables scanning code and URLs for API deprecations, auditing websites for professional quality, and running resale value scans from photo URLs over MCP streamable HTTP.-
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: showing defaults, checking a single URL, and checking multiple URLs. There is no overlap in scope, so an agent can easily select the correct tool.
All tools follow the consistent 'apihealth_' prefix followed by a verb-like descriptor (status, check, check_many). The naming pattern is uniform and intuitive.
With 3 tools covering the core health-check operations, the count is well-scoped for the server's narrow purpose. It is neither sparse nor excessive.
The toolset covers checking one or multiple URLs and viewing defaults, which covers the primary workflow. A minor gap is the lack of a way to modify defaults, but this is not essential for typical health-check usage.