MCP Server Change and Health Monitor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token; a tool call needs one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_mcp_serversA | Check MCP servers by URL, npm package, or official registry search. Returns one row per server: whether it answered, how fast, the tools it exposes now, and what changed since the last run, with breaking changes marked. Runs on Apify, pay per event. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection between overlapping tools. Its purpose—health-checking and diffing MCP servers—is clearly stated.
The single name check_mcp_servers follows a clear verb_noun snake_case convention. With one tool there is no inconsistency to introduce.
A single tool is thin even for a narrow monitoring scope; the three input modes (URL, npm package, registry search) could arguably be distinct tools. Still, one 'check' operation is a defensible minimal surface.
The core action—probe a server, report latency, exposed tools, and diffs with breaking changes marked—is covered. However, there's no way to manage a watchlist, batch-check multiple servers, or retrieve historical results beyond 'since the last run'.