MCP Endpoint Health Monitor — Protocol & Tools Check
Pricing
Pay per usage
MCP Endpoint Health Monitor — Protocol & Tools Check
Test public Model Context Protocol endpoints beyond HTTP 200. Validate MCP discovery or initialize, JSON-RPC, Streamable HTTP, negotiated versions, tools/list, latency, and authentication boundaries in batch.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Luigy Gabriel
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
7 hours ago
Last modified
Categories
Share
MCP Endpoint Health Monitor
An HTTP 200 is not an MCP health check. This Actor validates public Streamable HTTP endpoints at the protocol layer: JSON-RPC shape, current stateless discovery, compatibility initialization, version negotiation, tool discovery, latency, and authentication boundaries.
Checks
- MCP 2026-07-28
server/discover - Compatibility fallback to the 2025-11-25
initializehandshake - JSON-RPC 2.0 response validity
tools/listand discovered tool names- HTTP status and aggregate latency
- Clear
auth-required,degraded,unreachable, andinvalidstates
Security boundaries
Version 1 accepts unauthenticated public HTTP(S) endpoints only. It rejects credentials embedded in URLs and blocks DNS targets that resolve to private, loopback, link-local, benchmark, multicast, or metadata-network ranges. Redirects are not followed.
Automation
Add up to 50 endpoints, schedule the Actor in Apify, and connect the dataset or webhook to your monitoring workflow. Each endpoint produces one structured dataset item; the complete run summary is stored in the REPORT key-value record.